geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-2876) Initial web service EJB support for Axis2
Date Fri, 23 Feb 2007 05:40:05 GMT

    [ 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.


Mime
View raw message