cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Heider (JIRA)" <>
Subject [jira] [Commented] (CXF-4325) ws?js not working with Spring based config in JBoss 7.1
Date Fri, 25 May 2012 17:46:23 GMT


Timothy Heider commented on CXF-4325:

I have done more work on this.  Your idea is correct: it has something to do with classloaders
in JBoss.

JBoss 7.1 has cxf 2.5.2 embedded in it.  When I change my CXF version to 2.5.2 (in my project)
and make it "provided" a lot of errors go away in my log during deployment.  Looks like I'm
using 2.5.2 because that's what JBoss provides.  Does that support ?JS ?

I have never had a good understanding of how the hierarchical loader works in JBoss.  I am
learning about this now and starting to understand this issue better.

I am also having problems with my JAXWS service getting autowired by Spring.  This is related
to the same issue (Classloaders).  Spring needs access to WebApplicationContext and JAXWS
is in some other ClassLoader "space".

I will comment on this issue after I make more progress.  I want to explore how to control
ClassLoaders in JBoss in deployment and also see what happens when I put Spring and CXF into
the common/lib folder of the server.

> ws?js not working with Spring based config in JBoss 7.1
> -------------------------------------------------------
>                 Key: CXF-4325
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JavaScript Client, JAX-WS Runtime
>    Affects Versions: 2.6
>         Environment: Linux + JBoss 7.1
> project in Netbeans 7.1.2.  Simple WAR (clean project)
>            Reporter: Timothy Heider
>            Priority: Minor
>             Fix For: NeedMoreInfo
> I have everything working except for the one thing I really want: ?js code rendering.
 It returns this:
> <soap:Envelope xmlns:soap="">
> <soap:Body>
> <soap:Fault>
> <faultcode>soap:Server</faultcode>
> <faultstring>
> No such operation: null (HTTP GET PATH_INFO: /pbx/pbxnull)
> </faultstring>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
> which is the same as if the JS wasn't hooked in at all.
> Here is my beans.xml file:
> <beans xmlns=""
>       xmlns:xsi=""
>       xmlns:jaxws=""
>       xmlns:jaxrs=""
>       xsi:schemaLocation="
>   <import resource="classpath:META-INF/cxf/cxf.xml"/>
>   <import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
>   <import resource="classpath:META-INF/cxf/cxf-extension-javascript-client.xml"/>
>   <jaxws:endpoint id="pbx"
>       implementor="realise.pbx.core.PbxCoreImpl"
>       address="/pbx"/>
> </beans>
> I am able to get wsdl's by ?wsdl and execute services using JaxWsProxyFactoryBean.
> The beverages sample works with the same jar's to generate JS so I know the feature works.
 I'm somewhat baffled.  I built the 2.6.0 source today but I thought before I dig in too much
more I would see if you knew about something like this already being a problem.
> Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message