You may want to look at WS-Addressing. It provides some mechanisms to state
who the calls is from, the action, a unique message ID, ... I'm not sure how
far the WS-FX Addressing project (http://ws.apache.org/ws-fx/addressing/)
has gotten, but it may be worth taking a look at.
Thanks,
- David
You may want to look at WS-Addressing. It provides some mechanisms to state
who the calls is from, the action, a unique message ID, ... I'm not sure how
far the WS-FX Addressing project (http://ws.apache.org/ws-fx/addressing/)
has gotten, but it may be worth taking a look at.
Thanks,
- David
I disagree, the right way is to start with your WSDL and schema files. If
you want any hope of being WS-I compliant or using doc/literal this is your
best bet. As soon as you start with an interface, you start dealing Java
types that do not correlate to schema types very well. For example, if you
Title: How to view my Axis Java objects as XML
That's not always accurate. If your schema is complicated,
Axis cannot handle minOccurs/maxOccurs very well and choice. So although all the
Java objects created will serialize to valid XML, the combination of objects and
therefore the structure
