openejb-junit module

2010-11-04 Thread Jean-Louis MONTEIRO 

Hi,

IIRC, Quintin did a nice work creating that module.
But, as far as i can see, this artifact is never published.

Is there any reason?
Is something missing we can achieve?

Jean-Louis
-- 
View this message in context: 
http://openejb.979440.n4.nabble.com/openejb-junit-module-tp3026748p3026748.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.

Re: JUnit Runner

2010-11-04 Thread David Blevins 

On Feb 23, 2010, at 3:14 AM, David Blevins wrote:

 Hey Quintin!
 
 Checked this little gem in -- sorry it's taken so long to get it reviewed.  
 There's some good stuff in here.  I was going to check it into a branch, but 
 it's in pretty awesome shape.  Really gets the creative juices flowing.
 
 We can support @RunTestAs using the same code the container uses to support 
 @RunAs -- we could even use the same annotation.  No need for a special 
 LoginModule  We could also add in support for @TransactionAttribute and even 
 @Interceptors.  All of the above will be a little sneaky and take a bit of 
 dancing, but totally doable.
 
 First thing though is I think we should flatten out all the abstractions that 
 aren't critical.  The security stuff for example strings from OpenEjbRunner 
 to JUnit4Runner and through OpenEjbTestContext.  With this approach it's 
 going to be real difficult to add more test method annotations.  Most this 
 comes from trying to get away from direct JUnit 4 usage.  I think for this 
 first iteration we can just make our lives simple, yank those abstractions 
 and just code straight against JUnit4.  We'll probably end up with a third of 
 the code.  So OpenEjbRunner and JUnit4Runner can get merged, TestContext can 
 get yanked and everything can become a Statement.
 
 What do you think?

Digging up this thread again.

Did some more tinkering with this kind of concept.  Check out:

  
http://svn.apache.org/repos/asf/openejb/trunk/openejb3/container/openejb-core/src/test/java/org/apache/openejb/core/stateless/StatelessContainerTest.java

A cross between the stuff Quintin was working on and the validation test stuff 
that Karan did.  Takes the build and return an app concept from Karan's work 
and pulls it into the test runner with injection that Quintin prototyped.  
The stuff that I hacked on is also not really ready for primetime as it doesn't 
do any scanning for apps in the classpath -- only the ability to build apps 
programmatically.  Ideally we'd have both ... either in different test runners 
or the same.

Tricky part obviously is that once we put something in front of users, we can't 
ever change it's behavior in any incompatible way.  All the stuff we have goes 
a bit too far into the experimental.

Wondering if doing a very stripped down version is the best approach to getting 
something out there and then float some of the ideas out in snapshots to get 
some feedback.

Thoughts?


-David

3.1.4 and stateless pooling

2010-11-04 Thread David Blevins 
Looks like there might be an issue with stateless bean pooling and failed 
instance creation draining the pool.

Won't have a chance to look at it till the weekend.  If someone wants to 
investigate, great.


-David

Re: [VOTE] OpenEJB 3.1.4 release

2010-11-04 Thread Matthias Wessendorf 
I am seeing this, when shutting down tomtom

SEVERE: The web application [/ejb-examples] appears to have started a
thread named [poolevict...@17704464] but has failed to stop it. This
is very likely to create a memory leak.
Nov 4, 2010 8:25:34 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/ejb-examples] appears to have started a
thread named [poolevict...@2221573] but has failed to stop it. This is
very likely to create a memory leak.
Nov 4, 2010 8:25:34 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/ejb-examples] appears to have started a
thread named [poolevict...@11600272] but has failed to stop it. This
is very likely to create a memory leak.
Nov 4, 2010 8:25:34 PM org.apache.catalina.loader.WebappClassLoader
findResourceInternal
INFO: Illegal access: this web application instance has been stopped
already.  Could not load
org/apache/catalina/loader/JdbcLeakPrevention.class.  The eventual
following stack trace is caused by an error thrown for debugging
purposes as well as to attempt to terminate the thread which caused
the illegal access, and has no functional impact.
Nov 4, 2010 8:25:34 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesJdbc
WARNING: JDBC driver de-registration failed for web application
[/HelloEjbService]
java.lang.NullPointerException
at 
org.apache.catalina.loader.WebappClassLoader.clearReferencesJdbc(WebappClassLoader.java:1944)
at 
org.apache.catalina.loader.WebappClassLoader.clearReferences(WebappClassLoader.java:1880)
at 
org.apache.catalina.loader.WebappClassLoader.stop(WebappClassLoader.java:1798)
at org.apache.catalina.loader.WebappLoader.stop(WebappLoader.java:738)
at 
org.apache.catalina.core.StandardContext.stop(StandardContext.java:4812)
at 
org.apache.openejb.tomcat.catalina.TomcatWsRegistry.removeWsContainer(TomcatWsRegistry.java:242)
at 
org.apache.openejb.server.webservices.WsService.beforeApplicationDestroyed(WsService.java:353)
at 
org.apache.openejb.assembler.classic.Assembler.fireBeforeApplicationDestroyed(Assembler.java:182)
at 
org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:804)
at 
org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:796)
at 
org.apache.openejb.tomcat.catalina.TomcatWebAppBuilder.afterStop(TomcatWebAppBuilder.java:403)
at 
org.apache.openejb.tomcat.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:66)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at 
org.apache.catalina.core.StandardContext.stop(StandardContext.java:4841)
at 
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:924)
at 
org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1319)
at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1290)
at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:323)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1086)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1098)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:450)
at 
org.apache.catalina.core.StandardService.stop(StandardService.java:587)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:648)
at 
org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:692)
Nov 4, 2010 8:25:34 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080



-Matthias

On Thu, Nov 4, 2010 at 6:55 AM, Shawn Jiang genspr...@gmail.com wrote:
 All EJB related tck cases passed with geronimo 22 branch.

 +1

 On Tue, Nov 2, 2010 at 6:09 PM, Jonathan Gallimore
 jonathan.gallim...@gmail.com wrote:
 +1

 Jon

 On Mon, Nov 1, 2010 at 7:03 AM, David Blevins david.blev...@visi.comwrote:

 Ok.  This one should be pretty quick -- not too many changes.

 Repo:

  https://repository.apache.org/content/repositories/orgapacheopenejb-005/

 Binaries:

  http://people.apache.org/~dblevins/staging-3.1.4-vote1/

 Branch (to become a tag):

  http://svn.apache.org/repos/asf/openejb/branches/openejb-3.1.4/

 Rat log:

  http://people.apache.org/~dblevins/staging-3.1.4-vote1/rat.log
  http://people.apache.org/~dblevins/staging-3.1.4-vote1/rat.xml (ant
 script with excludes)

 iTests results on OSX:

  http://people.apache.org/~dblevins/staging-3.1.4-vote1/osx-jdk6.txt
  http://people.apache.org/~dblevins/staging-3.1.4-vote1/build.xml

 Release notes:


 http://people.apache.org/~dblevins/staging-3.1.4-vote1/3.1.4/RELEASE-NOTES.txt



 Here's my

Renaming the OpenEJB/Tomcat bundle

2010-11-04 Thread David Blevins 
Getting the feeling calling the bundle Tomtom is a disadvantage.  Hadn't 
realized how incredible popular the Tomtom GPS tech was in Europe.  There's 
really no way to google it or monitor it on twitter without getting a ton of 
results related to the GPS.  I've seen a fair number of people say they dislike 
the name -- course they say so in unflattering ways :)

Have been thinking about what a better name would be and finally had a thought 
that wasn't terrible.

Thinking Tomee might be fun (pronounced like Tommy).  Basically short for 
Tomcat EE.

Thoughts?


-David

Re: Renaming the OpenEJB/Tomcat bundle

2010-11-04 Thread Thiago Veronezi 
I think thats a really good name.
[]s,
Thiago.

On Thu, Nov 4, 2010 at 5:13 PM, David Blevins david.blev...@visi.comwrote:

 Getting the feeling calling the bundle Tomtom is a disadvantage.  Hadn't
 realized how incredible popular the Tomtom GPS tech was in Europe.  There's
 really no way to google it or monitor it on twitter without getting a ton of
 results related to the GPS.  I've seen a fair number of people say they
 dislike the name -- course they say so in unflattering ways :)

 Have been thinking about what a better name would be and finally had a
 thought that wasn't terrible.

 Thinking Tomee might be fun (pronounced like Tommy).  Basically short for
 Tomcat EE.

 Thoughts?


 -David