JBoss development,
A new message was posted in the thread "JavaEE namespace deployers":
http://community.jboss.org/message/519682#519682
Author : Scott Stark
Profile : http://community.jboss.org/people/scott.stark@jboss.org
Message:
--------------------------------------------------------------
The JNDIView bean needs a massive overhaul to properly display all of the namespaces. I would like to completely move away from class loader based component namespaces. I believe an spi is needed in the naming project that the ENCFactory implements to provide read-only access to all current components for use by admin views like JNDIView. At least this issue is related:
https://jira.jboss.org/jira/browse/JBAS-6001
I created https://jira.jboss.org/jira/browse/JBNAME-44 to introduce the spi into naming.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519682#519682
JBoss development,
A new message was posted in the thread "ClassPool Refactoring":
http://community.jboss.org/message/519571#519571
Author : Kabir Khan
Profile : http://community.jboss.org/people/kabir.khan@jboss.com
Message:
--------------------------------------------------------------
> mailto:kabir.khan@jboss.com wrote:
> There is a cache by default at the moment. I'll turn it off, and have the tests run with and without caching
Done
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519571#519571
JBoss development,
A new message was posted in the thread "JBEE-15 - Break all EE apis into separately versioned subprojects":
http://community.jboss.org/message/519543#519543
Author : Steve Ebersole
Profile : http://community.jboss.org/people/steve.ebersole@jboss.com
Message:
--------------------------------------------------------------
I just wanted to point out the need (for Hibernate's needs anyway) to at least have this available targeting JDK 1.4. Someone on IRC (David Llyod perhaps) mentioned that the 1.6 runtime was able to load classes faster if they are compiled targetting 1.6 and suggested compiling for all the JDKs.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519543#519543
JBoss development,
A new message was posted in the thread "MutableAttachments.addAttachment is counter-intuitive":
http://community.jboss.org/message/519537#519537
Author : Carlo de Wolf
Profile : http://community.jboss.org/people/wolfc
Message:
--------------------------------------------------------------
The MutableAttachments API defines a lot of addAttachment functions, which should actually be named setAttachment.
Because I'm not adding (another) attachment named <name>, but overriding any previous attachment named <name> with a new one. Alternatively it could be called putAttachment (in line with the Map API).
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519537#519537
JBoss development,
A new message was posted in the thread "Deployer ordering issue for EJB/JAX-RS/WAR?":
http://community.jboss.org/message/519532#519532
Author : Carlo de Wolf
Profile : http://community.jboss.org/people/wolfc
Message:
--------------------------------------------------------------
Hehe, this touches exactly my misunderstand of ComponentDeployers. I use them to split meta data, instead of installing runtime components.
Still we should have some sort of composition mechanism on a meta data level. But that would probably be sub-deployments?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519532#519532
JBoss development,
A new message was posted in the thread "ClassPool Refactoring":
http://community.jboss.org/message/519496#519496
Author : Kabir Khan
Profile : http://community.jboss.org/people/kabir.khan@jboss.com
Message:
--------------------------------------------------------------
Forgot to mention that I scheduled JBREFLECT-92 for a future release since alpha1 is released and alpha2 will probably be a rename of the beta? In other words I did not schedule it against the beta so it would erroneously get included in alpha2 somehow. Once JIRA is updated for the release, this issue should be moved to the right one
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519496#519496