]
Weston Price resolved JBAS-4147.
--------------------------------
Resolution: Rejected
The reason the HSQLDB plugin is distributed is because HSQL is the defaut database
distributed with JBoss and required by the J2EE/EE specifications. Derby is not
distributed and deployed by default. There is no reason to include this in any
distribution as a standard deployment choice.
Build and install missing derby-plugin.jar
------------------------------------------
Key: JBAS-4147
URL:
http://jira.jboss.com/jira/browse/JBAS-4147
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Installer, Build System
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
Environment: Windows XP, JDK 6, although irrelevant to the issue here.
Reporter: Panagiotis Astithas
Assigned To: Weston Price
When using the Derby DBMS with jboss, the example configuration file in:
JBOSS_HOME\docs\examples\jca\derby-ds.xml
references a Derby MBean:
<mbean code="org.jboss.jdbc.DerbyDatabase"
name="jboss:service=Derby" />
This MBean is supposed to properly start and shutdown the embedded Derby instance. It is
supposed to be delivered as a jar in JBOSS_HOME\server\default\lib\ along with
hsqldb-plugin.jar, for instance, which serves a similar purpose.
Unfortunately the zip/tar.gz download does not appear to contain it, nor the JEMS
installer seems to create it, even when configured with Derby instead of HSQL.
Apparently the jar gets built when building jboss in varia/output/lib, but not in the
default directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: