A WSDL is a contract, and changing this often is not the correct thing to do. Changing the service contract often goes against the fundamentals of the SOA paradigm.
Someone may be able to suggest a better solution if you could explain the problem you are trying to solve (not the way you intend to solve it) HTH Azeez On Thu, Feb 28, 2008 at 5:48 PM, Kanchana Welagedara <[EMAIL PROTECTED]> wrote: > Hi All > > > I got use case where i don\t have a static wsdl but want a DII client > invocation.I\m planing to use Axis2 .Earlier i used for static wsdl using > proxy generators .But this time I can\t use proxies.In further I get a > WSDL file that defines message based SOAP calls. The payload message is > defined in XML Schema. It can contain any number of complex types.TheSchema > should be displayed in the "Creater"(Creater where we make the xml > definition for particular web flow ) and the user should be able to link > variables/items in Spikeflow(www.nspike.com/) to elements/attributes in > the schema. Then in running our runtime should be able to create correct > SOAP requests to send and be able to parse SOAP responses. > > Normally we would do this by generating java objects with JAXB that > > maps to the Schema. But we can't do the JAXB and compilation step, > > since the WSDL and Schema changes. > > Really appreciate if any one can shoot any ideas on this > > Thanks a lot > Kanchana > > > -- Thanks Afkham Azeez http://azeez78.blogspot.com http://www.wso2.org GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
