Skip to main content

JAX-WS support for Http bindings

2 replies [Last post]
denian
Offline
Joined: 2009-02-27
Points: 0

Hi,

We are developing a product using web services and we generate the code from a WSDL. We already posted some questions (http://forums.java.net/jive/thread.jspa?messageID=332409&#332409) and now we are able to publish a server with multiple bindings but only using Soap 1.1 or Soap 1.2. An example of our service would be:

We extend WSServlet and create a WSEndpoint for each binding but when we try to publish an endpoint using Http binding it doesn't work. We've been checking the implementation and it seems like Http binding (http://www.w3.org/2004/08/wsdl/http) is not supported. In addition, we've noticed that, when we build a wsdl model from WSDLModeler, the port of the Http binding has a null address.

Are we doing something wrong? Any help will be appreciated.

Thanks in advance.

Daniel

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Glen Mazza

Do you actually *need* the HTTP binding--AFAICT it's kind of rare today[1],
both client- and service-side.

Glen

[1] http://www.nabble.com/Name-that-Web-Service-tt16993337.html#a16993337

metro-3 wrote:
>
> Hi,
>
> We are developing a product using web services and we generate the code
> from a WSDL. We already posted some questions
> (http://forums.java.net/jive/thread.jspa?messageID=332409&#332409) and now
> we are able to publish a server with multiple bindings but only using Soap
> 1.1 or Soap 1.2. An example of our service would be:
>
>
> > binding="service:ServiceSoap11Binding">
>
>

> > binding="service:ServiceSoap12Binding">
>
>

> > binding="service:ServiceHttpBinding">
>
>

>

>
> We extend WSServlet and create a WSEndpoint for each binding but when we
> try to publish an endpoint using Http binding it doesn't work. We've been
> checking the implementation and it seems like Http binding
> (http://www.w3.org/2004/08/wsdl/http) is not supported. In addition, we've
> noticed that, when we build a wsdl model from WSDLModeler, the port of the
> Http binding has a null address.
>
> Are we doing something wrong? Any help will be appreciated.
>
> Thanks in advance.
>
> Daniel
> [Message sent by forum member 'denian' (denian)]
>
> http://forums.java.net/jive/thread.jspa?messageID=334285
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
> For additional commands, e-mail: users-help@metro.dev.java.net
>
>
>

--
View this message in context: http://www.nabble.com/JAX-WS-support-for-Http-bindings-tp22252186p222574...
Sent from the Metro - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
For additional commands, e-mail: users-help@metro.dev.java.net

denian
Offline
Joined: 2009-02-27
Points: 0

Hi,

I've read your post and that's exactly the binding that I'm talking about: HTTP
GET/POST binding. The thing is that one of our clients has defined that binding in his WSDL. But I guess we will have to use only Soap 1.1 and 1.2.

Thank you very much for your answer.