The best practice is to put the wsdl file into service archive file .
100% correct. Wouldn't it be cool to generate ?wsdl/?xsd if MR is *RPCMessageReceiver, when the service object supplier is "ServiceObjectSupplier"
>
> Current Axis-spring module has SpringAppContextAwareObjectSupplier and
> SpringServletContextObjectSupplier would has it own scope and imho we
> have to write a applicationContex.xml according to them and it's
> pretty restrictive. Thus, naturally i want to write my own supplier
> with it's own helper parameters.
What do you mean by it has its own scope , is it different from our four
session scope ?
Oh no. I didn't mean that. Sorry. For Ex; SpringServletContextObjectSupplier specialized in embedded version (war). Here, it expect to have spring.xml from web.xml. Now if some one wants to deploy a another spring related service to a running axis2.war instance with a completely different applicationContext.xml, is hot deployment really happen ?. These is what i meant by scope, Its limitations.
>
Saminda , with your change any one how write spring need to implement
the new interface ?
Oh no. They can simply use the available Supplier classes. Users really don't have to worry about it.
But if any user want to plug another framework to Axis2 to supply service objects, the service object supplier has to implement the proposed interface, otherwise the deployment engine wouldn't recognize it as a service object suppler and ignores it. Wouldn't that be fair enough ?
Saminda
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
