[JBoss JIRA] (JBRULES-3682) drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
by Mark Proctor (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3682?page=com.atlassian.jira.plug... ]
Mark Proctor updated JBRULES-3682:
----------------------------------
Assignee: Geoffrey De Smet
> drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
> ---------------------------------------------------------------------------------------
>
> Key: JBRULES-3682
> URL: https://issues.jboss.org/browse/JBRULES-3682
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 5.3.0.Final
> Environment: local
> Reporter: Amit Telang
> Assignee: Geoffrey De Smet
> Labels: maven
>
> Hi, after inclusion guvnor 5.x in application, we are unable to deploy our application through Hudson on our managed server. Issue is related to drools-compiler-5.3.0.Final.jar dependancy with antlr3.3 jar file. If I use exclusion tag to exclude this it excludes all the jar which starts with antlr.
> If I use package exclude to include this antlr3.3 it do not compile. Unable to resolve this small looking issue for a long time.
> Please provide any valuable feedback if someone also faces this issue.
--
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
11 years, 7 months
[JBoss JIRA] (JBRULES-3682) drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
by Mark Proctor (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3682?page=com.atlassian.jira.plug... ]
Mark Proctor updated JBRULES-3682:
----------------------------------
Fix Version/s: 6.0.0.Alpha1
> drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.
> ---------------------------------------------------------------------------------------
>
> Key: JBRULES-3682
> URL: https://issues.jboss.org/browse/JBRULES-3682
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 5.3.0.Final
> Environment: local
> Reporter: Amit Telang
> Assignee: Geoffrey De Smet
> Labels: maven
> Fix For: 6.0.0.Alpha1
>
>
> Hi, after inclusion guvnor 5.x in application, we are unable to deploy our application through Hudson on our managed server. Issue is related to drools-compiler-5.3.0.Final.jar dependancy with antlr3.3 jar file. If I use exclusion tag to exclude this it excludes all the jar which starts with antlr.
> If I use package exclude to include this antlr3.3 it do not compile. Unable to resolve this small looking issue for a long time.
> Please provide any valuable feedback if someone also faces this issue.
--
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
11 years, 7 months
[JBoss JIRA] (JBRULES-3673) Fact metadata declared in a POJO are lost when declaring fact metadata in DRL
by Mario Fusco (JIRA)
Mario Fusco created JBRULES-3673:
------------------------------------
Summary: Fact metadata declared in a POJO are lost when declaring fact metadata in DRL
Key: JBRULES-3673
URL: https://issues.jboss.org/browse/JBRULES-3673
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
Assume a POJO is used as a fact and annotated with @Position as follows:
public class PositionAnnotatedEvent {
@Position(1)
private String arg1;
@Position(0)
private String arg0;
// getters and setters
}
When I add some metadata to this class in DRL, for example:
declare org.jboss.qa.brms.bre.regression.POJOAnnotationMergeTest.PositionAnnotatedEvent
@role(event)
end
Then the following rule using positional arguments does not compile, producing an IndexOutOfBoundsException with message 'Error trying to access field at position 0'. The same rule with named arguments compiles:
rule 'sample rule'
when
org.jboss.qa.brms.bre.regression.POJOAnnotationMergeTest.PositionAnnotatedEvent( 'value1', 'value2'; )
then
end
The relevant stack trace follows:
java.lang.IndexOutOfBoundsException: Error trying to access field at position 0
at org.drools.factmodel.ClassDefinition.getField(ClassDefinition.java:162)
at org.drools.rule.builder.PatternBuilder.processPositional(PatternBuilder.java:432)
at org.drools.rule.builder.PatternBuilder.processConstraintsAndBinds(PatternBuilder.java:392)
at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:310)
at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:131)
at org.drools.rule.builder.GroupElementBuilder.build(GroupElementBuilder.java:65)
at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:80)
at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:2578)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:970)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:456)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:643)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:41)
--
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
11 years, 7 months
[JBoss JIRA] (JBAS-9523) On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for
by Nicholas DiPiazza (JIRA)
[ https://issues.jboss.org/browse/JBAS-9523?page=com.atlassian.jira.plugin.... ]
Nicholas DiPiazza updated JBAS-9523:
------------------------------------
Summary: On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for (was: On JBoss 5.1.0.GA EAP, jboss.xml <depends> for org.jboss.varia.property.SystemPropertiesService to load their System Properties. )
> On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for
> -------------------------------------------------------
>
> 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/tes...
> 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/Tes...
> 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/Tes...
> 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
11 years, 7 months
[JBoss JIRA] (JBAS-9523) On JBoss 5.1.0.GA EAP, jboss.xml <depends> ignored for org.jboss.varia.property.SystemPropertiesService
by Nicholas DiPiazza (JIRA)
[ https://issues.jboss.org/browse/JBAS-9523?page=com.atlassian.jira.plugin.... ]
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/tes...
> 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/Tes...
> 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/Tes...
> 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
11 years, 7 months
[JBoss JIRA] (JBAS-9523) On JBoss 5.1.0.GA EAP, jboss.xml <depends> for org.jboss.varia.property.SystemPropertiesService to load their System Properties.
by SBS JIRA Integration (JIRA)
[ https://issues.jboss.org/browse/JBAS-9523?page=com.atlassian.jira.plugin.... ]
SBS JIRA Integration updated JBAS-9523:
---------------------------------------
Forum Reference: https://community.jboss.org/thread/152996, https://community.jboss.org/message/775821#775821, https://community.jboss.org/message/775821 (was: https://community.jboss.org/message/775821, https://community.jboss.org/thread/152996)
> On JBoss 5.1.0.GA EAP, jboss.xml <depends> for org.jboss.varia.property.SystemPropertiesService to load their System Properties.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> 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/tes...
> 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/Tes...
> 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/Tes...
> 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
11 years, 7 months
[JBoss JIRA] (JBAS-9523) On JBoss 5.1.0.GA EAP, jboss.xml <depends> for org.jboss.varia.property.SystemPropertiesService to load their System Properties.
by Nicholas DiPiazza (JIRA)
[ https://issues.jboss.org/browse/JBAS-9523?page=com.atlassian.jira.plugin.... ]
Nicholas DiPiazza updated JBAS-9523:
------------------------------------
Security: Public (was: JBoss Customer)
> On JBoss 5.1.0.GA EAP, jboss.xml <depends> for org.jboss.varia.property.SystemPropertiesService to load their System Properties.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> 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/tes...
> 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/Tes...
> 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/Tes...
> 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
11 years, 7 months
[JBoss JIRA] (AS7-5916) CLONE - JNDI listBindings() does not work for items in java:jboss/exported - EAP 6.0.0
by Brad Maxwell (JIRA)
Brad Maxwell created AS7-5916:
---------------------------------
Summary: CLONE - JNDI listBindings() does not work for items in java:jboss/exported - EAP 6.0.0
Key: AS7-5916
URL: https://issues.jboss.org/browse/AS7-5916
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: Brad Maxwell
Assignee: Stuart Douglas
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
Attachments: BindJndiDemo.java
When an object is bound to java:jboss/exported/abc/def (for example using the naming subsystem in standalone.xml), it can be retrieved from a remote client with context.lookup("abc/def").
Calling context.listBindings("abc") return 0 bindings. This appears to be because ServiceBasedNamingStore.lookup() checks the service registry and then the boundServices, but listBindings() only checks the boundServices.
--
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
11 years, 7 months