[JBoss JIRA] Created: (JBWS-1401) JBossWS installation to Tomcat standalone is broken
by davide de benedictis (JIRA)
JBossWS installation to Tomcat standalone is broken
---------------------------------------------------
Key: JBWS-1401
URL: http://jira.jboss.com/jira/browse/JBWS-1401
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Environment: Tomcat 5.5.20
Reporter: davide de benedictis
following instructions and release notes on:
http://labs.jboss.com/portal/jbossws/user-guide/en/html/installation.html...
Tomcat start and successfully install a jbossws context.
The "{tomcat.home}/jbossws-deploy" directory is NOT created.
Connecting on "http://127.0.0.1:8080/jbossws/"
I can see the JBossWS welcome page.
trying to list the deployed Web Services I get:
javax.servlet.ServletException: Servlet.init() for servlet ContextServlet threw exception
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BasePro
tocol.java:664)
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
java.lang.Thread.run(Thread.java:595)
root cause
org.jboss.kernel.spi.registry.KernelRegistryEntryNotFoundException: Entry not found with name: Servi
ceEndpointManager
org.jboss.kernel.plugins.registry.AbstractKernelRegistry.getEntry(AbstractKernelRegistry.java:99)
org.jboss.ws.server.ServiceEndpointManagerFactory.getServiceEndpointManager(ServiceEndpointManagerF
actory.java:52)
org.jboss.ws.integration.tomcat.TomcatContextServlet.initServiceEndpointManager(TomcatContextServle
t.java:77)
org.jboss.ws.common.CommonContextServlet.init(CommonContextServlet.java:54)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BasePro
tocol.java:664)
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
java.lang.Thread.run(Thread.java:595)
--
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, 11 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
18 years
[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, 1 month
[JBoss JIRA] Commented: (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=comments#action_12348007 ]
Darran Lofthouse commented on JBWS-1260:
----------------------------------------
Working branch for this issue - https://svn.jboss.org/repos/jbossws/branches/dlofthouse/JBWS-1260
> 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 month
[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 month
[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:
-----------------------------------
Summary: WSDL To Java - Parameter unwrapping fails for a lot of scenarios. (was: exception when creating client-artifacts with unwrap enabled)
Affects Version/s: jbossws-1.0.4
(was: jbossws-1.0.3)
Description:
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)
was:
When creating client artifacts for http://www.webservicex.net/CurrencyConvertor.asmx?WSDL with unwrap set to true, the following error occurs:
Exception in thread "main" org.jboss.ws.WSException: String passed is null
at org.jboss.ws.metadata.wsdl.WSDLUtils.firstLetterUpperCase(WSDLUtils.java:453)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:138)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:114)
at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:701)
at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:694)
at org.jboss.ws.tools.WSDLToJava.unwrapResponse(WSDLToJava.java:321)
at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:555)
at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:372)
at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:512)
at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:534)
at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:188)
at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:329)
at org.jboss.ws.tools.WSTools.process(WSTools.java:138)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:120)
at org.jboss.ws.tools.WSTools.main(WSTools.java:61)
my wstools config is as follows:
<configuration xmlns="http://www.jboss.org/jbossws-tools">
<global>
<package-namespace namespace="http://www.webserviceX.NET/" package="test"/>
</global>
<wsdl-java file="http://www.webservicex.net/CurrencyConvertor.asmx?WSDL" unwrap="true">
<mapping file="CurrencyConverter-mapping.xml"/>
</wsdl-java>
</configuration>
> 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 month