utility-components.xml uses org.rhq.enterprise.gui.common.ti

[stfkbf]

When running RHQ 1.1.3 GA with Jopr 2.1.3 GA the following exception occurs during installation (after completing the initial configuration site and clicking the Install buttin):

Caused by: com.sun.faces.config.ConfigurationException:
Source Document: jndi:/localhost/WEB-INF/jsf-components/utility-components.xml
Cause: Unable to find class 'org.rhq.enterprise.gui.common.time.UserFormatterRenderer'

This problem does not occur when using versions compiled from trunk of the two projects (very nice with the new treeview :)). However this version does not work with the JBossESB plugin.

Removing the utility-components.xml file solves the problem. Is it safe to remove this file? And if so would it be possible to have it removed from the svn repository too?

[stfkbf]

I was mistaken. The jopr console appears to be working at first sight, but clicking around generates a lot of exceptions and some funny looking UI.

Which version of RHQ + JOPR can be used to build a stable release?

[mazz]

Best bet is to svn co the RHQ upstream project, build that, then build the Jopr plugins using your local maven repo that contains your RHQ builds.

Off the top of my head, the basic steps would be:

svn co http://svn.rhq-project.org/repos/rhq/trunk/ rhq
cd rhq
mvn -Penterprise,dev -Dmaven.test.skip -Ddbsetup install
cd ..
svn co https://anonsvn.jboss.org/repos/jopr/trunk/ jopr
cd jopr
mvn -Pdev -Dmaven.test.skip install

(assuming you didn't set up your own db settings in $HOME/.m2/settings.xml, this will assume you have a Postgres DB on your box listening to port 5432 with the rhq database whose user/pass is rhqadmin/rhqadmin).

We will be releasing a Jopr beta in the next couple days - we'll try to publish the proper maven deps in our public maven repo then.

[stfkbf]

I have used the following commands:

svn co http://svn.rhq-project.org/repos/rhq/tags/RHQ_1_1_3_GA

svn co http://anonsvn.jboss.org/repos/jopr/tags/Jopr_2_1_3_GA/

And then build from that using:

mvn install -Pojdbc-driver,enterprise,dist -Dmaven.test.skip=true -Ddbsetup-do-not-check-schema

Build trunk of both RHQ and Jopr in this way produces a working version. However currently the ESB plugin is not compatible with trunk (which i assume contains Jopr 2.2?)

[mazz]

Trunk contains 2.2, that is correct.

What is it about the ESB plugin that doesn't work? Are you saying it doesn't compile or you get a runtime failure?

I'm not sure what is or is not compatible with those tagged versions of the svn - I think those were tagged to indicate the builds of the last Embedded Jopr release.

[stfkbf]

That explains it :) I thought there was a stable 2.1.3.GA release.

The ESB plugin does not compile against the lastest version. The output is the following:

[INFO] Scanning for projects...
[WARNING] No SCM providers configured.
WAGON_VERSION: 1.0-beta-2
[INFO] ------------------------------------------------------------------------
[INFO] Building JON JBossESB Plugin
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [enforcer:enforce {execution: enforce-versions}]
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: 25466 at timestamp: 1235981331476
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 9 source files to C:\software\svn\jonplugin\target\classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ESBDiscoveryComponent.java:[18,5] method does not override a method from its superclass

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[74,49] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.ActionComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[83,16] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[85,22] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[85,64] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[96,8] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.ActionComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[118,49] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.ActionComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[127,49] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.ActionComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[136,49] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.ActionComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[145,49] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.ActionComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ActionComponent.java:[153,49] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.ActionComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ESBComponent.java:[73,66] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ESBComponent.java:[135,35] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ESBComponent.java:[139,37] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\ESBComponent.java:[147,28] createContent(org.rhq.core.domain.content.PackageDetails,java.io.InputStream,boolean,boolean) in org.rhq.plugins.jbossas.util.FileContentDelegate cannot be applied to (org.rhq.core.domain.content.transfer.ResourcePackageDetails,java.io.InputStream,boolean)

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\DeploymentComponent.java:[157,24] createContent(org.rhq.core.domain.content.PackageDetails,java.io.InputStream,boolean,boolean) in org.rhq.plugins.jbossas.util.FileContentDelegate cannot be applied to (org.rhq.core.domain.content.transfer.ResourcePackageDetails,java.io.InputStream,boolean)

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\DeploymentComponent.java:[239,24] cannot find symbol
symbol : variable bean
location: class org.jbosson.plugins.jbossesb.DeploymentComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\DeploymentComponent.java:[244,49] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent

C:\software\svn\jonplugin\src\main\java\org\jbosson\plugins\jbossesb\DeploymentComponent.java:[247,60] resourceContext has private access in org.rhq.plugins.jmx.MBeanResourceComponent


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12 seconds
[INFO] Finished at: Mon Mar 02 09:08:59 CET 2009
[INFO] Final Memory: 18M/127M
[INFO] ------------------------------------------------------------------------

[mazz]

Ahhh. Yes. This is easy to fix. I had to correct a bad API in that JMX component - I usually don't like changing public APIs, but this was bad and needed correction.

We no longer expose those data fields directly (e.g. "bean") - you have to access/override via getters/setters.

Please see:

http://jira.rhq-project.org/browse/RHQ-1603

Instead of directly accessing "bean" member, use getEmsBean():

/**
 * Gets the loaded MBean. This will attempt to {@link #loadBean() load} the bean if it
 * is not yet loaded. This might still return <code>null</code> if the MBean could
 * not be loaded.
 *
 * @return the loaded MBean or <code>null</code> if it could not be loaded
 *
 * @see #loadBean()
 */
public EmsBean getEmsBean() {

[stfkbf]

Hi

That did indeed work. In the files:

ActionComponent.java
ESBComponent.java

I changed the references to bean and resourceContext and bean as suggested.

In the file DeploymentComponent.java file i removed the reference to FileUtils (which doesn't exist but might now be org.rhq.core.util.file.FileUtil) + changed references as suggested.

In then file ESBDiscoveryComponent.java i changed the declaration to contain:

public class ESBDiscoveryComponent extends MBeanResourceDiscoveryComponent

The plugin now compiles and works (at least as far as i can see) with the trunk branches of RHQ and Jopr.

Thank you very much for your help :)

The modifications are very minor but if you like i can email the source files.

[ips]

Thanks for the update.

I'd suggest creating an issue in SOA JIRA (https://jira.jboss.org/jira/browse/SOA) and attaching your modifications as a patch. The ESB team will want to get the ESB plugin compiling against RHQ/Jopr trunk prior to the next release of JON for SOA.

[mazz]

In the file DeploymentComponent.java file i removed the reference to FileUtils (which doesn't exist but might now be org.rhq.core.util.file.FileUtil) + changed references as suggested.

This is news to me. I have no idea what changed or why. Perhaps some dev out there knows what this FileUtil change was?

[stfkbf]

Done: https://jira.jboss.org/jira/browse/SOA-1203

[kconner]

We compile against the version specified in the SOA release. The plugin will be updated, as appropriate, when the SOA platform moves forward.

The pom.xml is not used to build that plugin however, as we had a requirement to build against a specific release of JON. As such, the platform build contains an ant script which downloads the release from an internal server, compiles the plugin, then repackages the JON release.

Kev