[JBoss JIRA] Updated: (JBWS-1266) NullPointerException when using wstools with unwrap=true
by Darran Lofthouse (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1266?page=all ]
Darran Lofthouse updated JBWS-1266:
-----------------------------------
Fix Version/s: (was: jbossws-1.0.5)
> NullPointerException when using wstools with unwrap=true
> --------------------------------------------------------
>
> Key: JBWS-1266
> URL: http://jira.jboss.com/jira/browse/JBWS-1266
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: wstools
> Affects Versions: jbossws-1.0.3
> Reporter: Magesh Kumar B
> Assigned To: Darran Lofthouse
> Priority: Trivial
> Attachments: TestSEIService.wsdl
>
>
> Consider the following configuration:
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration xmlns="http://www.jboss.org/jbossws-tools"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.org/jbossws-tools http://www.jboss.org/jbossws-tools/schema/jbossws-tool_1_0.xsd">
> <wsdl-java file="wsdl/TestSEIService.wsdl" unwrap="true"/>
> </configuration>
> This contains the unwrap="true" property, using this with the attached wsdl leads to a NPE (NullPointerException). If this parameter is removed then it works properly. Although it could be an invalid usecase, a NULL checking is required!
> This is for the following SEI
> SEI that has primitive input parameter types
> public interface MySEI extends java.rmi.Remote {
> public int returnIntParamVoid(int a, int b)...
> ...
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
- 1
- 0
[JBoss JIRA] Created: (JBWS-1337) SOAP request with complex types mapped to default namespace is not accepted
by Magesh Kumar B (JIRA)
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
Fix For: jbossws-1.0.5
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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
- 2
- 1
[JBoss JIRA] Updated: (JBWS-1260) WSDL To Java - Parameter unwrapping fails for a lot of scenarios.
by Darran Lofthouse (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1260?page=all ]
Darran Lofthouse updated JBWS-1260:
-----------------------------------
Comment: was deleted
> WSDL To Java - Parameter unwrapping fails for a lot of scenarios.
> -----------------------------------------------------------------
>
> Key: JBWS-1260
> URL: http://jira.jboss.com/jira/browse/JBWS-1260
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: wstools
> Affects Versions: jbossws-1.0.4
> Reporter: Ole Matzura
> Assigned To: Darran Lofthouse
> Fix For: jbossws-1.0.5
>
>
> Testing parameter unwrapping when using wsdl to java with the following scenarios: -
> A - Element contains anonymous complex type which contains a single element.
> B - Element contains anonymous complex type which contains two elements.
> C - Element references complex type which contains a single element.
> D - Element references complex type which contains two elements.
> E - Element references complex type which contains an anonymous type which contains a single element.
> F - Element references complex type which contains an anonymous type which contains two elements.
> G - Element contains anonymous complex type which contains a single element which is an array. (1)
> H - Element references complex type which contains a single element which is an array. (3)
> I - Element references complex type which contains an anonymous type which contains a single element which is an array. (5)
> J - Element contains anonymout complex type which contains an empty sequence.
> K - Element references complex type which contains an empty sequence.
> L - Element references complex type which contains an anonymous type which contains an empty sequence.
> Scenarios A, B, and G are failing with the following error: -
> org.jboss.ws.WSException: String passed is null
> at org.jboss.ws.metadata.wsdl.WSDLUtils.firstLetterUpperCase(WSDLUtils.java:455)
> at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:137)
> at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113)
> Scenario D
> The parameter is being unwrapped even though it contains two elements, one of the elements is being lost.
> Scenarios E, F, I, and L are failing with the following error: -
> java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
> at javax.xml.namespace.QName.<init>(Unknown Source)
> at javax.xml.namespace.QName.<init>(Unknown Source)
> at org.jboss.ws.tools.WSDLToJava.unwrapResponseParticles(WSDLToJava.java:316)
> Scenarios J, and K are failing with the following error: -
> org.jboss.ws.WSException: Attempt to unwrap a response type with no particles
> at org.jboss.ws.tools.WSDLToJava.unwrapResponse(WSDLToJava.java:285)
> at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:540)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
- 1
- 0