[
https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s...
]
Guy Kaisin commented on AS7-5584:
---------------------------------
Hi all,
Just don't know how you make it work...
I've downloaded the last build from hudson from here
https://ci.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-7.0.x/
I took build version 3280.
But I still got 'context is read only' issue.
Please can you give details about your solution?
Do I need to use the "WritableServiceBasedNamingStore.pushOwner(xxx) "
workaround?
If yes, how do you build the ServiceTarget object needed as parameter of the
'pushOwner' ?
Regards,
Guy
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