Hi Bill,
I helped you isolate a thread sync bug in the EJB deadlock detector back in the early
JBoss 3.0 cycle.
Subsequently I fixed the CMP BLOB handling in 3.0 and 3.2 and also added test cases
that demonstrated some bugs.
I'll have a look at the existing implementation and drop Thomas a lin
"Bill Burke" wrote :
| [EMAIL PROTECTED]
|
Bill,
Thomas is not responding on this address. I can see that he has been active from the
CVS checkins, although not in this area.
Steve Coy
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825814#3825814";>View
the original post
ht
"Bill Burke" wrote :
|
| What is your email?
|
|
The forum will tell you if you ask nicely :-)
Just click on my name on the left.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825837#3825837";>View
the original post
http://www.jboss.org/index.html?module=bb&op=posting&m
Hi,
The declaration of EJBProxyFactory contains (the relatively old) comment from marc:
anonymous wrote : Moved from typed return to Object to allow for optimizations in
creation
I'm curious to know what this optimisation actually is and if it ever eventuated.
Unless there's a good reason for
Are you talking about the new ejb timer implementation?
If so, would you rather see it using the jmx timer service?
Steve Coy
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831678#3831678
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
Actually, I see now that Adrian is talking about the implementation of
BootstrapContext.createTimer().
As far as Thomas' ejb timer implementation is concerned, it is just using
java.util.Timer.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831688#3831688
