Separate WSDLs or a single WSDL for CRUD functions?

[mskendrick]

I have an architectural question that I would like to ask. First some background: I need to create some webservices that provide basic CRUD functions and are backed by a database. My question concerns the WSDL and whether or not is it best to have a separate WSDL for each of the functions (e.g. create, read, update, delete), or should they all be inside a single WSDL? What are the best practices?

Shannon Kendrick

[Arjen Poutsma]

Well, it depends on whether you want the ability to change them independently. If so, it makes sense to separate them. But I think that's most often not the case.

[res1st]

But it's useful to seperate the xml schema and the wsdl file.
I also have my fault related things (fault types and constants) in a seperate file.

I have an other question regarding the wsdl.
I've wrote the wsdl and manually added the URL of the web service. But if i have an application-server which runs on different machines, so the URL is different (of course ).
Do i have to write my own tool which automatically modifies the WSDL file or has someone before wrote it? Or is a variable available which will be replaced automatically by the server-URL?

Cheers,

Ingo

[Arjen Poutsma]

Do i have to write my own tool which automatically modifies the WSDL file or has someone before wrote it? Or is a variable available which will be replaced automatically by the server-URL?

For now, you have to write your own solution. However, there seems to be much request for this feature, so I think i'll add it somehow before I do a M2.

[res1st]

Thank you Arjen.

[Arjen Poutsma]

I've create a feature issue here: http://opensource.atlassian.com/proj.../browse/SWS-47. Check it out.

[Arjen Poutsma]

And the issue is fixed. Please read the way it works, or check out the echo sample, which uses this functionality.

[res1st]

Very good Arjen, it's looking nice.
As soons as M2 is released, i'll try it. At the moment, i have to fight with JAXB2 and other client WS technologies.

Ingo

[mskendrick]

Arjen,
I tried implementing the WSDL dynamic-location solution using WsdlDefinitionHandlerAdapter, and I ran into a slight problem. Apparently the rewrite of the location URL does not include the web context from the request - only the scheme, host, and port is modified. So if I deploy my WAR file to another web context in my app server, then the new context is not picked up.

WSDL file

<soap:address location="http://localhost:8080/pcc-web/services" />

Actual rewritten WSDL

<soap:address location="https://www.myhost.com/pcc-web/services" />

Expected rewritten WSDL

<soap:address location="https://www.myhost.com/production/services" />

I think that the web context should be updated in addition to the scheme, host, and port. What do you think?

Shannon Kendrick

[res1st]

I think you are right, Shannon. It would be nice if the application context can also be changed.

But how does it work? I did it like in the echo example and i get this log message:

DEBUG handler.SimpleUrlHandlerMapping  - Mapped URL path [/eim.wsdl] onto handler [org.springframework.ws.wsdl.wsdl11.SimpleWsdl11Definition@26fb32]

But if i open my browser and request

http://localhost:8080/eim/eim.wsdl

, i get my unchanged wsdl file.

Cheers,

Ingo