[
https://issues.apache.org/jira/browse/GERONIMO-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-4430.
-----------------------------------
Resolution: Invalid
Assignee: Jarek Gawor
First of all, please use the user mailing list ([EMAIL PROTECTED]) for asking
questions like these.
A.1) If you are using Jetty assembly and if you are deploying an application
with its own CXF jars than yes, you will need to disable CXF in Geronimo.
That's needed for example to prevent CXF version conflicts (Geronimo 2.1 uses
CXF 2.0.x while your application seems to be using CXF 2.1).
A.2) You mean the @EJB injection? If you convert your application to use the
standard Java EE 5 deployment descriptors, etc. the @EJB injection will work
right. However, if your application uses CXF-specific deployment descriptors
you have to look at CXF documentation on how to do that.
> JAX-WS webservice development in Geronimo-Tomcat Assembly with CXF 2.1
> ----------------------------------------------------------------------
>
> Key: GERONIMO-4430
> URL: https://issues.apache.org/jira/browse/GERONIMO-4430
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.1
> Environment: Spring 2.5 + CXF 2.1
> Reporter: kishore
> Assignee: Jarek Gawor
>
> Q.1) To implements JAX-WS webservices using Spring + CXF , does it required
> to turn on CXF engine in Geronimo ?
> Q.2) How to inject a business implementation bean to webservice pojo.
>
> Facing problem like, all setter injection are set properly in webservice pojo
> bean when spring context loaded. But at the time webservice contracts
> invocation all injected bean are referring to null. Due to this
> NullpointerException occurring.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
