[JBoss JIRA] Updated: (JBWS-1260) WSDL To Java - Parameter unwrapping fails for a lot of scenarios.
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1260?page=all ]
Thomas Diesler updated JBWS-1260:
---------------------------------
Fix Version/s: jbossws-1.0.5
> 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.2.0, 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
17 years, 4 months
[JBoss JIRA] Created: (JBWS-1310) OperationMetaData.getJavaMethod throws WSException: Ambiguous javaMethod
by Ray Tomlinson (JIRA)
OperationMetaData.getJavaMethod throws WSException: Ambiguous javaMethod
------------------------------------------------------------------------
Key: JBWS-1310
URL: http://jira.jboss.com/jira/browse/JBWS-1310
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.3
Environment: Windows XP dual core processor
Reporter: Ray Tomlinson
Priority: Blocker
Running two copies of a test client beating up on a few web-service methods produces "Ambiguous javaMethod: <method>" from org.jboss.ws.metadata.OperationMetaData(getJavaMethod) (line 203). There is no potential ambiguity since all methods have quite distinctive signatures and the problem is sporadic.
I believe this a lack of synchronization between multiple threads simultaneously trying to resolve the javaMethod field. Both see that javaMethod has not yet been set and the second to finish finds the javaMethod field has already been set by the first and mis-interprets this as an ambiguous method situation. Running a dual core processor exacerbates the problem.
Cannot use jboss with this bug.
--
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
17 years, 4 months