[
https://issues.apache.org/jira/browse/CXF-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-3957:
-----------------------------
Fix Version/s: NeedMoreInfo
We'd definitely need more information about this and likely a test case of some
sort. It sounds like it's a classloader issue which can easily be affected by
the deployment environment. For example, if you have a jaxws-api jar in your
bundle and the deployment environment also provides one, you could have two
different javax.xml.ws.handler.Handler classes loaded into the runtime and we
would not be able to cast from one to the other.
> Cannot convert to javax.xml.ws.handler
> ---------------------------------------
>
> Key: CXF-3957
> URL: https://issues.apache.org/jira/browse/CXF-3957
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: pavlos
> Labels: cxf, jboss, services, spring, web, xts
> Fix For: NeedMoreInfo
>
>
> I am trying to run a ws-transaction web service scenario. I follow the wsdl
> to java approach using CXF with maven within eclipse. At some point i need to
> register a jax-ws handler chain. More specifically, the handler chain has got
> one soap handler, namely the jboss arguna
> "com.arjuna.mw.wst11.service.JaxWSHeaderContextProcessor" which implements
> the javax.xml.ws.handler. However when i try to deploy my service it throws
> the following exception:
> Cannot convert value of type
> [com.arjuna.mw.wst11.service.JaxWSHeaderContextProcessor] to required type
> [javax.xml.ws.handler.Handler]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
