You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2007/01/12 22:12:27 UTC
[jira] Created: (GERONIMO-2730) JAX-RPC EJB Web Services support
appears to be broken
JAX-RPC EJB Web Services support appears to be broken
-----------------------------------------------------
Key: GERONIMO-2730
URL: https://issues.apache.org/jira/browse/GERONIMO-2730
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M2
Reporter: Jarek Gawor
The JAX-RPC-based EJB web services support appears to be broken. I'm attaching test code that demonstrates the problems. Please note that the test WS is identical as in the POJO tests (see https://issues.apache.org/jira/browse/GERONIMO-2729) where it works fine.
Here are the problems discovered:
1) By default, jar deployment with WS EJB will fail with:
Deployer operation failed: Unable to resolve reference "WebServiceContainer" in
gbean JEE5/JAXRPCEJB/1.1/car?EJBModule=JEE5/JAXRPCEJB/1.1/car,J2EEApplication=nu
ll,StatelessSessionBean=Greeter,j2eeType=WSLink,name=Greeter to a gbean matching
the pattern [?name=JettyWebContainer#]due to: No matches for referencePatterns:
[?name=JettyWebContainer#]
This can be fixed by adding an explicit dependency on the given container in the open-ejb.xml file (see the open-ejb.xml in the attached patch). I think such dependency should be automatically added by the deployer.
2) ?wsdl on the service fails with the following error:
HttpException(500,Could not fetch wsdl!,java.lang.IllegalStateException: request
must contain a wsdl or WSDL parameter: {wsdl=[Ljava.lang.String;@11054a5})
at org.apache.geronimo.jetty6.JettyEJBWebServiceContext.handle(JettyEJBW
ebServiceContext.java:147)
3) Invocation on the service fails with:
{http://xml.apache.org/axis/}stackTrace:java.lang.IndexOutOfBoundsExcept
ion: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at java.util.ArrayList.get(ArrayList.java:321)
at org.apache.axis.description.JavaServiceDesc.getOperationsByQName(Java
ServiceDesc.java:520)
at org.apache.axis.description.JavaServiceDesc.getOperationByElementQNam
e(JavaServiceDesc.java:465)
at org.apache.geronimo.axis.server.ReadOnlyServiceDesc.getOperationByEle
mentQName(ReadOnlyServiceDesc.java:151)
at org.apache.axis.providers.java.RPCProvider.getOperationDesc(RPCProvid
er.java:296)
at org.apache.openejb.server.axis.EJBContainerProvider.processMessage(EJ
BContainerProvider.java:62)
These errors were discovered when using trunk with jetty6.
Since openejb will be updated in trunk shortly, I think these errors can be ignored for now. However, I do not know if the same problems exist in Geronimo 1.2 for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-2730) JAX-RPC EJB Web Services support
appears to be broken
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved GERONIMO-2730.
-----------------------------------
Resolution: Fixed
The remaining OpenEJB issues were resolved so JAX-RPC EJB web services should be working now in Geronimo.
> JAX-RPC EJB Web Services support appears to be broken
> -----------------------------------------------------
>
> Key: GERONIMO-2730
> URL: https://issues.apache.org/jira/browse/GERONIMO-2730
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M2
> Reporter: Jarek Gawor
> Assigned To: Jarek Gawor
> Attachments: jaxrpc-ejb-tests.patch
>
>
> The JAX-RPC-based EJB web services support appears to be broken. I'm attaching test code that demonstrates the problems. Please note that the test WS is identical as in the POJO tests (see https://issues.apache.org/jira/browse/GERONIMO-2729) where it works fine.
> Here are the problems discovered:
> 1) By default, jar deployment with WS EJB will fail with:
> Deployer operation failed: Unable to resolve reference "WebServiceContainer" in
> gbean JEE5/JAXRPCEJB/1.1/car?EJBModule=JEE5/JAXRPCEJB/1.1/car,J2EEApplication=nu
> ll,StatelessSessionBean=Greeter,j2eeType=WSLink,name=Greeter to a gbean matching
> the pattern [?name=JettyWebContainer#]due to: No matches for referencePatterns:
> [?name=JettyWebContainer#]
> This can be fixed by adding an explicit dependency on the given container in the open-ejb.xml file (see the open-ejb.xml in the attached patch). I think such dependency should be automatically added by the deployer.
> 2) ?wsdl on the service fails with the following error:
> HttpException(500,Could not fetch wsdl!,java.lang.IllegalStateException: request
> must contain a wsdl or WSDL parameter: {wsdl=[Ljava.lang.String;@11054a5})
> at org.apache.geronimo.jetty6.JettyEJBWebServiceContext.handle(JettyEJBW
> ebServiceContext.java:147)
> 3) Invocation on the service fails with:
> {http://xml.apache.org/axis/}stackTrace:java.lang.IndexOutOfBoundsExcept
> ion: Index: 0, Size: 0
> at java.util.ArrayList.RangeCheck(ArrayList.java:546)
> at java.util.ArrayList.get(ArrayList.java:321)
> at org.apache.axis.description.JavaServiceDesc.getOperationsByQName(Java
> ServiceDesc.java:520)
> at org.apache.axis.description.JavaServiceDesc.getOperationByElementQNam
> e(JavaServiceDesc.java:465)
> at org.apache.geronimo.axis.server.ReadOnlyServiceDesc.getOperationByEle
> mentQName(ReadOnlyServiceDesc.java:151)
> at org.apache.axis.providers.java.RPCProvider.getOperationDesc(RPCProvid
> er.java:296)
> at org.apache.openejb.server.axis.EJBContainerProvider.processMessage(EJ
> BContainerProvider.java:62)
> These errors were discovered when using trunk with jetty6.
> Since openejb will be updated in trunk shortly, I think these errors can be ignored for now. However, I do not know if the same problems exist in Geronimo 1.2 for example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-2730) JAX-RPC EJB Web Services support
appears to be broken
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor reassigned GERONIMO-2730:
-------------------------------------
Assignee: Jarek Gawor
Committed the tests to trunk. The 'invocationTest' fails because of a number of OpenEJB issues.
> JAX-RPC EJB Web Services support appears to be broken
> -----------------------------------------------------
>
> Key: GERONIMO-2730
> URL: https://issues.apache.org/jira/browse/GERONIMO-2730
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M2
> Reporter: Jarek Gawor
> Assigned To: Jarek Gawor
> Attachments: jaxrpc-ejb-tests.patch
>
>
> The JAX-RPC-based EJB web services support appears to be broken. I'm attaching test code that demonstrates the problems. Please note that the test WS is identical as in the POJO tests (see https://issues.apache.org/jira/browse/GERONIMO-2729) where it works fine.
> Here are the problems discovered:
> 1) By default, jar deployment with WS EJB will fail with:
> Deployer operation failed: Unable to resolve reference "WebServiceContainer" in
> gbean JEE5/JAXRPCEJB/1.1/car?EJBModule=JEE5/JAXRPCEJB/1.1/car,J2EEApplication=nu
> ll,StatelessSessionBean=Greeter,j2eeType=WSLink,name=Greeter to a gbean matching
> the pattern [?name=JettyWebContainer#]due to: No matches for referencePatterns:
> [?name=JettyWebContainer#]
> This can be fixed by adding an explicit dependency on the given container in the open-ejb.xml file (see the open-ejb.xml in the attached patch). I think such dependency should be automatically added by the deployer.
> 2) ?wsdl on the service fails with the following error:
> HttpException(500,Could not fetch wsdl!,java.lang.IllegalStateException: request
> must contain a wsdl or WSDL parameter: {wsdl=[Ljava.lang.String;@11054a5})
> at org.apache.geronimo.jetty6.JettyEJBWebServiceContext.handle(JettyEJBW
> ebServiceContext.java:147)
> 3) Invocation on the service fails with:
> {http://xml.apache.org/axis/}stackTrace:java.lang.IndexOutOfBoundsExcept
> ion: Index: 0, Size: 0
> at java.util.ArrayList.RangeCheck(ArrayList.java:546)
> at java.util.ArrayList.get(ArrayList.java:321)
> at org.apache.axis.description.JavaServiceDesc.getOperationsByQName(Java
> ServiceDesc.java:520)
> at org.apache.axis.description.JavaServiceDesc.getOperationByElementQNam
> e(JavaServiceDesc.java:465)
> at org.apache.geronimo.axis.server.ReadOnlyServiceDesc.getOperationByEle
> mentQName(ReadOnlyServiceDesc.java:151)
> at org.apache.axis.providers.java.RPCProvider.getOperationDesc(RPCProvid
> er.java:296)
> at org.apache.openejb.server.axis.EJBContainerProvider.processMessage(EJ
> BContainerProvider.java:62)
> These errors were discovered when using trunk with jetty6.
> Since openejb will be updated in trunk shortly, I think these errors can be ignored for now. However, I do not know if the same problems exist in Geronimo 1.2 for example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2730) JAX-RPC EJB Web Services support
appears to be broken
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor updated GERONIMO-2730:
----------------------------------
Attachment: jaxrpc-ejb-tests.patch
> JAX-RPC EJB Web Services support appears to be broken
> -----------------------------------------------------
>
> Key: GERONIMO-2730
> URL: https://issues.apache.org/jira/browse/GERONIMO-2730
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M2
> Reporter: Jarek Gawor
> Attachments: jaxrpc-ejb-tests.patch
>
>
> The JAX-RPC-based EJB web services support appears to be broken. I'm attaching test code that demonstrates the problems. Please note that the test WS is identical as in the POJO tests (see https://issues.apache.org/jira/browse/GERONIMO-2729) where it works fine.
> Here are the problems discovered:
> 1) By default, jar deployment with WS EJB will fail with:
> Deployer operation failed: Unable to resolve reference "WebServiceContainer" in
> gbean JEE5/JAXRPCEJB/1.1/car?EJBModule=JEE5/JAXRPCEJB/1.1/car,J2EEApplication=nu
> ll,StatelessSessionBean=Greeter,j2eeType=WSLink,name=Greeter to a gbean matching
> the pattern [?name=JettyWebContainer#]due to: No matches for referencePatterns:
> [?name=JettyWebContainer#]
> This can be fixed by adding an explicit dependency on the given container in the open-ejb.xml file (see the open-ejb.xml in the attached patch). I think such dependency should be automatically added by the deployer.
> 2) ?wsdl on the service fails with the following error:
> HttpException(500,Could not fetch wsdl!,java.lang.IllegalStateException: request
> must contain a wsdl or WSDL parameter: {wsdl=[Ljava.lang.String;@11054a5})
> at org.apache.geronimo.jetty6.JettyEJBWebServiceContext.handle(JettyEJBW
> ebServiceContext.java:147)
> 3) Invocation on the service fails with:
> {http://xml.apache.org/axis/}stackTrace:java.lang.IndexOutOfBoundsExcept
> ion: Index: 0, Size: 0
> at java.util.ArrayList.RangeCheck(ArrayList.java:546)
> at java.util.ArrayList.get(ArrayList.java:321)
> at org.apache.axis.description.JavaServiceDesc.getOperationsByQName(Java
> ServiceDesc.java:520)
> at org.apache.axis.description.JavaServiceDesc.getOperationByElementQNam
> e(JavaServiceDesc.java:465)
> at org.apache.geronimo.axis.server.ReadOnlyServiceDesc.getOperationByEle
> mentQName(ReadOnlyServiceDesc.java:151)
> at org.apache.axis.providers.java.RPCProvider.getOperationDesc(RPCProvid
> er.java:296)
> at org.apache.openejb.server.axis.EJBContainerProvider.processMessage(EJ
> BContainerProvider.java:62)
> These errors were discovered when using trunk with jetty6.
> Since openejb will be updated in trunk shortly, I think these errors can be ignored for now. However, I do not know if the same problems exist in Geronimo 1.2 for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira