axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe" <dee...@opensource.lk>
Subject Re: Using the WSDLService in the registry[continuingRE: [Axis2][Engine]Step by Step;Engine, Engine registry deployment and the Phase Resolver]
Date Wed, 08 Dec 2004 06:39:34 GMT
hi all;

+1 for keeping ServiceDesc (rather *Desc classes) under the package
  org.apache.axis.description

if we use
org.apache.axis.registry

for the deployment module and for the PhaseResover we have to import
"org.apache.axis.registry" package, and I feel it is not so
nice but if we use  "org.apache.axis.description"  that is better.

Boz EngineRegistry is not the only one who is going to use ServiceDesc and
both the Deployment and PhaseReolve are going to use that we
can keep that under;
  org.apache.axis.description

Thanks

Deepal.

----- Original Message ----- 
From: "Srinath Perera" <hemapani@gmail.com>
To: <axis-dev@ws.apache.org>
Sent: Wednesday, December 08, 2004 12:28 PM
Subject: Using the WSDLService in the registry[continuingRE:
[Axis2][Engine]Step by Step;Engine, Engine registry deployment and the Phase
Resolver]


> In the EngineRegistry [see the old thread RE: [Axis2][Engine]Step by
> Step;Engine, Engine registry deployment and the Phase Resolver]
>
> A) how the Service is represented? two options
> 1) use WSDL service there
> this is cool theoritically but we face the problems of how to
> represent the  extended information e.g. Hnadlers
>
>
> 2) Use a ServiceDesc that wrap the WSDLService (we can get it 75% fom 1.1)
>
> I think we should go for option 2# then there will be ModuleDesc,
> GlobalDesc .. lot of Desc. Where should it go.  into WSDLModule,
> org.apache.axis.registry? org.apache.axis.description?
>
> We have to discuss about bringing the WSDL module to prototype2 to do
this.
> Thanks
> Srinath
>



Mime
View raw message