Also, I think we should re-organize the deploy folder, possibly with something in that vein: Deploy /system /TX /jbossjca-service.xml /jboss-local-jdbc.rar /jboss-xa-jdbc.rar /JMS (like it is today) /management (like it is today) /Timers /ejb2-timer-service.xml /quartz-ra.rar /schedule-manager-service.xml /scheduler-service.xml /JBossWeb /JBossWS /Remoting /http-invoker.war /jmx-remoting.sar /apps /jmx-console.war /web-console.war Etc. The current deploy folder is such a mess... BTW, we could argue we need the same thing for the lib folder i.e. lib/system lib/apps (or lib/user) > -----Original Message----- > From: Adrian Brock > Sent: lundi, 29. janvier 2007 14:37 > To: JBoss.org development list > Cc: Dimitris Andreadis; jboss-as(a)redhat.com; The Core > Subject: Re: [jboss-dev] Re: Plan for JBossAS 4.2.0.CR1 - > Your Help isNeeded > > Here's another suggested change to the default configurations for JCA: > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40077 77#4007777 > > We should enable all the useful features that are available > by default rather than just having a basic config and requiring > users to figure out how to configure them. > > The most important is the transaction query timeout > for sql queries > > <set-tx-query-timeout/> > > Which will avoid the FAQs about hanging database connections > providing the sql driver supports it. :-) > > > On Wed, 2007-01-24 at 10:15 -0600, Dimitris Andreadis wrote: > > > Hi folks, > > > > > > We are shooting for Feb/26th for JBossAS 4.2.0.CR1, which > is only 4.5 > > > weeks away. As a consequence: > > -- > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Adrian Brock > Chief Scientist > JBoss, a division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > >