[jboss-jira] [JBoss JIRA] (JBAS-9523) On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for org.jboss.varia.property.SystemPropertiesService

[Nicholas DiPiazza (JIRA)]

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

Nicholas DiPiazza updated JBAS-9523:
------------------------------------

    Summary: On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for org.jboss.varia.property.SystemPropertiesService  (was: On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for )

    
> On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for org.jboss.varia.property.SystemPropertiesService
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-9523
>                 URL: https://issues.jboss.org/browse/JBAS-9523
>             Project: Application Server 3  4  5 and 6
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Other
>    Affects Versions: JBossAS-5.1.0.GA
>         Environment: Any OS - I've only reproduced the issue with JBoss 5.1.0.GA.
>            Reporter: Nicholas DiPiazza
>
> Please see https://community.jboss.org/message/775821 
> We are moving from JBoss 4.3.0.EAP to JBoss 5.1.0.GA EAP.
>  
> In JBoss 4.3.0, we deploy an XML mbean with code="org.jboss.varia.property.SystemPropertiesService" to create some system properties:
>  
>  
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE server>
> <server>
>   <mbean code="org.jboss.varia.property.SystemPropertiesService" 
>   name="ndipiazza.config.props:type=Service,name=testSysProp">
>     <attribute name="Properties">     
>  test.local.jndi.localname=ejb/ExLocEJB
>  test.remote.jndi.localname=ejb/ExRemEJB
>     </attribute>
>   </mbean>
> </server>
>  
> We can then use these properties in web applications' JBoss configuration files such as jboss.xml:
>  
>  
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss PUBLIC
>       -//JBoss//DTD JBOSS 4.2//EN
>       http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd>
> <jboss>
>  <enterprise-beans>
>   <session>
>    <ejb-name>ExRemEJB</ejb-name>
>    <jndi-name>${test.remote.jndi.localname}</jndi-name>
>    <depends>ndipiazza.config.props:type=Service,name=testSysProp</depends>
>   </session>
>   <session>
>    <ejb-name>ExLocEJB</ejb-name>
>    <jndi-name>${test.local.jndi.localname}</jndi-name>
>    <depends>ndipiazza.config.props:type=Service,name=testSysProp</depends>   
>   </session>  
>  </enterprise-beans> 
> </jboss>
>  
> This was nice, because then we could hot-deploy system properties to the server without having to edit the configuration of the domain. 
>  
> However, in JBoss 5.1.0.GA, this seems to have stopped working. The jboss.xml will not evaluate these system properties presumably because they are not deployed in time. 
>  
> Some things:
>  
> 1) I am aware of this post: https://community.jboss.org/thread/152996 - which correctly says it will work if we specify the mbean for the SystemPropertiesService in jboss-service.xml. But this is NOT an option for us. We need to be able to deploy those system properties dynamically. 
>  
> 2) Note how I tried to use <depends> to make it so the mbean depended on that Service. But it just seems to ignore it. 
>  
> 3) If I wait until the server is fully deployed before deploying the ejb jar file, this works. But I have the requirement that the ejb-jar must load on server startup with everything else. So no delayed deploy trick will work here unfortunately. 
>  
> Is there some way I can achieve this how we have it working in JBoss 4.3.0?
>  
> I have attached some files to help test this:
>  
> 1) test-testSysProp-service.xml - https://community.jboss.org/servlet/JiveServlet/download/775821-71425/test-testSysProp-service.xml
>    Defines the system properties. Copy this in your server/PROFILE/deploy directory to deploy it. 
> 2) TestEJB.jar - https://community.jboss.org/servlet/JiveServlet/download/775821-71426/TestEJB.jar
>    An EJB jar that will use system properties from test-testSysProp-service.xml. The EJB will only deploy if those properties are able to be resolved. Otherwise, you will get this error: 
>  
>  
> ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=TestEJB.jar,name=ExRemEJB,service=EJB3_IORFactory state=Createorg.omg.CosNaming.NamingContextPackage.InvalidName: IDL:omg.org/CosNaming/NamingContext/InvalidName:1.0
>  
> 3) TestEJBProject.zip - https://community.jboss.org/servlet/JiveServlet/download/775821-71427/TestEJBProject.zip
>    The eclipse EJB project TestEJB

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