On Sat, 2006-02-18 at 04:58, Adrian Brock wrote: > On Fri, 2006-02-17 at 15:34, Scott M Stark wrote: > > These two issues currently assigned to Tim: > > http://jira.jboss.com/jira/browse/JBAS-1434 > > http://jira.jboss.com/jira/browse/JBMESSAGING-170 > > I hope so. The purpose of giving them to someone else was > that I didn't have time to do it, and they are something > that could be done by anybody. > > They have been progressively pushed back since 4.0.0
I'd prefer to find the time to write these tests myself then we can move the JMSContainerInvoker with its practically unoverridable implementation to legacy. This would also be one less thing to worry about for EJB3 integration. Which I see you also moved to 4.0.5. In my opionion this is a mistake. If you keep pushing these things back, people just learn to ignore it knowing that if they leave it long it enough it will be keep getting deferred to the next release. e.g. The "critical" clustering issue that has been hanging around for months: http://jira.jboss.com/jira/browse/JBAS-1476 I hope this isn't going to get pushed back as well. These critical issues should really be done in the next availble release candidate, not done at the last minute for the GA release. -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
