SOAP spec

after reading soap specification at w3c i have a few questions
1) you can't use soap-envelope namespace with application specific <element>?
since soap schema have not define namespace (env) can use with <MyElement>
inside soap schema -->
targetNamespace=http://www.w3.org/2003/05/soap-envelope
indicates that the elements defined by this schema are <Header>
for example: <env:MyElement> --> we cannot use the envlope namespace with <MyElement>?
note: <MyElement> is an element generate from my own application
2) in soap schema we have
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.w3.org/2003/05/soap-envelope" targetNamespace="http://www.w3.org/2003/05/soap-envelope" elementFormDefault="qualified">
in soap request xml we can delcare using that namespace by
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
so all element with env namespace will follow rules in soap schema at
http://www.w3.org/2003/05/soap-envelope/
is that correct?
at the same time all element in My namespace will follow rules in my new schema that i define?
3) the above is why we need namespace?
for example -
a) soap-envelope namespace is a set of elements includes <Envelope> <Header>
b) WSDL namespace is for a set of elements <definitions> <types> <message> <portType> <binding> .. etc etc
c) My own defined namespace is for a set of elements <MyElement> .. etc etc that i defined.
so namespace can distinguish a set of elements in XML that's defined by different people?
Thanks

Hi!
you can add your own complex content to the SOAP Faults detail element, as described in the Basic Profile (http://www.ws-i.org/Profiles/BasicProfile-1.1.html#SOAP_Fault_Extensibility), maybe you could add a ref to an attachment there?
regards,
/Ole
eviware.com

Similar Messages

JDeveloper 10.1.3 - Disabling ns0: namespace prefix in soap body children ?

I am attempting to use a PeopleSoft web service. However, the PeopleSoft web service does not recognize operations which have a namespace prefix. Using visual studio, namespace prefixes are not used in the child elements of the soap body element. I am able to call the service using visual studio.
JDeveloper 10.1.3 uses a namespace prefix for children of the body element which is recommended by the soap spec. However, I need to disable that behavior so that I can actually get the program working with PeopleSoft.
Can anyone tell me if there is an easy way to disable the ns0: prefix that is used by the generated web service proxy stub? I have traced through the generated proxy code but I do not see any properties that can be modified. The only thing I can think of is to modify the generated code but I do not want to go that route.
Thanks,
Rich

Delete the NS0: related text, in JDev, from your WSDL and it should work. I had the same problem with .NET not liking it also.
Keep in mind you'll have to tweak the WSDL again if you regenerate it.
You sure you're using 10.1.3? I upgraded and it shows the NS0: as a problem in existing projects. I'm working on the latest, production download so maybe it's been corrected.

Different soap request in 9.2.0.4 linux and windows for same webservice

hi,
i deployed a webservice on iis5 (dotnet 1.1). the client for this web service is written in java and is loaded into oracle db (9.2.0.4 linux). and there are errors. the same java code is working fine on 9.2.0.4 windows.
description of the error:
<?xml version="1.0" encoding="UTF-8" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<ns1:MethodName xmlns:ns1=http://tempuri.org/Service/message/ SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SomeString xsi:type="xsd:string" xsi:nil="true" />
<ErrorDes xsi:type="xsd:string" xsi:nil="true" />
</ns1:MethodName>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
there are problems with the 'SomeString' and 'ErrorDes' elements. there is an attribute xsi:nil="true". in the working requests this isn't present. the result of this, if for example DName isn't assigned a value this element isn't in the resulting response:
<?xml version="1.0" encoding="utf-8" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns=http://tempuri.org/ xmlns:types="http://tempuri.org/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<q1:MethodNameResponse xmlns:q1=http://tempuri.org/Service/message/>
<Result xsi:type="xsd:int">0</Result>
<ErrorDes xsi:type="xsd:string">string</ErrorDes>
</q1:MethodNameResponse>
</soap:Body>
</soap:Envelope>
what can cause this behaviour? is there a way to prevent sending the xsi:nil attribute?
thanks
ralf

This is just one of the web service interop problems you can face. Both omitting the accessor with the NULL value as in your "working request" and placing xsi:nil attribute with the value "true" as in "not working request" are valid in soap messages. The problem happens when either the soap client or soap server/container does not fully support the soap spec or support with wrong interpretations. Most of the toolkit are not sophisticated enough to let you choose one of two options above.
Maybe you might want to consider not allowing non-null values so that you can get around with the interop problem, and add logic in the client and service implementation to handle special cases for default values indicating null.
Below is FYI.
SOAP 1.1 spec says the following.
"A NULL value or a default value MAY be represented by omission of the accessor element. A NULL value MAY also be indicated by an accessor element containing the attribute xsi:null with value '1' or possibly other application-dependent attributes and values."
On the other hand, there is no "null" attribute in http://www.w3.org/2001/XMLSchema-instance namespace referenced by xsi in your soap messages, and xsi:nil is the valid attribute name.
Regards,
Pyounguk

EncodingStyle attr not properly ns qualified in SOAP response (7.0 beta)

It appears that BEA does not properly qualify the
encodingStyle attribute in its SOAP response message.
Although the document does specify an encodingStyle, the
attribute does not come from the SOAP envelope namespace.
In the captured response message below, encodingStyle
should be env:encodingStyle to be correct.
HTTP/1.0 200 OK
Date: Thu, 28 Mar 2002 21:13:25 GMT
Server: WebLogic WebLogic Server 7.0 beta Fri Feb 22 10:33:57 PST 2002 166852
Content-Length: 387
Content-Type: text/xml
Connection: Close
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
</env:Header>
<env:Body>
<m:buyResponse xmlns:m="http://www.bea.com/examples/Trader"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<result>
<stockSymbol>BEAS</stockSymbol>
<numberTraded>10</numberTraded>
</result>
</m:buyResponse>
</env:Body>
</env:Envelope>

Hi M,
First, I see your point (and agree), from a "pristine" point of view ;-)
But the SOAP spec (or Note, or Comment, or whatever) actually allows this :-)
Here's the exact paragraph:
"A SOAP application SHOULD include the proper SOAP namespace on all elements and
attributes defined by SOAP in messages that it generates. A SOAP application MUST
be able to process SOAP namespaces in messages that it receives. It MUST discard
messages that have incorrect namespaces (see section 4.4) and it MAY process SOAP
messages without SOAP namespaces as though they had the correct SOAP namespaces."
Kind of "Clintonian", if you know what I mean, but it is there. If your SOAP processor
were to discard this message, one would have to assume that MAY is synonymous with
MAY NOT :-)
Is the glass HALF-FULL, or HALF-EMPTY?
Anyway, I agree that the env namespace prefix OUGHT TO BE (like that, lol) added
to the encodingStyle attribute here :-)
Regards,
Mike Wooten
"M Shue" <[email protected]> wrote:
>
It appears that BEA does not properly qualify the
encodingStyle attribute in its SOAP response message.
Although the document does specify an encodingStyle, the
attribute does not come from the SOAP envelope namespace.
In the captured response message below, encodingStyle
should be env:encodingStyle to be correct.
HTTP/1.0 200 OK
Date: Thu, 28 Mar 2002 21:13:25 GMT
Server: WebLogic WebLogic Server 7.0 beta Fri Feb 22 10:33:57 PST 2002 166852
Content-Length: 387
Connection: Close
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
</env:Header>
<env:Body>
<m:buyResponse xmlns:m="http://www.bea.com/examples/Trader"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<result>
<stockSymbol>BEAS</stockSymbol>
<numberTraded>10</numberTraded>
</result>
</m:buyResponse>
</env:Body>
</env:Envelope>

Upper or lower case letter for SOAP

I used the JAXM from Sun to create my soap message,
but the tag <soap-env> is in lower case. I don't know if this is right or wrong, but the application server doesn't accept this!
Anybody can tell me if I can say this is a bug of JAXM?

I used the JAXM from Sun to create my soap message,
but the tag <soap-env> is in lower case. I don't know
if this is right or wrong, but the application server
doesn't accept this!
Anybody can tell me if I can say this is a bug of
JAXM?I'm having a very similar problem. The w3c SOAP specs appear to specify the <soap-env> tag to be uppercase, or at least it is in uppercase in all their examples.
Anyone got any idea of a workaround or when a fix will be issued?

Differences between SOAP-ENV and soapenv

Hi all,
I am trying to find out why some SOAP request (inbound web services) in siebel work and do not work when the namespace prefix is SOAP-ENV and soapenv,
For example XML Spy generates "</SOAP-ENV:Envelope>" where as soapUI generates "<soapenv:Envelope>" and some difference in the name spaces.
Intrestingly other scenarios like invoking inbound web services with WS-Security and with out security had worked fine when tested from XML Spy.
Why is siebel not accepting the xml from XML Spy for Siebel Authentication scenario?
Thank you

Hi, just to let you all know, and please correct me if I am wrong, I have found this on the internet:
http://mail-archives.apache.org/mod_mbox/ws-axis-user/200308.mbox/%3C00fd01c35ba6$ed85e620$6f01a8c0@TPX21%3E
Although, the SOAP spec uses the namespace prefixes of SOAP-ENV and
SOAP-ENC, these prefixes aren't required. You can use any string you like as
a namespace prefix, just as long as it maps to the appropriate namespace
name. The reason why the spec bothers with telling us the notational
conventions is that prefix names (e.g., SOAP-ENV) aren't normative, and the
spec just happens to be using this set of naming conventions. So the prefix
name doesn't matter. Only the actual referenced namespace name (e.g.,
http://schema.xmlsoap.org/soap/envelope/) matters.
I confirmed this information from an expert from Fusion Middleware and he says that the name-prefix could be anything as long as it is mapped in the namespace (URL from the SOAP XML).

Setting response HTTP status code

Hi all,
it's possible to set a response HTTP 202 status code for Axis?
Thanks Pasquy.

Not sure if you're aware of this, but the status codes that must/should be used are specified in the SOAP HTTP binding spec and the Basic Profile.
See http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html (see, e.g., s4.3.6), and the SOAP spec.
That said, apparently 202 is acceptable in some circumstances, and I'm not sure on how to set the response code with Axis.
-Tim

COM Support in Photoshop CS3

Hi all,
Recently we upgraded from CS to CS3 but for the life of me, I can't find any COM assemblies (Interop DLLs) to use in CS3 for automating Photoshop.
Anyone knows if this is removed? Or is it included in certain versions of CS3 like the extended one?
I need this to be able to compile one of our tools from CS to CS3.
Thanks.

There is no COM or DCOM. Use SOAP instead. You're most likely out of luck if you have to compile code to an interface specification that no longer exists.
Adobe is apparently doing maintenance on their Web site right this minute. I was unable to find the Photoshop DOM & SOAP spec online, though I rarely look either. I have my own copies.
While the following may not be much help, you may be able to bootstrap your search by starting here:
http://www.adobe.com/devnet/bridge/
or here:
http://www.adobe.com/support/downloads/product.jsp?product=111&platform=Windows

7940 (2) how to Cfwd just the second line?

I have a 7940 with (2) lines. The Cfwdall will of course foward line (1) to voicemail. But what if I want to just cfwd just line #2 to voicemail? Is there a quick way to do this? I cant figure out if I have to adjust my soft key template, or this is not possible??
thanks!

