You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Srinath Perera <he...@gmail.com> on 2004/12/08 07:28:52 UTC
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
Re: Using the WSDLService in the registry[continuingRE: [Axis2][Engine]Step by Step;Engine, Engine registry deployment and the Phase Resolver]
Posted by Deepal Jayasinghe <de...@opensource.lk>.
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" <he...@gmail.com>
To: <ax...@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
>
Re: Using the WSDLService in the registry[continuingRE: [Axis2][Engine]Step by Step;Engine, Engine registry deployment and the Phase Resolver]
Posted by Srinath Perera <he...@gmail.com>.
On Wed, 8 Dec 2004 12:49:14 +0600, Sanjiva Weerawarana
<sa...@opensource.lk> wrote:
> "Chathura Herath" <ch...@opensource.lk> writes:
> >
> > My idea is the service desc neither belongs to the registry nor to the
> > engine rather it is an intermediary OM working on top of WOM. Further
> > Service desc is basically WOM customized to suite the Axis requirements.
to me ServiceDesc have more than one role to play .. it has a role in
engine too it is not just a WOM custamization
> > would opt to keeping them in a separate package like in Axis 1.1
> > org.apache.axis.description.
>
> +1.
>
> Where will the registry itself be? IMO it makes sense to put that in
> the engine package itself .. since its an integral part of the
> engine.
+1 yes when we go for description there would be almost nothing left in
the org.apache.axis.registry package .. let us put all desc in the
org.apache.axis.description and move the engine registry to
org.apache.axis.engine
Thanks
Srinath
Re: Using the WSDLService in the registry[continuingRE: [Axis2][Engine]Step by Step;Engine, Engine registry deployment and the Phase Resolver]
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
"Chathura Herath" <ch...@opensource.lk> writes:
>
> My idea is the service desc neither belongs to the registry nor to the
> engine rather it is an intermediary OM working on top of WOM. Further
> Service desc is basically WOM customized to suite the Axis requirements.
I
> would opt to keeping them in a separate package like in Axis 1.1
> org.apache.axis.description.
+1.
Where will the registry itself be? IMO it makes sense to put that in
the engine package itself .. since its an integral part of the
engine.
Sanjiva.
RE: Using the WSDLService in the registry[continuingRE: [Axis2][Engine]Step by Step;Engine, Engine registry deployment and the Phase Resolver]
Posted by Chathura Herath <ch...@opensource.lk>.
> -----Original Message-----
> From: Srinath Perera [mailto:hemapani@gmail.com]
> Sent: Wednesday, December 08, 2004 12:29 PM
Hi Srinath, all
+1 for option 2
Further...
> To: axis-dev@ws.apache.org
> 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?
My idea is the service desc neither belongs to the registry nor to the
engine rather it is an intermediary OM working on top of WOM. Further
Service desc is basically WOM customized to suite the Axis requirements. I
would opt to keeping them in a separate package like in Axis 1.1
org.apache.axis.description.
Cheers
Chathura
>
> We have to discuss about bringing the WSDL module to prototype2 to do
> this.
> Thanks
> Srinath