Apparently what I am looking for is xformat:binding in the WSDL
(xmlns:xformat="http://cxf.apache.org/bindings/xformat";).
Where is this documented?
Dan Connelly wrote:
Thanks Andrea:
The code and the sample you suggested did the trick.
However, I have another question: Can CXF marsha
Daniel Kulp <[EMAIL PROTECTED]> writes:
> Generally, if you run "mvn -X" it will spit out a TON of stuff. One
> thing it spits out is a dependency tree where you can see what is
> including what.
Thanks. I was trying to stop the JAXB artifacts from being included so
that I could see how a system
Daniel Kulp wrote:
The last option would be to make the "Destination" stuff in http
plugable. The jetty stuff just provides a HttpDestinationProvider or
something into the http module. Jetty wouldn't subclass the http
factory or anything. It just provides functionality into the existing
h
On Sunday 06 May 2007 12:57, Steven E. Harris wrote:
> Footnotes:
> ¹ Does anyone know of a way to trace the root cause of a dependency in
> Maven? That is, find which artifact cites the dependency directly?
Generally, if you run "mvn -X" it will spit out a TON of stuff. One
thing it spits ou
> But is the idea here that a client would fetch this WSDL document from
> some remote server, or that it will have a WSDL document bundled up,
> say, in its JAR?
> I ask because fetching the WSDL from a remote server would add one
> network round-trip to every client's start-up sequence.
If this
