When you think of sharing such information in wsdl you should always
take into account that you typically have several stages in a company
develeopment environment.
So you either have to provide one endpoint per stage (e.g. dev, test,
prod) or you only provide an endpoint for dev.
I mostly opted for the last option. So the jms information in the wsdl
was there to document e.g. the queue name but in the code the jms
server, queue name, ... were set in spring and used placeholders. So the
admin could change the setting at deployment time or even at runtime.
Christian
Am 29.04.2011 11:18, schrieb [email protected]:
Thanks to Both of you.
I am done with the client generation, able to invkoe web method.
But I don't have the way so that WSDL can viewable with web service
consumers.
So what I am thinking is like,
Share WSDL with Http transport and JMS JNDI URI path with the web service
consumers, so that they can invoke web service using JMS. but modify the
endpoint for JMS.
Need you thoughts and suggetions.
Thanks.
Harshal--
View this message in context:
http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4358299.html
Sent from the cxf-dev mailing list archive at Nabble.com.
--
----
http://www.liquid-reality.de
