This is one of the “issues” I have with JAX-WS. The “interface” that is
generated is supposed to be completely generated from the portType. Thus, it
does not know from the portType that this is 1.1 or 1.2. The SOAPBinding
annotation should only go on the actual service object which wou
Note that there was a mistake in my first mail: see 2.6.7 and not 1.6.7!
Le 17/03/2014 15:05, Michel Labarre a écrit :
Hello
Really, no one has this problem? I have the same problem with version
2.6.13.
thank you
Le 14/03/2014 15:40, Michel Labarre a écrit :
Hello
We running CXF 1.6.7 versio
Hello
Really, no one has this problem? I have the same problem with version
2.6.13.
thank you
Le 14/03/2014 15:40, Michel Labarre a écrit :
Hello
We running CXF 1.6.7 version with SOAP 1.1 wsdl. All run fine.
New services are required with SOAP 1.2. I run the Web Service
generator under eclip
Hello
We running CXF 1.6.7 version with SOAP 1.1 wsdl. All run fine.
New services are required with SOAP 1.2. I run the Web Service generator
under eclipse to generate all classes from WSDL.
Generation works fine but when I test with SOAPUI on the newly installed
server I obtain a fault with th
will be deployed to.
>
> Try something like this:
>
>-wsdlLocation
>
> http://path/to/your/wsdl
>
> Andrew.
>
>
--
View this message in context:
http://www.nabble.com/wsdl2java-question-tp21354597p21354914.html
Sent from the cxf-user mailing list archive at Nabble.com.
2009/1/8 brian_beech :
>
>
>
>${basedir}/src/main/wsdl/School.wsdl
>
>
>
e wsdl will be deployed to.
Anyone have any suggestions for configuring/working around the local file
being referenced in the generated class?
Thanks,
--
View this message in context:
http://www.nabble.com/wsdl2java-question-tp21354597p21354597.html
Sent from the cxf-user mailing list archive at Nabble.com.
This is a JAXB thing.There is a jaxb customization that can be used to
control it.
See section 7.5.1 of the JAXB spec for more details.
Dan
On Wednesday 15 October 2008 10:16:27 am Segal, Jeffrey wrote:
> Hello,
>
> I believe wsdl2java is "optimizing" its schema translation against my
>
Hello,
I believe wsdl2java is "optimizing" its schema translation against my
will, so I was wondering if there is a way to turn that off. It's
essentially changing this:
to this:
protected BigInteger identifier;
instead of this:
protected WrapperType identifier;
This may be
Thanks for the Howto. Basically the problem was that I used ParameterStyle.BARE
in my webservice.
With wrapped parameters the interface looks ok and uses generics as you said.
Thanks,
Fabian
Original Message
Subject: Re: WSDL2Java question: Wrapped Lists (01-Okt-2008 23:47
You should take a look at this Howto:
http://cwiki.apache.org/CXF20DOC/defining-contract-first-webservices-with-wsdl-generation-from-java.html
The service gnerated here will have plain lists that make nice use of
generics.
Greetings
Christian
The generated CustomerService looks like this:
@
Hello,
I'm developing a web service with the java first approach. My domain
model contains Hibernate annotations.
As I don't want to share them with my webservice client, I thought it
might be a good idea to use wsdl2java to generate a seperate model for
the client which has no Hibernate annotatio
12 matches
Mail list logo