I was wondering if there any changes/improvements we need to do in the handling of AS 5 in
Currently we use some specific jars to startup AS, specific locations to deploy users app,
some specific JMX commands to see if it is alive and to stop it...are all these things
backwards compatible from JB4.2 to JB5 or are there some things that have radically
changed we need to take care of ?
I've cc'ed in Rob Stryker who should be able to give you details if you need them
to answer the question.
This is an update of the AS5 Beta4 plan. Since the time until JBW is extremely limited
try to reduce the scope wherever we can to the essential/critical bits. The target
to have complete all development by Feb/1st and leave one week for final
Component updates, preferably completed by Jan/18th, drop-dead date Jan/25th (without
- HEM 3.3.2.Beta2 (Emmanuel)
Done, but the fix in not used yet by EJB3
- Upgrade jboss transactions to 4.3.0.GA
Will probably be dropped for Beta4, currently under discussion.
- Integrate jboss-ha-server-api.jar
- Upgrade jboss-ha-client.jar to 1.0.0.GA
Upgrade to JBoss Cache 2.1.0.GA
- Fix JBoss Cache / AS integration issues
Brian's dealing with those. A new version of pojo cache is currently under QA due to
- Upgrade jboss aop to 2.0.0.CR3 (Kabir)
The release is cut, but waiting for POJO cache update
- VFS to 2.0.0.Beta7 (Ales)
To bring in performance improvements. May do caching changes on Beta8
- non-snapshot Microcontainer release
(2.0.0.Beta10) Ales or Adrian.
MC is now at snapshot due to the classloader switch. As soon as we verify the change is
(TCK/testsuite) we need a tagged release. MC JIRA needs to be updated too.
- Messaging upgrade (Tim/Clebert)
Scott has already produced 2 JBM releases (currently at 1.4.0.SP3a) to resolve
problems . Need to clarify if another release will be needed and what it will contain.
There was also this snapshot introduced by jbossws-native50, just now:
Is that a SPI change that should be discussed? We need to be moving out of snapshots,
- Deal with vfs, aop, jbossxb performance
Waiting for vfs and aop updates to see how much things will improve.
Seam apps should be deployed and run at an acceptable speed.
Profile service completeness and demonstrated usage through the new
- management CRUD usecases
- support for managing
Datasources and JMS (Alexey)
I'd like to coordinate with Charles so we can showcase a couple of basic CRUD
through the new management console.
Bootstrapping of the MC
- initial persistent format
of the profile repository
This is still waiting on Scott, unless we can re-assign it.
There is also the task of avoiding the metadata vs metavalue type
leakage, but AFAIK it is not documented in JIRA.
Moving away from the UnifiedClassloader
Adrian performed the switch here and any problems should be reported here:
Adrian's refactoring of deployer implementation - no updates yet
Anil's redo of the security deployer based on the new metadata.
Anil updated the jboss security libs, but didn't see any deployer changes. Is there
more to it?
- Separation of the EJB3 module into it's own external project.
- Complete the annotation and extended persistency work (JIRA tasks?)
- EJB3/TCK improvements
This is tough as EJB3 has cyclical dependencies on the aspects module. EJB3 is broken out
its own project and mavenization/componetization will continue in parallel, but for AS5
Beta4 we'll release using the "frozen" EJB3 version from AS trunk.
PaulG is also helping with the mavenization of the AS build.
We are a little down to 245 failures (91%), down from 200 failures (93%), due to the
VFSClassloader change. Most of those failures are expected so we need to sort things out
with tests that don't make sense anymore, or need to be corrected.
Stabilize the jdk16 build, it doesn't currently run to full completion:
No much progress here. Ales made changes in the MC to switch from:
ClassLoader.loadClass --> Class.forName(className, false, classLoader)
Maybe we should do something similar for AS and other included projects ?
Shelly should be looking at the jdk16 testsuite build.
Need everyone to help with a good JBAS JIRA cleanup, we still have some 133 issues
scheduled for Beta4. Anything not marked as blocker/critical will be deferred, so please
have a look at your issues and define proper priorities, or better, reschedule or
Tasks assigned to you:
Tasks reported by you:
Again, please don't break things that already work.
Any issues, let me know.
jboss-development mailing list