+1 .. that has a additional advantage as when the OpenEJB code changes the this cade break and by putting it at openEJB and add a test it can handle easily as well.
Let me think how it should be done. a thought; I will hide the what expected by open EJB behind a interface. the real implemetation of the interface let us put inside OpenEJB cvs. let us load the impl class in runtime (same way JAXB/JNDI load the impls) using property file or a hard coded class name. This make the axis can compile without openejb jars (yap it will fail at runing) thoughts .. may be we should do the same to jetty as well .. then we can switch between tomcat and jetty easily. Thanks Srinath > +1 from me to move the relevant code...Alan, do you want to take a stab at > it? > > -- dims > > ----- Original Message ----- > From: Alan D. Cabrera <[EMAIL PROTECTED]> > Date: Sun, 8 Aug 2004 19:51:55 -0400 > Subject: Axis dependencies > To: [EMAIL PROTECTED], [email protected] > > > > > There are parts of the Axis code that rely on OpenEJB. This seems to > introduce a circular dependence as OpenEJB relies on Geronimo. IIUC, > this code may be better placed in OpenEJB. > > > > Thoughts? > > > > > > Regards, > > Alan > > > > > > > > -- > Davanum Srinivas - http://webservices.apache.org/~dims/ > > ------------------------------------ Lanka Sofware Foundation ------------------------------------
