Taken from the JAX-WS 2.0 specs, section 5.2.5.3:
anonymous wrote :
|
| Use of @WebService(wsdlLocation) and Metadata
|
| There are some restrictions on the packaging of the description and any
associated metadata documents.
| The goal of these restrictions is to make it possible to
Thanks!!!
I will post this issue as a bug.
//Oskar
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031470#4031470
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031470
___
The JSR181 specification (http://jcp.org/en/jsr/detail?id=181) says in 4.1
Annotation: javax.jws.WebService:
anonymous wrote : wsdlLocation:
| The location of a pre-defined WSDL
| describing the service. The wsdlLocation is
| a URL (relative or absolute) that refers to a
| pre-existing
Hi!
Thanks for your help. I'm sorry to say, that is not what I actually need or do.
I want to have control over my contract (the WSDL-file). That is why I'm using
contract first development. I have external parts using my services
(contracts). Therefore generated contacts is not a good
You shouldn't have to create WSDL files at all. If you're using annotations
and jbossws-1.2 then the WSDL is created and published during deployment
whenever the deployer spots a @webservice. v. easy!!
simply navigate to
http://localhost/jbossws/services
to see which endpoints were detected
