geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: Info needed: migrating openejb-itests to testsuite framework
Date Thu, 12 Oct 2006 20:25:54 GMT

On Oct 12, 2006, at 1:27 PM, Prasad Kashyap wrote:

> My efforts in deploying the openejb-itests.jar with the attached plan
> is failing b'coz of some errors in the plan. The errors in the plan
> are being introduced at some stage in the deploy process.
>
> My plan uses the pkgen ns for key-generator
>    xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"
>     ...
>     ...
>     <pkgen:key-generator>
>
>
> But the deploy tool is seeing the following the ns
>    xmlns:pkg="http://www.openejb.org/xml/ns/pkgen-2.0"
>    ......
>    ......
>    <pkg:key-generator>
>
>
> Where is this coming from ?

I can't find anywhere it could be coming from.  There are namespace  
substitutions in XmlBeansUtil and Upgrader but neither of those could  
produce this change.  They could change 2.0 to 2.1.

Wish I could offer useful advice :-(

david jencks

>
> Thanx
> Prasad
>
>
>
>
> On 10/11/06, Prasad Kashyap <goyathlay.geronimo@gmail.com> wrote:
>> Hi Jacek,
>>
>> We now have a testsuite directory under geronimo which is the basis
>> for a system and functional test framework for all of Geronimo. I  
>> have
>> begun with a doc in the wiki about this.
>> http://cwiki.apache.org/GMOxDEV/integration-testing.html The doc is
>> still in a rudimentary stage but it will give you a general idea.  
>> I am
>> enhancing it as I go along.
>>
>> This discussion revolves around migrating the openejb itests to this
>> new framework. So after a G assembly is done, the build will continue
>> to testing the various functional pieces of the server like
>> webcontainer, ejbcontainer, console, clustering etc.
>>
>> Cheers
>> Prasad
>>
>> On 10/11/06, Jacek Laskowski <jacek@laskowski.net.pl> wrote:
>> > On 10/11/06, Prasad Kashyap <goyathlay.geronimo@gmail.com> 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
>> >
>>
>> <openejb-jar.xml>
>> <itests-deploy.log>


Mime
View raw message