On 10/11/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
David,Thanks for that write-up on the openejb itests. It helped me understand the structure better. All the client code (in src/itests) have a dependency on the beans (in src/java) anyway. So this is what I did. I put all the beans in 1 core project (openejb-itests). I put the plans and DDs in their individual projects. The individual projects then unpack just the needed classes from that core project and build the ejb archive with it's plan and DD. testsuite/ejbcontainer-testsuite ejb-modules openejb-itests <-- core project with beans openejb-security-001 <-- just plan and DD openejb-security-002 openejb-security-003 openejb-cmp2-prefetch openejb-cmp2-petstore openejb-cmp2-cmrmapping openejb-cmp2-storage test-ejbcontainer <--- junit tests in client
Hi Prasad, Why are the matter being discussed here? Shouldn't it go to openejb-dev? Jacek -- Jacek Laskowski http://www.laskowski.net.pl
