> -----Original Message----- > From: Simon Nash [mailto:[email protected]] > Sent: Sunday, December 04, 2011 7:27 PM > To: [email protected] > Subject: Re: Dynamic service references ? >
> I've checked in a fix to the 1.x trunk that should handle this scenario > for both serialization to XML and Java serialization. There's no > change > to the external API for serializing and deserializing service > references. > > I'm leaving TUSCANY-3984 open for now until we're satisfied that the > fix > works for all the required cases. > > Simon Thank you very much for the fix. I have checked out the current trunk and experimented with it. I am glad that serializing service references now works. But I still have two related questions with regard to using this feature for the purpose of introducing dynamism: 1. When I specify the uri attribute on the binding.ws instead of the wsdlElem, that gets replaced by the wsdlElem in the serialized form. Is that intentional? 2. What is the intended behaviour when I specify BOTH the wsdlElem and uri attributes? Shouldn't the explicit uri override the uri retrieved from the wsdl? However, that is not what seems to happen. In terms of creating a dynamic endpoint, it guess it would be easiest if one could just add an overriding uri to the serialized form. The wsdl file is static after all, and dynamically replacing only that wsdlElem in the XML wouldn't be enough. I may be missing something here. -- Sebastian IDS Scheer Consulting GmbH Geschäftsführer/Managing Directors: Kamyar Niroumand, Ivo Totev Sitz/Registered office: Altenkesseler Straße 17, 66115 Saarbrücken, Germany - Registergericht/Commercial register: Saarbrücken HRB 19681 http://www.softwareag.com
