This content has been marked as final.
Show 3 replies
-
1. Security domain for JMS authentication is blacklisted when implementation is in EAR
alesj Jan 13, 2011 6:31 AM (in response to martin.hynar)Which AS are you running?
.ear is by default isolated in AS6, hence not seen from DefaultDomain.
If you extract it into separate .jar, then it's shared by DefaultDomain, hence seen by JMS.
-
2. Re: Security domain for JMS authentication is blacklisted when implementation is in EAR
martin.hynar Jan 13, 2011 7:39 AM (in response to alesj)The target platform is JBoss EAP 5.1.0.
How to change the visibility in classloading so that it becomes visible?
-
3. Re: Security domain for JMS authentication is blacklisted when implementation is in EAR
alesj Jan 13, 2011 8:11 AM (in response to martin.hynar)The target platform is JBoss EAP 5.1.0.
Hmm, this is actually not community version, hence official support is who you should be asking this. ;-)
How to change the visibility in classloading so that it becomes visible?
Simple hint anyway:
* http://java.dzone.com/articles/jboss-microcontainer-classloading
* http://community.jboss.org/wiki/JBoss5custommetadatafiles
... but looking at the EAP5.1 config of EarClassLoaderDeployer::isolated, it's already false ...