Hi Devs, I believe we are still working on WSDL support. But, even if we do, is this possible without hot-deployment?
Thanks, Senaka > Hi All, > > I have a requirement to support dynamically generated wsdls. Each wsdl > will contain a core set of operations, but will then have additional > operations defined. I want to use the wsdl with the core set of > operations as my service in Axis2C, but then write code in my invoke > method that will know about the additional new operations as they will > follow a standard pattern. > > My question is, how can I get Axis2C to forward the request to my invoke > method, for operations that are not in the services.xml file? > > In services.xml could I somehow use wildcards? Like this: > > <operation name="Update*"> > <parameter name="wsamapping">\"\"</parameter> > </operation> > > So then a custom wsdl file would be given to a client and it could have > operations like "UpdateFoo" and "UpdateBar", which are not in the > services.xml, but the "Update*" could match them. Then in my invoke > method I could analyze the operation name and know what to do with it > (e.g. "UpdateFoo" would tell me to use "Foo" logic and I would know how > to handle that). > > The purpose for this is ease of use to the client. We have many > operations that are generalized, but if I can generate new wsdl to do > specifically what the user is trying to do, they can use these custom > operation names directly. This will result in greatly increased > usability. > > I think most of the work is on the service in my code, but I need a way > to tell Axis2C to forward along the request even if it is not in the > known set. Is there a way to do this, or is there a way to modify the > code to support this? > > Thank you much, > > -Dave. > > > ********************************************************************** > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > Any unauthorized review, use, disclosure or distribution is prohibited. If > you are not the intended recipient, please contact the sender by reply > e-mail and destroy all copies of the original message. > ********************************************************************** > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]