On Tue, Apr 13, 2004 at 10:06:25PM -0500, David Blevins wrote:
> On Tue, Apr 13, 2004 at 03:22:50PM -0500, Dain Sundstrom wrote:
> > David,
> > 
> > I just checked in support for ejb-ref, ejb-local-ref and a hacked 
> > version of Stateful BMT policy.  The hacked BMT policy does not support 
> > holding a tx context open between invocations.
> > 
> > Now the integrated tests results are:
> > Tests run: 168,  Failures: 40,  Errors: 5

> I had that in the Assembler class, which we aren't using.  It checks
> if it's already there and adds it if it isn't.  Best not to do that in
> the server as it isn't there in the embedded scenario.
> 
> When I was hacking things up at apachecon, I remember adding that code
> to the AbstractEJBContainer, which was ok as the code checked first,
> etc.

FYI, I added that hack.  It's set in GenericEJBContainer

With another hack I was able to get more of the serialization tests to work. 

   Tests run: 168,  Failures: 4,  Errors: 5

Still 4 failures, to go.  

-David

> 
> Maybe there is a better place now.  Not sure.
> 
> -David
> 
> > 
> > java -Djava.naming.factory.url.pkgs=org.apache.geronimo.naming -jar 
> > target/assembly/bin/server.jar org/openejb/itests
> > 
> > -dain
> > 
> > /*************************
> >  * Dain Sundstrom
> >  * Partner
> >  * Core Developers Network
> >  *************************/
> > 
> > On Apr 12, 2004, at 1:30 PM, David Blevins wrote:
> > 
> > >
> > >maven
> > >cd target/assembly
> > >java -jar bin/server.jar org/openejb/itests
> > >
> > >--in another console--
> > >cd target/openejb-DEV
> > >./bin/openejb-tests
> > >
> > >
> > >On Mon, Apr 12, 2004 at 01:04:25PM -0500, Dain Sundstrom wrote:
> > >>I mean how did you get the tests to run?
> > >>
> > >>-dain
> > >>
> > >>On Apr 12, 2004, at 12:59 PM, David Blevins wrote:
> > >>
> > >>>
> > >>>1. Sublcassed ObjectInputStream to allow me to set the classloader I
> > >>>want.
> > >>>
> > >>>2. Created a sublcass of EJBRequest that also implements 
> > >>>EJBInvocation
> > >>>  and reads the data in a lazy fasion.  By the time the arguments are
> > >>>  needed, the right classloader has been set on the ObjectInputStream
> > >>>by
> > >>>  the EJBRequestHandler and all is good.
> > >>>
> > >>>-David
> > >>>
> > >>>On Mon, Apr 12, 2004 at 12:11:35PM -0500, Dain Sundstrom wrote:
> > >>>>How did you get this to run?
> > >>>>
> > >>>>-dain
> > >>>>
> > >>>>/*************************
> > >>>>* Dain Sundstrom
> > >>>>* Partner
> > >>>>* Core Developers Network
> > >>>>*************************/
> > >>>>
> > >>>>On Apr 12, 2004, at 3:51 AM, David Blevins wrote:
> > >>>>
> > >>>>>Still quite a few failures, but minimal remote server functionality
> > >>>>>is
> > >>>>>working.  I whipped up an EJBInvocation implementation that reads 
> > >>>>>the
> > >>>>>data off the stream as it passes through the interceptor stack in 
> > >>>>>the
> > >>>>>container.  As soon as we are in a post-release cycle, I'm going to
> > >>>>>stream-line that even further.
> > >>>>>
> > >>>>>Test results are:
> > >>>>>Tests run: 112,  Failures: 27,  Errors: 6
> > >>>>>
> > >>>>>Couple things causing problems:
> > >>>>>
> > >>>>>- DatabaseBean can't get a datasource, so no BMP tests run. (open)
> > >>>>>
> > >>>>>- BeanPolicy$2.invoke throwing "Not yet implemented" is preventing
> > >>>>> nearly all the SFSB tests from running. (open)
> > >>>>>
> > >>>>>- Still having classloader issues on outbound proxy replacements,
> > >>>>> so many RMI-IIOP tests are failing. (working on it)
> > >>>>>
> > >>>>>All in all the test suite is doing it's job.
> > >>>>>
> > >>>>>-David

Reply via email to