Thomas -
The JAXRPC 1.1 Spec states (pg 37) that xsd:any is required and should be
mapped to a property named "_any" of type SOAPElement. As for xsd:anyType,
that is optional.
You are correct about my use case. My operation accepts a schema type that
includes an element of undefined structur
Hello -
I have discovered a number of bugs in the SAAJ implementation for 4.0.1 RC2 and
have created fixes for them. These fixes enable the use of xsd:any elements.
However, I would not consider the fixes elegant in any manner, as it appears
that the current SAAJ implementation derived from A
I have now confirmed both issues:
1) Unable to use SOAPBody.addDocument() method to create SOAPElement from DOM
Document
2) Response object with xsd:any does not serialize properly (no matter what is
set in the SOAPElement object).
Wish I could continue this, but its time for bed. Thoughts?
After some hours of digging around, the actual issue seems to be related to
serialization of the response object. The response object looks as follows:
| public class GetByUserResponse {
| protected javax.xml.soap.SOAPElement _any;
|
| public GetByUserResponse() {
| }
As a follow up, I attempted to use SOAPElementAxisImpl directly by:
| SOAPElement element = new SOAPElementAxisImpl(doc.getDocumentElement());
|
This had no effect either. I am currently using 4.0.1 RC1, has this bug been
fixed in a more recent version in CVS?
Shawn Dahlen
View the orig
I am having issues trying to build a SOAPElement from a DOM Document. The code
is as follows:
| MessageFactory factory = MessageFactory.newInstance();
| SOAPMessage msg = factory.createMessage();
| SOAPBody body = msg.getSOAPPart().getSOAPEnvelope().getSOAPBody();
| SOAPElement element
For those who are curious, I found the solution to the issue I was having.
JAXRPC 1.1 does not support xsd:any with a specified namespace. It only
supports the namespace values of ##any and ##other. When I used one of those
values, the appropriate Java class was generated by wscompile. JAXRPC
Thank you for your response. Unfortunately, switching from anonymous types did
not help the situation. WSCOMPILE still unwraps the type containing only an
xsd:any element.
If anyone has other suggestions, I would appreciate it. Otherwise, who or what
organization should I contact about a pot
Hello -
I am attempting to create an implementation of a web service in which a
particular operation is defined as follows:
http://iss.lmco.com/schema/action-item-summary";
maxOccurs="1"/>
It appears part of my WSDL definition was lost. Here it is:
|
|
|
| service:getAllResponse"/>
|
|
|
|
| service:getAllInput"/>
| service:getAllOutput"/>
|
|
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=vie
I have been reading over the Web Services for J2EE spec to determine if
absolute urls are allowed for WSDL imports. At this time I would say they are
allowed. Is this assumption correct?
I would like to know because my company has published a number of abstract WSDL
files I must implement.
I
In your binding section, you seem to use the namespace prefix 'soapbind', while in the
service section, you use 'soap' for the address element. They should be from the same
namespace:
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
Just a thought.
View the original post :
http://www.jbo
Hello -
I'm in the process of trying to deploy a web service that uses a modular WSDL file.
Our company has published xml schema and abstract WSDL documents in a central
repository, and I am attempting to provide an implementation of that abstract service.
My concrete WSDL document appropriat
13 matches
Mail list logo
