literature and questions

[res1st]

Hi,

i want to learn more about top-down development and need information about writing WSDL documents. It would be nice if Spring-WS would provide a list of good links, tutorials or literature recommendation to learn WSDL.

After i've wrote my WSDL file, what's the next step in Spring-WS to create a Web Service?

• Does Spring-WS provides a Server-Skeletion Generator?
• Does Spring-WS always need other technologies like Axis or XFire? Or has it his own SOAP-Stack?
• Is Spring-WS somehow focused on web/html applications or is it neutral and also for fat clients?

Cheers,

Ingo

[Arjen Poutsma]

i want to learn more about top-down development and need information about writing WSDL documents. It would be nice if Spring-WS would provide a list of good links, tutorials or literature recommendation to learn WSDL.

That is a good idea, I will try and add some links to the main Spring-WS page. For starters here is a list which helped me on my way:

• Which style of WSDL should I use?
• Web Services Platform Architecture, a great book on the various WS-* standards.
• SOAP 1.1 spec,
• WSDL spec,
• WS-I Basic Profile defines do's and don'ts for your web services

Does Spring-WS provides a Server-Skeletion Generator?

Not yet. There are ideas for generating a Spring bean definition file from a wsdl. There is no way to generate a Java stub from a WSDL, for reasons I explained here.

Does Spring-WS always need other technologies like Axis or XFire? Or has it his own SOAP-Stack?

It is based the central concept of a WebService, or the sub interface SoapMessage. Currently, there is only implementation for that interface: SaajSoapMessage, which is based on the SOAP with Attachments API for Java (SAAJ).

So, no, you don't need any other dependencies. It is based on J2EE 1.4 standards.

Is Spring-WS somehow focused on web/html applications or is it neutral and also for fat clients?

I am afraid I don't understand the question. Could you elaborate a bit?

Thanks for the interest!

[res1st]

Thank you very much for your answers!

Is Spring-WS somehow focused on web/html applications or is it neutral and also for fat clients?

I am afraid I don't understand the question. Could you elaborate a bit?

You said in another post, that Spring-WS is "based on Spring-MVC". So i thought that Spring-WS is maybe strongly related to browser-applications.

[Arjen Poutsma]

You said in another post, that Spring-WS is "based on Spring-MVC". So i thought that Spring-WS is maybe strongly related to browser-applications.

Ah, I see. What I meant was that the architecture and design are based on Spring-MVC. If you have ever used Spring-MVC, you will see a lot of similarities, and in the near future, you can even reuse the binding and validation code.

But this is only on a design level. You don't need Spring-MVC to use Spring-WS, and it is not related to browser-apps at all.

[Arjen Poutsma]

Here are some more links, courtesy of W3 Schools:

• SOAP
• WSDL

In general, W3Schools is a great, pragmatic resource for learning anything about XML and related technologies.

[res1st]

Thank you!
You should add the links to the spring-ws homepage and/or to the documentation.