[
https://jira.jboss.org/jira/browse/EMBJOPR-26?page=com.atlassian.jira.plu...
]
Ian Springer resolved EMBJOPR-26.
---------------------------------
Resolution: Done
Assignee: Ian Springer
The hibernate plugin is now included in the plugins dir of the JBAS4 admin console WAR -
r33. The admin console starts up without any errors and the log message
"[BootstrapAction] Loaded RHQ plugin [Hibernate]." confirms that the hibernate
plugin was loaded successfully. To test that the various Resources all get discovered and
work properly, a test app will need to be created as described in this JIRA's
description and deployed to the admin console JBAS instance.
include Hibernate plugin in JBAS4 admin console
-----------------------------------------------
Key: EMBJOPR-26
URL:
https://jira.jboss.org/jira/browse/EMBJOPR-26
Project: Embedded Jopr
Issue Type: Feature Request
Components: Web App/Integration
Affects Versions: 1.0
Reporter: Ian Springer
Assignee: Ian Springer
Fix For: 1.1
Original Estimate: 6 hours
Remaining Estimate: 6 hours
Charles: Add the Hibernate plugin to the JBAS4 console. This was something which came up
in the 1.0 demo, and should be long hanging fruit and useful if we get included in an
EAP4.3 fix pack.
Adding the hibernate plugin is simple enough. It's testing it that's difficult.
To do so, we need an EJB3 app that includes some entity beans, as well as startup code
that deploys the Hibernate stats mbean (as described by
https://docs.jbosson.redhat.com/confluence/display/JON2/Hibernate+Statist...).
This test app should also include a client app that allows us to generate some Hibernate
stats by hitting the entity EJBs. Ideally this testapp would be a webapp, but a
command-line client would suffice. The JBoss EJB3 distribution comes with a sample ear
that includes an ejb-jar with a single Session bean and a war with a client
(jboss-EJB-3.0_RC9_Patch_1/docs/tutorial/ear/). Unfortunately, it doesn't contain any
entity beans.
Charles, perhaps Len or Jarek could build the required test app.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira