]
Darran Lofthouse updated JBWS-1337:
-----------------------------------
Fix Version/s: (was: jbossws-1.0.5)
SOAP request with complex types mapped to default namespace is not
accepted
---------------------------------------------------------------------------
Key: JBWS-1337
URL:
http://jira.jboss.com/jira/browse/JBWS-1337
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jaxrpc
Affects Versions: jbossws-1.0.3.SP1
Environment: Tested with SOAPUI and JBossWS1.0.3SP1 on JBossAS4.0.4GA
Reporter: Magesh Kumar B
Priority: Critical
Literal web services are required to be schema valid. So when looking into these issues,
as long as the xml matches the schema, then we MUST support it.
<Foo xmlns="blah"/>
Is semantically equivalent to
<ns:Foo xmlns:ns="blah"/>
Both should work. Also the following are equivalent:
<customer xmlns="customer-namespace">
<name xmlns=''>Fred</name>
</customer>
<ns:customer xmlns:ns="customer-namespace">
<name>Fred</name>
</ns:customer>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: