I'm still not sure I understand what you mean by "work with dynamic WSDLs".
On the client side, Axis supports a dynamic invocation interface so it can dynamically figure out how to invoke a service that it didn't know about before. On the service side, Axis needs to know in advance how to map incoming messages to class methods (defined using a WSDD). As I said, I don't know how to make it dynamically expose new services. Anne On 8/2/05, Saqib Rasul <[EMAIL PROTECTED]> wrote: > By "Moving to Axis" we would like to shift these items from our control to > the control of Axis: > > - SOAP request/response > > Axis also seems to do much better error handling in ensuring the SOAP > messages are SOAP compliant and that is something we want to include in our > web app. > > Our aim in replaceing our WS implementation with AXIS would be to let AXIS > take care of the plumbing and validating the SOAP messages. Also since AXIS > provides a standard WS implementation, and if we decide to publish/create > further WS, would rather do them with AXIS. > > We did start with a WSDL first as you suggested and then tuned the WS to > ensure WS-I compatibility. But now creating with implementation more WS we > would rather not be reinventing the wheel. > > I guess my question is how to configure axis to the above mentioned things > (handle the SOAP messages and take care of the plumbing) and weather AXIS can > work with a dynamic WSDLs. > > I hope you can understand what i mean... > > Many thanks in advance. > > Regards, > > Saqib > > > -----Ursprüngliche Nachricht----- > > Von: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > > Gesendet: Tuesday, 2 August 2005 1:36 PM > > An: axis-user@ws.apache.org > > Betreff: Re: Axis to handle already existing WS implementation > > > > Please explain more about your situation. > > > > What do you mean by "moving to Axis"? What would you like to > > use Axis for? > > > > Axis performs > > - WSDL generation > > - SOAP request/response > > - Document/literal style services > > > > So does that mean you would like to replace you current WS > > features with Axis? > > If so, you'll need to make some changes to you current web app. > > > > Axis supports WS generation from WSDL or from Java. As a best > > practice to ensure better interoperability, it's better to > > generate the WS from WSDL. Capture your dynamically generated > > WSDLs and use them to generate your WSs. Then replace your > > current WS infrastructure with Axis, and direct Axis to > > invoke the appropriate application code when requests come. > > > > If that isn't possible, then use your current application > > code to generate the WS and the WSDL. > > > > If you asking whether you can dynamically expose web services > > with Axis, I don't know if it can do that. > > > > Anne > > > > On 8/2/05, Saqib Rasul <[EMAIL PROTECTED]> wrote: > > > Hello all, > > > > > > We have several WS features already implemented into out Web App: > > > - WSDL generation > > > - SOAP Request/Response > > > - Document Literal style WS and WSDLs > > > > > > Our WS and WSDLs are WS-I compliant. > > > > > > And are now thinking of moving to AXIS. From axis documentation it > > > seems that axis is helpful to create Client/Server Java stubs for > > > handling WSDLs. The problem that we have is out WSDLs are generated > > > dynamically for an "information Container", so its useless generate > > > Cleint/Sever java-stubs. > > > > > > Can someone point out some documentation on how to work > > with AXIS if > > > the WSDLs are unknown/dynamic. In other words how can we still hook > > > into the AXIS system with dynamic WSDLs? > > > > > > Many thanks in advance, > > > > > > Regards, > > > > > > Saqib > > > > > > > > -------------------------------------------------------------- > > ---------- > > > SAGA D.C. GmbH Phone : +49 (0) 6731-9428-0 > > > Berliner Strasse 73 Fax : +49 (0) 6731-9428-26 > > > D-55232 Alzey > > > mailto:[EMAIL PROTECTED] http://www.sagadc.de > > > > > > > > > > >
