Axis implementation in 4.0.2 buggy - elements not qualified

[bgrieder]

Hi,

I am implementing webservices of the type document/literal and am having trouble with (sub) element namespaces on the message sent back by JBoss.

It looks like the Axis implementation in Jboss is buggy; (sub)elements in the SOAP message sent back do not have any namespace prefix even though the schema attribute elementFormDefault is set to qualified.

Setting it to unqualified is a workaround (when you can afford it).

Please check the link below for the axis issue.

http://java2.5341.com/msg/94432.html

Bruno

[thomas.diesler]

This is a known issue and stems from the very fundamental problem that Axis does not even look at the schema let alone your elementFomDefault to derive its meta data.

The solution we can offer is to use a ws4ee-deployment.xml file where you explicitly define the form to use for every property.

[bgrieder]

Thomas,

Thanks. I feel less alone.

I have also noticed a difference between the Sun JWS Pack and Axis - one looks at the element name while the other looks at the type name hence the need to define an element which has the name of its type in the xsd if you want to use the two at the same time. [which is what I do: jwsdp to generate the mappings and Axis as a client]

Does the new non-Axis stack fix all this?

Bruno

[thomas.diesler]

Yes it fixes all of that, because it passes all issues that have so far been resolved from the jboss testsuite + some 350 new internal tests + some 2200 Sun compatibility tests.

I hope to have a final release ready soon.