[embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-329) Reliance on Hardcoded Library Paths

[Thomas Hauser (JIRA)]

Reliance on Hardcoded Library Paths
-----------------------------------

                 Key: EMBJOPR-329
                 URL: https://jira.jboss.org/browse/EMBJOPR-329
             Project: Embedded Jopr
          Issue Type: Bug
    Affects Versions: 1.3.3
            Reporter: Thomas Hauser


This is related to https://jira.jboss.org/browse/JBPAPP-4886

>From JBPAPP-4886:

If the JBoss library locations are altered and the JBoss variables for the libraries (jboss.lib.url,jboss.common.lib.url and jboss.server.lib.url) are made consistent with the library locations the JBoss Admin Console cannot be opened.

Investigations shows
This is because the ApplicationServerDiscoveryComponent class don't use JBoss variables and instead hard coded the path to jar files:
See at the end of ApplicationServerDiscoveryComponent:
   CLIENT_JARS = Arrays.asList(new String[] { "client/jbossall-client.jar", "client/trove.jar", "client/javassist.jar", "common/lib/jboss-security-aspects.jar", "lib/jboss-managed.jar", "lib/jboss-metatype.jar", "lib/jboss-dependency.jar" });
   AS6_CLIENT_JARS = new ArrayList(CLIENT_JARS);
   AS6_CLIENT_JARS.add("lib/jboss-classpool.jar");
   AS6_CLIENT_JARS.add("lib/jboss-classpool-scoped.jar");

And it seems still the case in the trunk: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=blob;f=modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ApplicationServerDiscoveryComponent.java


Customers timescale is that they need a patch in October as their first production of a JBoss application is expected in November.

Please not that this is a time sensitive issue! Thanks

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira