Hello, Library updates to JBAS often create chain-effects and delays, so I'd like to put everyone on the same page for the next 4.x release, which is 4.0.5.GA, scheduled (initially) for Sep/29th. The goal is to have all updates done, 2 weeks before the release, so that testing, qa, installer can proceed without problems. If this is not possible we need either to move the JBAS release date, or cancel some particular library upgrade(s) The list of updates is bellow. What concern me is that jbossws-1.0.5 is scheduled for Oct/31st which makes it impossible to incorporate in the next jbas release. At the same time, remoting-2.0.0 doesn't work with the existing jbossws-1.0.3, so either we cancel those 2 updates, or create a reduced jbossws-1.0.4 release earlier. I would like also to know, if checking in the latest EJB3 code, requires any additional upgrades (remoting maybe?). The EJB3 module should really be coming as a binary dependency to jboss 4.x, so is there a plan for this? Finally, does anyone know where jaxb v2.0 is used in jboss 4.x ? AFAIK, we don't bundle it with the distro. <componentref name="sun-jaxb" version="2.0"/> If you see any other library update missing, let me know. Thanks /Dimitris - Tomcat will be upgraded to 5.5.18 (now) http://jira.jboss.com/jira/browse/JBAS-3586 - MyFaces upgraded to 1.1.4, when the release becomes available (but I don't have too many hopes about them releasing) http://jira.jboss.com/jira/browse/JBAS-3554 - Update EJB3 in Branch_4_0. http://jira.jboss.com/jira/browse/JBAS-3625 - update JBossRemoting to version 2.0.0 http://jira.jboss.com/jira/browse/JBAS-3272 - Upgrade jbossws to 1.0.4.GA http://jira.jboss.com/jira/browse/JBAS-3626 -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Dimitris Andreadis AS Development Manager JBoss, a Division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hello, Library updates to JBAS often create chain-effects and delays, so I'd like to put everyone on the same page for the next 4.x release, which is 4.0.5.GA, scheduled (initially) for Sep/29th. The goal is to have all updates done, 2 weeks before the release, so that testing, qa, installer can proceed without problems. If this is not possible we need either to move the JBAS release date, or cancel some particular library upgrade(s) The list of updates is bellow. What concern me is that jbossws-1.0.5 is scheduled for Oct/31st which makes it impossible to incorporate in the next jbas release. At the same time, remoting-2.0.0 doesn't work with the existing jbossws-1.0.3, so either we cancel those 2 updates, or create a reduced jbossws-1.0.4 release earlier. I would like also to know, if checking in the latest EJB3 code, requires any additional upgrades (remoting maybe?). The EJB3 module should really be coming as a binary dependency to jboss 4.x, so is there a plan for this? Finally, does anyone know where jaxb v2.0 is used in jboss 4.x ? AFAIK, we don't bundle it with the distro. <componentref name="sun-jaxb" version="2.0"/> If you see any other library update missing, let me know. Thanks /Dimitris - Tomcat will be upgraded to 5.5.18 (now) http://jira.jboss.com/jira/browse/JBAS-3586 - MyFaces upgraded to 1.1.4, when the release becomes available (but I don't have too many hopes about them releasing) http://jira.jboss.com/jira/browse/JBAS-3554 - Update EJB3 in Branch_4_0. http://jira.jboss.com/jira/browse/JBAS-3625 - update JBossRemoting to version 2.0.0 http://jira.jboss.com/jira/browse/JBAS-3272 - Upgrade jbossws to 1.0.4.GA http://jira.jboss.com/jira/browse/JBAS-3626 -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Dimitris Andreadis AS Development Manager JBoss, a Division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

jaxb is used by the jbossws stack. Another issue that has been around for a while is obfuscating the dom4j classes to avoid these leaking into the user space. The dom4j subset we included in 4.0.4 broke use of xpath from dom4j since it has an explicit dependency on jaxen. I'm doing some testing with jarjar to create an org.jboss.dom4j package namespace version. Dimitris Andreadis wrote: > Hello, > > Library updates to JBAS often create chain-effects and delays, so I'd > like to put everyone on the same page for the next 4.x release, which is > 4.0.5.GA, scheduled (initially) for Sep/29th. > > The goal is to have all updates done, 2 weeks before the release, so > that testing, qa, installer can proceed without problems. If this is not > possible we need either to move the JBAS release date, or cancel some > particular library upgrade(s) > > The list of updates is bellow. What concern me is that jbossws-1.0.5 is > scheduled for Oct/31st which makes it impossible to incorporate in the > next jbas release. At the same time, remoting-2.0.0 doesn't work with > the existing jbossws-1.0.3, so either we cancel those 2 updates, or > create a reduced jbossws-1.0.4 release earlier. > > I would like also to know, if checking in the latest EJB3 code, requires > any additional upgrades (remoting maybe?). The EJB3 module should really > be coming as a binary dependency to jboss 4.x, so is there a plan for > this? > > Finally, does anyone know where jaxb v2.0 is used in jboss 4.x ? AFAIK, > we don't bundle it with the distro. > > <componentref name="sun-jaxb" version="2.0"/> > > If you see any other library update missing, let me know. > > Thanks > /Dimitris > > - Tomcat will be upgraded to 5.5.18 (now) > http://jira.jboss.com/jira/browse/JBAS-3586 > > - MyFaces upgraded to 1.1.4, when the release becomes available (but I > don't have too many hopes about them releasing) > http://jira.jboss.com/jira/browse/JBAS-3554 > > - Update EJB3 in Branch_4_0. > http://jira.jboss.com/jira/browse/JBAS-3625 > > - update JBossRemoting to version 2.0.0 > http://jira.jboss.com/jira/browse/JBAS-3272 > > - Upgrade jbossws to 1.0.4.GA > http://jira.jboss.com/jira/browse/JBAS-3626 > > -- > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Dimitris Andreadis > AS Development Manager > JBoss, a Division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

It would be kept in the server/default/lib for app compatibility. It would just be embedded in the core jmx/system layer as an impl detail and removed from the server bootstrap classpath. Emmanuel Bernard wrote: > Keep Steve in the loop since Hibernate use dom4j >