|
osdir.com mailing list archive |
|
Subject: Re: Server running... - msg#00010List: java.openejb.develmaven 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 Thread at a glance:
Previous Message by Date: click to view message previewRe: Server running...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 Next Message by Date: click to view message previewhttp://openejb.codehaus.orgHello, I have visited openejb.codehaus.org and noticed that your website is not listed on some search engines. I am sure that through our service the number of people who visit your website will definitely increase. SeekerCenter is a unique technology that instantly submits your website to over 500,000 search engines and directories -- a really low-cost and effective way to advertise your site. For more details please go to www.SeekerCenter.net. Give your website maximum exposure today! Looking forward to hearing from you. Best Regards, Vanessa Lintner Sales & Marketing www.SeekerCenter.net vanessa@xxxxxxxxxxxxxxxx You are receiving this email because you opted-in to receive special offers through a partner website. If you feel that you received this email in error or do not wish to receive additional special offers, please input the follow url in ie. http://www.seekercenter.net/remove.php?email=dev@xxxxxxxxxxx Previous Message by Thread: click to view message previewRe: Server running...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 Next Message by Thread: click to view message previewRe: Server running...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 To run the tests you need specify the java.naming.factory.url.pkgs to include the geronimo naming providers. I hope to add this to the default server startup, but for now just use this command: 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 Loading Comments...
|
|
