Implemented a simple WAS EJB module which leverages the ibm-ejb-jar-bnd.xmi specific DD for defining a JNDI with which the Home interface of the EJB is binded. Wrote a simple test case to test unmarshalling that xmi file using the generated JAXB tree. Everything is OK, just I have to go home now and I will commit code by tomorrow.
On Tue, Jul 15, 2008 at 8:27 PM, Mohammad Nour El-Din <[EMAIL PROTECTED]> wrote: > Solved my the JAXB classes generation issues and conflicts, working on > writing test cases. Here how I am going to do it: > > 1- As WAS has a lot of features and extensions I will start by full > simple scenarios to test. > 2- Evolving from these simple scenarios and will build more complex > ones trying to cover all aspects of WAS specific DDs, as much as > possible and according to what we can provide in OpenEJB. > > On Mon, Jul 14, 2008 at 6:15 PM, Mohammad Nour El-Din > <[EMAIL PROTECTED]> wrote: >> Sorry for the that question, I will just follow what David Blevins did >> with Sun and WebLogic specific DDs. >> >> On Mon, Jul 14, 2008 at 4:34 PM, Mohammad Nour El-Din >> <[EMAIL PROTECTED]> wrote: >>> I am fixing some name conflict probelms in the generated java classes. >>> But I have one question about the generated package names, can we >>> still use packages like *or.omg.xmi*, or we should change the package >>> names to something like *org.apache.openejb.config.jee.was*, the whole >>> question is about names only and its relation to being used in >>> open-source project ? >>> >>> -- >>> Thanks >>> - Mohammad Nour >>> >> >> >> >> -- >> Thanks >> - Mohammad Nour >> > > > > -- > Thanks > - Mohammad Nour > -- Thanks - Mohammad Nour
