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

[Eduardo Martins (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eduardo Martins updated AS7-6246:
---------------------------------

    Component/s: Naming

    
> Naming context read-only during legacy SAR deployment
> -----------------------------------------------------
>
>                 Key: AS7-6246
>                 URL: https://issues.jboss.org/browse/AS7-6246
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMX, Naming
>    Affects Versions: 7.2.0.Alpha1
>            Reporter: Philippe Marschall
>            Assignee: Eduardo Martins
>              Labels: jmx, jndi, naming, sar
>
> When the {{#startService()}} and {{#stopService()}} methods of a sublass of {{ServiceMBeanSupport}} are invoked the JNDI context is read only.
> Consider the following MBean:
> {code}
> public class LegacySample extends ServiceMBeanSupport implements LegacySampleMBean {
>         private static final String NAME = "java:global/env/foo/legacy";
>         private static final String VALUE = "BAR";
>         private static final Logger LOG = Logger.getLogger("sar-legacy");
>         public LegacySample() {
>                 super();
>         }
>         @Override
>         protected void startService() throws Exception {
>                 InitialContext ic = new InitialContext();
>                 ic.rebind(NAME, VALUE);
>                 LOG.info("started");
>         }
>         @Override
>         protected void stopService() throws Exception {
>                 InitialContext ic = new InitialContext();
>                 ic.unbind(NAME);
>                 LOG.info("stopped");
>         }
>         @Override
>         public String getMessage() {
>                 return "legacy";
>         }
> }
> {code}
> This will fail.

--
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