I am already using filtering mechanism. I filtered targetnamespace for both the WS service and WS types. However, I realized that in case of reusable service it will make it actually less reusable on the client side - f.e. namespace change will require regeneration of mapping classes. So I removed filtering for namespace for types. Now types are all the same across different installations (each installation for different client). However, since the NS for porttype varies across installations then such service is again not reusable. And I am having different NS for portype because I want different NS for service and port - and there is no way to define in wsdl a porttype in NS=a and service and port in NS=b, is there?
So now I think the only way is to instead of varying the namespace, changing the service and port name - f.e. by adding a customer id as a suffix. So types and porttypes will be the same for all installations. However, service and port will be different - although in the same namespace. So the client will not need to regenerate mapping classes - it only needs to know service and port name for each installation. Hope, I was clear :) BTW, I would like to have different names for the same service but in different installation file to have the possibility to deploy two customers on the same ServiceMix without name conflicts. Maybe you know better way. tx Michal gnodet wrote: > > Then, what about using maven filtering mechanism ? > I've blogged about that some time ago: see > http://gnodet.blogspot.com/2007/03/using-maven-to-switch-runtime.html > You must ensure that the filtering occurs before wsdlgen ... > > Cheers, > Guillaume Nodet > > > On Aug 22, 2007, at 10:48 AM, Michal wrote: > > > > -- View this message in context: http://www.nabble.com/jsr181-endpoint---overriding-service-name-that-comes-from-wsdl-tf4310068s12049.html#a12272211 Sent from the ServiceMix - User mailing list archive at Nabble.com.
