Hi,
I have a large set of existing WSDL describing ~200 business
interfaces, and a set of classes that bind SOAP to the underlying
services and vice-versa.
I'm trying to publish these services through CXF, and so far have had
mixed results
My approach has been to subclass the CXFServlet, and on
Basically I'm aiming at deploying many strongly typed services defined
in the wsdl, but servicing each of them using a generic (existing)
mechanism.
If I declare each wsdl defined service in a then
they load and publish successfully. I've subclassed the service
factory to do things like rename th
that's what i'm looking for - got a url?
On Jan 24, 2008 12:46 PM, Benson Margulies <[EMAIL PROTECTED]> wrote:
>
> >
> > Ideally I'd like to achieve all of this programatically - i.e. without
> > having to knock together a big config file.
>
> All that spring config corresponds to plain old Java
thanks, will give that a go.
On Jan 24, 2008 1:02 PM, Benson Margulies <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2008-01-24 at 12:54 +1000, Rob Barrett wrote:
> > that's what i'm looking for - got a url?
>
> See what the following page does for you. I'm
I'm about to start some data binding code to map soap messages to java
components and I'm looking at the DataBinding interfaces in cxf.
Could anyone point me at a good point of introduction to this
interface/class set. I'd like to find out about the lifecycle of these
things, how/when they are cal
ions, both of the above would need updating for that as well. A
> chunk of jaxb's complexity is around that.
>
> Anyway, I'd definitely recommend looking at the XmlBeans databinding.
> The JAXB databinding does a BUNCH of things that makes it very complex.
>
>
Does anyone have an example of how to create a soap:fault from a
custom exception thrown by a JAX-WS service?
Cheers, Rob
> http://www.jroller.com/gmazza/date/20071019 ? Check steps #4, #6, and
> #10, for the WSDL, service, and client, respectively.
>
> HTH,
> Glen
>
> Am Donnerstag, den 07.02.2008, 07:50 +1000 schrieb Rob Barrett:
>
> > Does anyone have an example of how to create a soap:fault fro
e the @WebFault annotation will help
> you. Google or wait for someone here more knowledgeable. I don't know
> much about that annotation.
>
> Glen
>
> Am Donnerstag, den 07.02.2008, 14:20 +1000 schrieb Rob Barrett:
>
> > Thanks Glen.
> >
> > H
Is it reasonable to use a ThreadLocal for holding request specific
metadata? i.e. are there cases where CXF can use more than one thread
to handle a request or where CXF handles more than one request on the
same thread?
Or does this just depend on the configuration of the container e.g.
tomcat/jet
10 matches
Mail list logo