[
http://jira.jboss.com/jira/browse/JBAS-2120?page=all ]
Adrian Brock closed JBAS-2120.
------------------------------
Resolution: Deferred
Closing features that are (or will be) implemented in JBoss Messaging.
http://jira.jboss.com/jira/browse/JBMESSAGING
If anybody wants to provide a patch that implements these,
the issue can be reopened.
Duplicates of these issues will be closed
unless they provide an implementation/patch.
Patches should first be discussed in the
development forum:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=153
if there isn't already a forum link attached to this issue.
JBossMQ should use the <type-mapping> from the DataSource
---------------------------------------------------------
Key: JBAS-2120
URL:
http://jira.jboss.com/jira/browse/JBAS-2120
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.3RC1
Reporter: Adrian Brock
Priority: Minor
Currently JBossMQ's
JDBC2 persistence manager
(
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQJDBC2Persistence)
JDBC statemanager (
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQStateJDBC)
have their SQL configured through a big map of system properties.
This means that you need different configurations for each backend DB.
See docs/examples/jms or
http://www.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB
Instead, we should use the <type-mapping> from the DataSource which uses the
standardjbosscmp-jdbc.xml
to map queries to the database.
The only configuration required, would then be
* The DataSource
* Table Names
* Column Names
with default names for each.
This should be done as a "fork", e.g. create a JDBC4
since we still want to support people with the old configurations.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira