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 Mon, 10 Dec 2012 16:33:21 GMT


Timothy Heider commented on CXF-4325:

I am using jboss-as-7.1.1.Final

I have my system working with CXF now including the JS integration but I was never able to
get ?js function working.  It took me a while to understand that JBoss includes its own CXF
and that it is a bit outdated compared to what is current in the CXF project. 

I met my requirement by having my Maven build render the JS client interfaces with the plugin.
 The WSDL's are rendered with Maven too and both JS and WSDL are provided as simple HTTP documents.

JBoss 7.1 is very different from something like Tomcat or Jetty.  They are very stripped down
web servers.  JBoss actually works great with CXF but you have to figure out some little tricks,
like how to get the ServletContext (for loading resources, etc) and also how to get the JS
client working with Maven so it's portable. 

You can close this issue.  Thanks for your response.
> 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
For more information on JIRA, see:

View raw message