axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chathura Herath" <chath...@opensource.lk>
Subject RE: [Axis2] Deployment requirements for M1
Date Fri, 03 Dec 2004 07:46:38 GMT
Hi,
 
If I understand right ,you are proposing an Adaptor from the ServiceMetaData
AXISWSDLService  so that interface given by the service Desc thing to the
Deployment will remain unchanged. I haven't looked at the code though but
think this ServiceMetaData interface is very much similar to that
AXISWSDLService interface I have proposed in the wiki. 
Are we to do the same for Operations too??
 
My view is let's change the AXISWSDLService interface so it will match your
interfaces, rather than squeezing in an adaptor and a new object hierarchy.
 
Regards
Chathura
  _____  

From: Deepal Jayasinghe [mailto:deepal@opensource.lk] 
Sent: Friday, December 03, 2004 11:56 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Deployment requirements for M1
 
hi chathura and all;
 
What I have currently implemented is generating metadata object structure
(ServiceMetaData etc..) in the deployment module using service.xml and then
create an executable service object form metadata and give that to
EngineRegistry. 
 
But moving from metadata object structure to AXISWSDLService directly , I
mean creating AXISWSDLService directly from service.xml and WSDL is not a
simple task (I am not saying it can't , but not so easy). And creating a
metadata object structure may not so cost since deployment module run in a
different thread.
 
So for the M1 what if I first create metadata object structure from
service.xml and then create AXISWSDLService using WSDL file and then inject
what ever the necessary data from 
ServiceMetaData to AXISWSDLService  (   :) ).
 
thoughts?
Deepal
 

Mime
View raw message