[jboss-jira] [JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment
Philippe Marschall (JIRA)
jira-events at lists.jboss.org
Fri Dec 21 11:18:08 EST 2012
[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742894#comment-12742894 ]
Philippe Marschall commented on AS7-5584:
-----------------------------------------
The patch only works for "pojo" sars, at the time when the patch was made there was no {{ServiceMBeanSupport}} class in AS7. So {{ServiceMBeanSupport}} don't work. I'll see what I can do and file a separate JIRA.
> 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-in-jboss-7-from-mbean-naming-context-is-read-onl
--
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
More information about the jboss-jira
mailing list