[
https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s...
]
kknd22 commented on AS7-5584:
-----------------------------
Guy,
I applied the patch from this jira into my local 7.1.1 final jar:
build/src/main/resources/modules/org/jboss/as/sar/main/module.xml (+1 -0)
sar/src/main/java/org/jboss/as/service/AbstractService.java (+7 -1)
sar/src/main/java/org/jboss/as/service/CreateDestroyService.java (+2 -2)
sar/src/main/java/org/jboss/as/service/StartStopService.java (+2 -2)
It worked. Yes, AbstractService.java has the
WritableServiceBasedNamingStore.pushOwner(container.subTarget()); workaround. So if your
last build doesn't work maybe you should double check the source that you downloaded
to make sure that it contains this fix.
-Chris
Naming context read-only during SAR deployment
----------------------------------------------
Key: AS7-5584
URL:
https://issues.jboss.org/browse/AS7-5584
Project: Application Server 7
Issue Type: Bug
Components: POJO
Affects Versions: 7.1.1.Final
Reporter: Philippe Marschall
Assignee: Philippe Marschall
Fix For: 7.2.0.Alpha1
During the #start() #stop() method of a legacy SAR the naming context is read only. The
problem seems to be that
{{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the
thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}}
http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira