You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Matthew Inger <ma...@gmail.com> on 2010/02/15 22:51:06 UTC

Use of JAX-WS front-end

I'm wondering if anyone can help out here, but I've run into roadblocks with
everything i've tried related to using the JAX-WS frontend.

I first started out by deploying the singlebundle dosgi-1.1 distribution
into spring dmServer 2.0.0, which went off without any issues.  I then
created a web service
which was backed by a hibernated based java service (using an hsqldb memory
db for now).  The generated wsdl with the default bindings did not suit my
needs,
so i started out by switching the data binding to jaxb, which worked just
fine:

      <entry key="org.apache.cxf.ws.databinding" value="jaxb" />

Still, the wsdl was quite there, as it all the method parameters had
arguments like "arg0" and "arg1".  So i switched the front end to "jaxws",
and annotated the
service interface appropriately:

      <entry key="org.apache.cxf.ws.frontend" value="jaxws" />

@WebService
@SOAPBinding(style=Style.RPC, use=Use.LITERAL)
public interface WidgetWebService {
    @WebMethod
    void addWidget(@WebParam(name="widgetData") WidgetData widgetData);
}


At this point, the wsdl coming out of cxf was now completely devoid of any
operations, and was still ocuing document style bindings (instead of the
requested RPC style).
I did some research which suggested this was a problem with the packaging of
the singlebundle distribution.

So i figured I'd give the multibuild distribution a try.  With no
instructions for dmServer, I tried anyway by setting up a seperate
repository directory, and starting up the cxf
bundles, which wasn't too difficult.  However, when I stry to start my web
service, with or without jax-ws, i get this error:


org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Unable to locate Spring NamespaceHandler for XML
schema namespace [http://cxf.apache.org/policy]

which I can't seem to get past.

So, at that point, I figured, let me give the 1.2-SNAPSHOT a try.  So i
cleared everything out, and started over, deployed the singlebundle
1.2-SNAPSHOT distribution, which
seemed fine. Deploying my bundles went fine, but after deploying my bundles,
no webservice was available, nothing was reported in the error log, and
there was nothing listening
(according to netstat) on the requested port.


Any help here would be appreciated.  My requirements are as follows, which
I'm sure are not any different from what most people have been implementing:

1.  JaxWS frontend
2.  JaxB binding
3.  WS-Security integration (which I have not even seen any information on
in relation to dosgi, which is something that i'm a little surprised about).
4.  Spring 3.0.x
5.  Spring DM 2.x
6.  Hibernate 3.3.x

I would be willing to consider a switch to apache felix or any other
container if that will meet my requirements, and I can get dosgi to work
properly in another container.

Thanks in advance for any help.