[jboss-jira] [JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment

[Philippe Marschall (JIRA)]

    [ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740945#comment-12740945 ] 

Philippe Marschall commented on AS7-5584:
-----------------------------------------

Guy,
You need the latest 7.x (actually 7.2) builds from
https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/
the patch hasn't been merged into the 7.0 line.
                
> 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