[
https://issues.apache.org/jira/browse/CXF-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559734#action_12559734
]
Marinó A. Jónsson commented on CXF-1390:
----------------------------------------
Actually, I'm running CXF 2.0.3 with Spring 2.5.1 on Jetty 6.1.6 (using
CXFServlet and jaxws:endpoint Spring configuration) without a hitch!
However, deploying the exact same war on a Geronimo Little-G 2.0.2 (packing
jetty 6.1.5) produces this dreaded UnsatisfiedDependencyException.
In both cases I'm using Java 6.
<rant>
The reason I use Little-G rather than the full size version is that I still
haven't found a way past classloader conflicts - if I include the CXF libs it
complains about the jaxws NamespaceHandler, and if I exclude the CXF libs it
complains that it can't find the CXFServlet. I've tried turning off the the
cxf-module and cxf-deployer system modules, and hundreds of other deployment
variations - but to no aval. Deploying Spring-less (as per Geronimo's "Simple
Web Service with JAX-WS" example) seems to work though - but of course that
doesn't do me any good :)
</rant>
cheers,
Marino
> Upgrade to Spring 2.5
> ---------------------
>
> Key: CXF-1390
> URL: https://issues.apache.org/jira/browse/CXF-1390
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.3
> Reporter: Dan Diephouse
> Fix For: 2.0.4
>
>
> CXF doesn't work correctly on Spring 2.5. For instance, you get this:
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jrulesService': Unsatisfied dependency expressed
> through constructor argument with index 2 of type
> [org.apache.cxf.jaxws.JaxWsServerFactoryBean]: Ambiguous constructor argument
> types - did you specify the correct bean references as constructor arguments?
> (What ever happened to the famed backward compatability!? :-) *sigh*)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
