[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475874 ] Davanum Srinivas commented on GERONIMO-2876: Looks like i have to wait for a new patch :) thanks, dims Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475373 ] Lin Sun commented on GERONIMO-2876: --- Thanks Jarek and Lasantha for reviewing the patch! I intended to put out there to get some comments.:) Jarek, yes I missed that few fines to invoke the ejbcontainer in EJBWebServiceGBean.java and will add that in. Lasantha, what I proposed is to have the javax.wsdl.Definition object stored in org.apache.geronimo.jaxws.PortInfo and this doesn't impact CXF at all (see the patch I attached). It is not good to have Axis2 or CXF specific info in JAXWS module in general but I propose we do that in this case for javax.wsdl.Definition before we have a better solution. I'll submit a new patch later on. Thanks again!:-) Lin Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475388 ] Lasantha Ranaweera commented on GERONIMO-2876: -- Hi Lin, I would dearly like if you can use the existing org.apache.geronimo.axis2.PortInfo to this patch too (if the effort you are putting is 200-300% from your original effort). It will make our work more progressive than going again backward and coming back again. Also it will add more value to your patch too. What is the exact problem you are having with org.apache.geronimo.axis2.PortInfo? Thanks, Lasantha Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475431 ] Lin Sun commented on GERONIMO-2876: --- Hi Lasantha, The prob I am having is that in JAXWSServiceBuilder.configureEJB, it sets the jaxws.portInfo as the value of portInfo to the targetGBean. I could overwrite it in Axis2Builder by providing an Axis2 version of the configureEJB method, but I had a hard time to get the axis2.portInfo from there. A simple cast won't work. I think the following might work: 1) check if wsdlFile exists, if exist, try cast it to axis2.portInfo. 2) if wsdlFile doesn't exist, construct a new axis2.portInfo by coping values from jaxws.portInfo. Lin Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475472 ] Jarek Gawor commented on GERONIMO-2876: --- Btw, is it really necessary to pass the WSDLDefinition object around anyway? It looks like that definition is used in AxisServiceGenerator.getServiceFromWSDL() but then it is serialized into a String and converted into some Axis2 type. Wouldn't it be just easier to directly read from a file or url (portInfo.getWsdlFile()) ? Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475495 ] Lin Sun commented on GERONIMO-2876: --- Jarek just showed me the portion of code in CXF that builds wsdlURL based on configurationBaseUrl and wsdlFile. So let's not passing WSDLDefinition object around and build it inside of Axis2WebServiceContainer. Hope this solution will make everyone happy. :-) I'll submit a patch for that. thanks for all your comments and help!:-) Lin Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475543 ] Lasantha Ranaweera commented on GERONIMO-2876: -- Agreed :) Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475264 ] Lasantha Ranaweera commented on GERONIMO-2876: -- Hi Lin, I have to oppose your first suggestion of removing org.apache.geronimo.axis2.PortInfo and restoring with org.apache.geronimo.jaxws.PortInfo due to the following reason. :( Currently org.apache.geronimo.axis2.PortInfo file will store the javax.wsdl.Definition object which will be necessary to handle WSDL provided situation. Then we might need to add the javax.wsdl.Definition to the common org.apache.geronimo.jaxws.PortInfo which is not acceptable IMO. If you have a solution for the above problem then I will +1. Thanks, Lasantha Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475271 ] Jarek Gawor commented on GERONIMO-2876: --- Lin, There is a reason why there is a split between EJB and POJO containers. In POJO case, we have an access to the service instance and we can do whatever we want with it, e.g. we can instantiate it, inject it with resources, destroy it, etc. However, in EJB case, the EJB container only has access to the EJB instances. All we can do in EJB case is basically pass the requests to the EJB container and let the EJB container invoke the right EJB. That means we can't do things like resource injection and instead we must rely on the EJB container to do that for us. Take a look at the EJBMethodInvoker in CXF code or old Axis1 code to see how the call is forwarded to the EJB container. Btw, I think you are working with a slightly old version of trunk (your plan.xml and config.xml need an update). Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475278 ] Lasantha Ranaweera commented on GERONIMO-2876: -- There was a small missing in usage of org.apache.geronimo.axis2.PortInfo class and I have updated it in the GERONIMO-2877 patch. Hope this will help you too. Initial web service EJB support for Axis2 - Key: GERONIMO-2876 URL: https://issues.apache.org/jira/browse/GERONIMO-2876 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Environment: winxp + sun 1.5 Reporter: Lin Sun Attachments: G2876.patch This work-in-progress patch tried to port the initial web service ejb support from CXF to Axis2 (G2850) and here are a few details: 1) I had a hard time with classexception while working through the two portinfo classes (org.apache.geronimo.jaxws.PortInfo and org.apache.geronimo.axis2.PortInfo) thus I am proposing to get rid of org.apache.geronimo.axis2.PortInfo for simplicities. 2) I decided to keep the old Axis structure instead of the new CXF structure for EJB support, as I envision that all the requests will be handled in one Axis2WebServiceContainer. Able to do a full build with the patch.Tested the patch with jax-ws-ejb test. For CXF, 2 out of 3 pass (same as before the patch). For Axis2, was able to see the ejb module loaded and started. However, get the jaxb error: 22:51:09,906 INFO [JAXBUtils] Both ObjectFactory package-info not found in pa ckage hierachy 22:51:10,296 ERROR [Axis2WebServiceContainer] Exception occurred while trying to invoke service method doService() org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)]; nested e xception is: javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException - with linked exception: [javax.xml.bind.UnmarshalException: unexpected element (uri:http://apache.org/g reeter_control/types, local:greetMe). Expected elements are (none)] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:367) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessa geReceiver.java:147) Will attempt to fix this tomorrow by supplying the generated ObjectFactory package-info classes for jax-ws-ejb test. Please let me know any comments you might have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