Hey Tommer,
I like your new method! The other thing I was thinking was that if you want to stick with the original plan, the Agents could turn off the ring on the shared line (via ccmuser) when they want to opt out. This might be a bit cumbersome but would accomplish what they are looking for.
Here is some info on AXL;
AVVID XML Layer (AXL)
The AVVID XML Layer (AXL) Application Programming Interface (API) provides a mechanism for inserting, retrieving, updating, and removing data from the database using an eXtensible Markup Language (XML) Simple Object Access Protocol (SOAP) interface. This allows a programmer to access Cisco CallManager data using XML and receive the data in XML form, instead of using a binary library or DLL.
The AXL API methods, known as requests, are performed using a combination of HTTP and SOAP. SOAP is an XML remote procedure call protocol. Users perform requests by sending XML data to the Cisco CallManager server. The server then returns the AXL response, which is also a SOAP message.
From this doc;
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_usage_guide09186a008065282b.html
By exposing Cisco CallManager real-time information, performance counter, and database information, customers can write customized applications. AXL-Serviceability APIs, an extensible SOAP-based XML web service, conforms to the SOAP Spec 1.1 [1] and the WSDL Spec 1.1 [2]. AXL-Serviceability APIs represent one server component of the Cisco Serviceability product.
AXL-Serviceability APIs provides RPC-style operations for the clients. Clients of AXL-Serviceability APIs can run in different OS platforms and can communicate with AXL-Serviceability APIs through the standard SOAP protocol. The AXL-Serviceability APIs includes a goal to provide access to the core Cisco Serviceability functionalities through an open and standard transport protocol and data model.
The following list gives the Serviceability services that are exposed via AXL-Serviceability APIs:
Windows 2000 Perfmon Data Collection.
Cisco CallManager Device RIS Search
The AXL-Serviceability APIs gets implemented as an ISAPI component of the IIS. AXL-Serviceability APIs as an extensible service allows external implementation of SOAP ports that are to be plugged in through the SOAP port extension dll. This document describes the implementation of AXL-Serviceability APIs that are based on version 3.3.0.1 or higher. The latest implementation of AXL-Serviceability APIs supports only the Perfmon Data Collection functionality and Real-Time information. Cisco plans to add more Serviceability functionalities to the AXL-Serviceability APIs in the near future.
From this doc;
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_usage_guide09186a0080655371.html#wp36586
Hope this helps!
Rob

Exact purpose of MimeHeaders param to MessageFactory.createMessage()

I'm building a web service intermediary, and I'm trying to make sure I can handle
SOAP messages with attachments.
When I first saw the "MimeHeaders" parameter in "MessageFactory.createMessage(MimeHeaders,
InputStream)", I was a little befuddled. I figured this was related to handling
attachments, but I find almost zero documentation on what I'm supposed to be doing
here.
In my experiments, I tried sending a message with a simple "text/xml" attachment.
I set the content type of the attachment when creating the attachment. If my
"createMessage()" call passed "null" for the MimeHeaders parameter, then the resulting
SOAPMessage ignored the MIME-ness of the message and just stored the SOAP envelope.
If I instead create a MimeHeaders object and add a "Content-Type" header of "text/xml",
and pass that object instead of "null" for the MimeHeaders parameter, then it
appears to record the SOAP envelope along with the attachment. I'm guessing the
"Content-Type" header that I added in the MimeHeaders object applies to the main
body of the message, and not the attachment.
My main problem is that I tried that change with the MimeHeaders object through
pure guesswork. I can't find anything in the BEA docs that gives me a clue what
really should be done here.

