+1  I think this is a little more intuitive.

-Nick





"Davanum Srinivas" <[EMAIL PROTECTED]> 
03/21/2007 05:37 AM
Please respond to
axis-dev@ws.apache.org


To
axis-dev@ws.apache.org
cc

Subject
Re: [Axis2] Wsdsl inside service aar file






Deepal,

I think we should consider adding the wsdl name in services.xml
instead of trying to do this. If nothing is specified then we do what
we do now scanning the wsdl's. I definitely don't think we should
switch to your proposal at this late juncture.

thanks,
dims

On 3/21/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi All;
>
> At the moment we have small issues with the way we handle wsdl files in
> the META-INF directory. What we are doing is load all the wsdl inside
> the META-INF and then make AxisServices out of them , next read
> services.xml and from that pick the required AxisServices (and throw the
> remaining services , if it not referenced by services.xml) it seems to
> me that it is bit inefficient . Therefore I am thinking of improving
> that a bit as mentioned below;
>
>     *
>
>       If user has only one wsdl then he can name his wsdl as
>       srevices.wsdl and put that into META-INF directory.
>
>     *
>
>       If user has wsdl with multiple service element still he can name
>       the wsdl file as services.wsdl and put into the META-INF 
directory.
>
>     *
>
>       In all the other cases (where user has multiple wsdl) then he can
>       name them with the services name , for example if the service name
>       if foo then you can put wsld called foo.wsdl into META-INF
>
> So with this approach user can easily associate wsdl and AxisService.
>
> thought and comments .....
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to