You have pinpointed a key issue with any JMS binding - how do you specify connection information? The working group has come to the conclusion that it may be useful in some scenarios to specify the JNDI information, although it is clearly not generally useful in all circumstances.
I just read “SOAP over Java Message Service 1.0”. I am very happy with this working group which will deliver standard for JMS transport for SOAP messages.
All specifications (I found) at this moment are vendor specific on some why. In many usages of JMS as transport I saw not correct usage of JMS properties in WSDL. I think this draft is making the same mistake.
From my point of view, a WSDL file:
- describes a services interfaces and binding …
- is developed and delivered by Servcie Provider.
- doesn’t contain any portion of data specific for one of clients (Service Consumer). So no client specific information in WSDL. This is only way to deliver one WSDL and publish it in Service Repository. If client information is embedded in WSDL, Service Provider has to deliver one WSDL per client (Service Consumer).
In your specification, there is possibility to specify following properties in WSDL:
Both are client configuration.
I see following problem: Service Provider can’t develop one WSDL for all Service Consumers. Service Provider can’t develop one WSDL per client because he/she doesn’t know client specific configuration. Or is your idea that Service Provider develop WSDL without JMS binding specified and any Service Consumers (clients) add it’s JMS binding to it’s version of WSDL file.
Thank you very much for this specification work.