Yes, you will want to create MIME headers from the HTTP headers.
Q1. Are you saying that if the content-type of the HTTP header is "text/xml",
it wouldn't find the attachments?
A1. Dunno. I wouldn't though, because that's not how the SwA (or SAAJ) says to
do it. See the following link: http://www.w3.org/TR/2000/NOTE-SOAP-attachments-20001211#SOAPMultipart
Q2. If the content-type of the HTTP request is "multipart/related", is there any
assumption about whether the main SOAPMessage is 1.0/1.1 or 1.2?
A2. I hope not, because that (determining the SOAP version based on the MIME type)
is dictated in the SOAP specs themselves. See the following link: http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383526.
Regards,
Mike Wooten
"David Karr" <[email protected]> wrote:
>
Ok, that's helpful. However, your description seems to imply that the
only way
for the incoming message to be considered to have attachments is to use
"multipart/related".
Are you saying that if the top-level content-type is "text/xml", it
wouldn't
find the attachments? Also, if the top-level content-type is "multipart/related",
is there any assumption about whether the main SOAPMessage is 1.0/1.1
or 1.2?
So if the intermediary is a servlet, I should just pass the HTTP headers
into
the MimeHeaders?
"Michael Wooten" <[email protected]> wrote:
Hi David,
These classes are part of the JAX-RPC API, so you would want to search
for this
information on Sun's (or Javasoft's) website. If you can't find it there,
it may
be because they (Sun) wants to be able to change the implementationwithout
breaking
your code :-) That's actually what makes seperating the interface from
the implementation,
powerful.
That said, the Content-type header, in this MimeHeader object, is used
to determine
the MIME type of the InputStream. If it's multipart/related, an attempt
will be
made to create a SOAPMessage with attachment parts, from the InputStream.
The
format of this multipart/related message is covered in RFC 2387 (http://www.faqs.org/rfcs/rfc2387.html).
This document says that the Content-type of each part, is in the Header
fields
of the part itself. These parts are the AttachmentPart objects thatare
returned
(in a java.util.Iterator), when you call the SOAPMessage.getAttachments()
method.
If the Content-type header in this MimeHeader is application/soap+xml,
the InputStream
is assumed to be a SOAP 1.2 message (http://www.w3.org/TR/2002/CR-soap12-part2-20021219/).
If it's text/xml, the InputStream is assumed to be a SOAP 1.0/1.1 message.
Typically, a Web Service intermediary is realized as a Servlet Filter
or JAX-RPC
Handler. In the case of the former, you would use the createMessage(MIMEHeaders,InputStream)
method. The HttpServletRequest contains the headers you use, as well
as the ServletInputStream.
In the case of the later, the SOAPMessage has already been created by
the JAX-RPC
implementation in WLS :-)
HTH,
Mike Wooten
"David Karr" <[email protected]> wrote:
I'm building a web service intermediary, and I'm trying to make sure
I can handle
SOAP messages with attachments.
When I first saw the "MimeHeaders" parameter in "MessageFactory.createMessage(MimeHeaders,
InputStream)", I was a little befuddled. I figured this was related
to handling
attachments, but I find almost zero documentation on what I'm supposed
to be doing
here.
In my experiments, I tried sending a message with a simple "text/xml"
attachment.
I set the content type of the attachment when creating the attachment.
If my
"createMessage()" call passed "null" for the MimeHeaders parameter,then
the resulting
SOAPMessage ignored the MIME-ness of the message and just stored the
SOAP envelope.
If I instead create a MimeHeaders object and add a "Content-Type" header
of "text/xml",
and pass that object instead of "null" for the MimeHeaders parameter,
then it
appears to record the SOAP envelope along with the attachment. I'mguessing
the
"Content-Type" header that I added in the MimeHeaders object applies
to the main
body of the message, and not the attachment.
My main problem is that I tried that change with the MimeHeaders object
through
pure guesswork. I can't find anything in the BEA docs that gives me
a clue what
really should be done here.

Circular references in web-services

Hi
I'm running WebLogic 6.1sp3 on Solaris and NT. I've been experimenting
a little bit with retrieving data from web-services and have been
experiencing that any circular references I have make the application
spin until it ends in a StackOverflowError.
Does SOAP allow for circular references or is this just a flaw in
WebLogic.
Looking at the structure of the XML reply from a SOAP service (I
have not studied the build-up of XML replies in depth) my immediate
thought would be that the structure does not allow that. You would
require referencing of nested elements instead of embedding. However
searching around a bit I found that something called PocketSOAP
(http://www.pocketsoap.com/) claim to support circular references.
If SOAP does not support this I guess I'll be looking into some
algorithm to untangle circular references.
have a nice day
ThorAAge

The soap implementation in WLS 6.1 does not support
circular references.
WLS 7.0 can handle circular reference (when soap encoding is used).
Check out the section 5 of the soap spec
(http://www.w3.org/TR/SOAP/#_Toc478383512)
if you would like to see more details.
regards,
-manoj
"Thor AAge Eldby" <[email protected]> wrote in message
news:[email protected]..
Hi
I'm running WebLogic 6.1sp3 on Solaris and NT. I've been experimenting
a little bit with retrieving data from web-services and have been
experiencing that any circular references I have make the application
spin until it ends in a StackOverflowError.
Does SOAP allow for circular references or is this just a flaw in
WebLogic.
Looking at the structure of the XML reply from a SOAP service (I
have not studied the build-up of XML replies in depth) my immediate
thought would be that the structure does not allow that. You would
require referencing of nested elements instead of embedding. However
searching around a bit I found that something called PocketSOAP
(http://www.pocketsoap.com/) claim to support circular references.
If SOAP does not support this I guess I'll be looking into some
algorithm to untangle circular references.
have a nice day
ThorAAge

Web Services support for collection like ArrayList

Getting this error message:
"<Info> Did not find property empty in java.util.ArrayList:
java.lang.NullPointerException"
Are collections like ArrayList supported or am I trying to do something that
can't be done? Any suggestions?
Thanks
Danny

Hi Danny,
Betcha thought I forgot 'bout cha, huh?
I didn't ;-)
The short answer to your question is no; WLS 6.1 does not support using any of
the classes in java.util.*. However, it does support Object arrays as an element
of an Object array, which means you can have code in you service implementation
that looks like this:
public Object[] getNestedObjects()
     Object[] objects = new Object[2];
     objects[0] = new Object[]{
          new String("23.76"),
          new Float((float)23.76)
     // Here, WorkOrder is a JavaBean or an object
     // that implements weblogic.soap.xml.XMLizable
     WorkOrder[] workOrders = new WorkOrder[]{
                    new WorkOrder(),
                    new WorkOrder(),
                    new WorkOrder()
     objects[1] = new Object[]{
          new String("My name is"),
          new String("Slim Shady"),
          workOrders
     return objects;
The main issue I see with doing this is again, interoperability ;-)
If the SOAP toolkit consuming the WSDL for the web service with the above method
cannot handle the "xsd:anyType" XML Schema data type, you're in trouble. In general,
SOAP toolkits want to know what type an element is so they can process it correctly.
When you use a Variant data type (in Visual Basic) or java.lang.Object (in Java),
you are basically promoting the use of weak data typing (or late binding). From
what I've read about SOAP (well, actually what Don Box said he had in mind), XML
Schema and namespaces were adopted to combat this very thing- weak or no data
typing. Personally, I agree ;-) I think strong data typing makes processing a
SOAP request much easier and faster, for everyone. Don't get me wrong, I don't
have anything against object casting, but SOAP parameters (and return values)
are not objects. They are XML elements, just like the other parts of the SOAP
message. There is no behavior, just state. This being the case, isn't it safer
to stick with the data types (e.g. arrays, structures, primitives, etc.) defined
in the SOAP spec and "XML Schema Part 2: Datatypes" document? Enough SOAP boxing
(pun intended). If you are interested in the "complexTypes" object graphs (using
developer defined classes that implement weblogic.soap.xml.XMLizable) lab results,
I can send you a zip. The biggest difference between using JavaBeans and objects
that implement weblogic.soap.xml.XMLizable, is that you have much more control
over which Java objects the later gets serialized/deserialized to/from. With classes
that implement weblogic.soap.xml.XMLizable, the SOAP processor passes you the
actual XML stream for the SOAP parameter (which in this case, is your developer
defined class). It (the SOAP processor) also calls your developer defined class
to get an XML representation for it's data types. It works great with Java clients
(using the client.jar, of course), and I'm trying it out with .NET and MS SOAP
clients this weekend. The most interesting revelation was figuring out how wsgen
(well, actually the WSDL processor) generates the information in the <types> element
of the WSDL ;-) I actually even know how to code an XMLizable so that it produces
the exact element and attribute names I want. I also figure out how to get it
to produce an <element ...>, as opposed to a <attribute ...>, and visa versa.
Of course, WLS 7.0 (and WebLogic Workshop) make all of this a moot point, but
it was fun to get the SOAP/WSDL processors in WLS 6.1 to "do my bidding" for a
short while ;-)
Regards,
Mike Wooten
"Danny Ngo" <[email protected]> wrote:
>
Hi Mike,
Thank you for your response. Do you know if WLS 6.1 Web Services support
the
return of nested object array (object that contains other object arrays).
Thanks
-Danny
"Michael Wooten" <[email protected]> wrote:
Hi Danny,
For interoperability (with non-Java SOAP implementations)reasons, the
Java collections
are not supported in WLS 6.1 ;-) You should consider using an arrayin
place of
this.
Regards,
Mike Wooten
Danny Ngo <[email protected]> wrote:
Getting this error message:
"<Info> Did not find property empty in java.util.ArrayList:
java.lang.NullPointerException"
Are collections like ArrayList supported or am I trying to do something
that
can't be done? Any suggestions?
Thanks
Danny

Looking for plsql to create nonce

Hello: I need to create a nonce value to pass to webservice. It is used for security purposes - used so that sending the same message again is not allowed since I guess the service checks whether the nonce has been recently used and rejects recent duplicate nonces.
It is defined for soap messages at http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf
I'm on apex 4.1.1 with 11g db
Thanks, Hawk

Thanks - your suggestion works fine. I also got some base64 encoded stuff to work with the following (soap spec references some base64 binary blah blah...):
- utl_raw.cast_to_varchar2(utl_encode.base64_encode(utl_raw.cast_to_raw( +18CharacterString+ )))
but prefer your solution DBMS_RANDOM.STRING('x',24). Thanks.

WSAddressing MessageID soapenv:mustUnderstand="0"

Hi,
I try to invoke an async WebService from BPEL.
Then I monitor the SOAP request I see the SOAP header shown below.The attribute soapenv:mustUnderstand is false for element MessageID and ReplyTo. According to the SOAP spec my WebService must understand these elements, because MessageID and ReplyTo contains the informations for the callback.
In the SOAP request from BPEL the mustUnderstand attribute is false, so my JBossWS ServerEngine remove these header informations, before the WSAReceiveHandler can read them.
10:16:15,906 DEBUG [SOAPElementAxisImpl] Remove child node: ns1:MessageID
10:16:15,916 DEBUG [SOAPElementAxisImpl] Remove child node: ns3:ReplyTo
I like to know there I can change the value of the mustUnderstand attribute, so that my ServerEngine have to understand the message?
Part of the SOAP request header:
<ns1:MessageID ns2:rootId="304" ns2:parentId="304"
ns2:priority="3"
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0"
xmlns:ns1="http://schemas.xmlsoap.org/ws/2003/03/addressing"
xmlns:ns2="http://schemas.oracle.com/bpel">
bpel://localhost/default/TestAsncBPEL~1.0/304-BpInv0-BpSeq0.3-3
</ns1:MessageID>
<ns3:ReplyTo
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
soapenv:mustUnderstand="0" xsi:type="ns3:EndpointReferenceType"
xmlns:ns3="http://schemas.xmlsoap.org/ws/2003/03/addressing">
<ns3:Address xsi:type="xsd:string">
http://test:9700/orabpel/default/TestAsncBPEL/1.0/TestSession/TestSessionServiceIFRequester
</ns3:Address>
<ns3:ReferenceProperties xsi:nil="true" />
<ns3:PortType xsi:type="xsd:QName"
xmlns:ns4="http://test.de/wsdl">
ns4:TestSessionCallbackIF
</ns3:PortType>
<ns3:ServiceName xsi:type="xsd:QName"
xmlns:ns5="http://test.de/wsdl">
ns5:TestSessionService
</ns3:ServiceName>
</ns3:ReplyTo>

Hi !
I am from the OraBEPL team.
SOAP spec says:
"A env:mustUnderstand value of 'true' means that the SOAP node must process the header with the semantics described in that header's specification, or else generate a SOAP fault."
Seems like JBoss has a problem. If it doesn't bother to process the header, it should not remove the header before it can be processed by the target handler.
I am not aware there is way to change that to true. But in the new release, we will not sending them over at all. How is that gonna affect you ?
regards,
- glenn

How to add exactly 2 NON XML caracters at the end of a SOAP body

Hello all I am trying to add two (and only two) extra non xml caracters "AA" at the END of a SOAP body using the JAXWS handlers as so:
HTTP/1.1 200 OK
Content-Type: text/xml;charset=UTF-8
Content-Length: 131
Content-Length: 131
Server: Jetty(7.x.y-SNAPSHOT)
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body></SOAP-ENV:Body></SOAP-ENV:Envelope>
AA
The problem is that if you try to add them to the SOAP body (see code below) you get a XML Unmarshalling exception. If I add "AA" as a soap attachment I get MORE than 2 caracters after the SOAP body (which I don't want)
Here is the my SOAPHandler code :
@Override
public boolean handleMessage(SOAPMessageContext mc) {
if (Boolean.TRUE.equals(mc.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY))) {
try {
SOAPMessage message = context.getMessage()
String stringSoapMessage= getMsgAsString(message);
stringSoapMessage += "ss";
message.getSOAPPart().setContent((Source) new StreamSource(new ByteArrayInputStream(msg.getBytes())));
message.saveChanges();
context.setMessage(message);
} catch (Exception e1) {
return true;
public String getMsgAsString(SOAPMessage message) throws SOAPException {
String msg = null;
try {
ByteArrayOutputStream baos = new ByteArrayOutputStream();
message.writeTo(baos);
msg = baos.toString();
} catch (Exception e) {
e.printStackTrace();
return msg;
so my question is this: is there any way to add exactly 2 non xml caracters at the end of the soap body using jaxws handlers ? I have spent several weeks on this so it is not an easy question...
Thanks,
Fred.

Yes I have done it using CFX interceptors. But the runtime dependencies needed were too big for this particular use. I mean having to use these:
apache/cxf/cxf-bundle/2.6.0/cxf-bundle-2.6.0.jar
org/apache/neethi/neethi/3.0.2/neethi-3.0.2.jar
wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.jar
/org/codehaus/woodstox/wstx-asl/3.2.4/wstx-asl-3.2.4.jar
org/apache/ws/xmlschema/xmlschema-core/2.0.2/xmlschema-core-2.0.2.jar
org/mortbay/jetty/jetty-util/6.0.2/jetty-util-6.0.2.jar
org/eclipse/jetty/jetty-util/7.5.4.v20111024/jetty-util-7.5.4.v20111024.jar
org/apache/geronimo/specs/geronimo-servlet_2.5_spec/1.1.2/geronimo-servlet_2.5_spec-1.1.2.jar
org/apache/geronimo/specs/geronimo-javamail_1.4_spec/1.7.1/geronimo-javamail_1.4_spec-1.7.1.jar
org/apache/geronimo/specs/geronimo-servlet_3.0_spec/1.0/geronimo-servlet_3.0_spec-1.0.jar
org/eclipse/jetty/jetty-http/7.5.4.v20111024/jetty-http-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-server/7.5.4.v20111024/jetty-server-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-io/7.5.4.v20111024/jetty-io-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-continuation/7.5.4.v20111024/jetty-continuation-7.5.4.v20111024.jar
to add two caracters at the end of a soap message seems like over kill. If this is the only way to do this then i'll do it this way but it just seems like the implementation of the JAXWS API in JDK 6 seems inches away from being able to do this no ?
Thanks for the replies,
Fred

SOAP spec

Similar Messages

Maybe you are looking for