Thanks David :) I am listing what might helpful for you to review. (no hurry ..... even I like to have about two weeks time to get the real thing started).
1) new code has removed alll the hardcoded obj names. 2)At the test cases I do manually initaite the GBeans that would started by the plan in real case. 3) I think I got the basic of the plans. It is XML file explans the set of GBeans and there referances..... . If I need GBean A referd by GBean B I should specify poth GBeans at the plan and put a referance in B to A's obj name. then the B will get a refrance to A. 4) WSConFig Builder .. (it does not implement the interface properly yet) build a GBean (s) for the WS, Store the GBeans in a confguration and write the configuration to a store. Using the URI return anyone can load the configuration. 5) I am not sure How the Axis GBean should find the deployed Configurations. I look at the referance patterns but do not get the real hang on it yet. Cheers Srinath On Wed, 3 Nov 2004 20:50:39 -0800, David Jencks <[EMAIL PROTECTED]> wrote: > I am looking forward to looking at the new code very much and hope that > I can quickly finish up what I've been working on so I can concentrate > on the new code properly. > > Many thanks, > > david jencks > > > > On Nov 3, 2004, at 8:39 PM, Srinath Perera wrote: > > > Hi All; > > > > As I promise I have send a patch that fix the basic problems > > (hardcoded obj names ..ect ) in the Axis geronimo module and get the > > POJO case up and runing :). > > > > The patch is checked in; I am looking foward to the comments to know > > am I heading in the right direction. (I am busy with a exam and might > > not write codes for about two weeks on the module.) but I will be > > online and will happy if I can communicate in the mean time and > > understand the expectation of the EWS from the Geronimo point of view > > throughly. > > > > Thanks > > Srinath > > > > > > > > On Fri, 29 Oct 2004 15:17:14 +0600, Srinath Perera > > <[EMAIL PROTECTED]> wrote: > >> Thanks everybody for the help :) :)... I think I got the big picure > >> and hopfully should be able to get the Web Services working(which do > >> not have EJB) behind them with out kernel. (There is a classloader > >> issue when the EJB involved. I will try to get the code up removing > >> all referances to kernel for POJO based WS.) > >> > >> I think over all the stuff over the weekend get back. My view about > >> the Web Service is follows. There are two types of web services > >> A) EJB based > >> B) POJO based (servlet based one .. actually both has a servlet at the > >> front so I dont see any sense in the name "Servlet based" : ) ) > >> > >> Web Service(HTTP one we concern about) is a Servlet that accepts SOAP > >> over HTTP. Axis basically > >> 1) get the request XML (SOAP) and converts them to the java objects > >> 2) call the java class (POJO) or EJB that provide the implementation > >> 3) get what ever the result and send them back as SOAP > >> > >> Only deferance between the EJB based and POJO based one is > >> 1) Axis call a EJB instead of POJO at step #2 > >> 2) We have to make sure EJB is up when the webservice is called > >> > >> I think we should be able to do it with one WSBuilder. To be the steps > >> is like follows > >> 1. Geronimo Deployer find that the WAR/EAR is a ws module by looking > >> at exsistance of the webservices.xml file in the module > >> 2. The WSBuilder will create the confiuration and start it > >> a. there should be a one GBean for each WS (we have to sort out > >> how to do this) > >> b. there should be a GBean for each EJB that referanced > >> 3. when the confiuration started web services are avalible > >> > >> AxisGBean will keep track of the things and manage Axis > >> > >> Thanks > >> Srinath > >> > >> > >> > >> > >> On Fri, 29 Oct 2004 01:24:19 -0700, David Blevins > >> <[EMAIL PROTECTED]> wrote: > >>> > >>> On Oct 28, 2004, at 11:52 PM, David Jencks wrote: > >>> > >>>> My understanding of web services is that messages can be sent to > >>>> either servlets or ejbs. (Apparently the servlets aren't "Servlet" > >>>> implementations, but are usually wrapped in one). We need a gbean > >>>> to > >>>> be deployed for each such servlet and each such ejb. At the moment > >>>> I > >>>> think the best approach is to have a WSServletBuilder and a > >>>> WSEJBBuilder that will actually build the gbeans. These, especially > >>>> the WSEJBBuilder, would be similar to the openejb > >>>> SessionConfigBuilder. > >>> > >>> Not just similar to but the same as--one session bean can have all of > >>> the following interfaces: > >>> - Local > >>> - Remote > >>> - ServiceEndpoint > >>> > >>> All of which can have transaction attributes associated with them. > >>> The > >>> ServiceEndpoint interface can even be invoked directly by EJBs, > >>> Servlets, or App Clients through declaring it as a service-ref and > >>> looking a it up through JNDI. Any invocations on the ServiceEndpoint > >>> interface go through JAX-RPC. > >>> > >>> Aside from JAX-RPC/ServiceEndpoint invocations, people can invoke the > >>> session bean through SOAP/WSDL over HTTP or HTTPS. In this case > >>> there > >>> is a mapping from WSDL to the ServiceEndpoint interface. > >>> > >>> All in all, this is not very different from the CORBA integration > >>> which > >>> also supports Java and non-Java clients through IIOP. In this case > >>> we > >>> use SOAP instead of IIOP, ServiceEndpoint/JAX-RPC instead of > >>> Remote/RMI-IIOP, WSDL-to-Java mapping instead of IDL-to-Java mapping, > >>> and Axis instead of an ORB. > >>> > >>> -David > >>> > >>> > >> > > > >
