[
https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1491:
--------------------------------------
Thanks Murray for the contribution, it's really helpful :)
Howard/Murray - in order for a new db config to be considered "supported" in the
distribution a new Hudson run would have to be setup against Ingres and run on each
release. Howard - you'd need to liaise with QA to get that arranged.
However, until that is done, I see no problem in including the new config in the distro if
we add a comment at the top of the file making it clear it hasn't been QA'd by
JBoss yet.
e.g.
<!-- Please note this configuration file has not been QA'd by JBoss. Use at your
own risk -->
or something similar.
add support for Ingres RDBMS to JBoss Messaging
-----------------------------------------------
Key: JBMESSAGING-1491
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1491
Project: JBoss Messaging
Issue Type: Patch
Affects Versions: 1.4.0.SP3.CP06, 2.0.0 Beta, EAP/SOA-P Integration, 1.4.3.GA,
2.0.0.GA, Unscheduled, AS 5.0 Integration
Environment: N/A
Reporter: murray armfield
Assignee: Tim Fox
Priority: Minor
Attachments: ingres-persistence-service.newrev.xml,
ingres-persistence-service.xml, ingres-persistence-service.xml, ingres.diff,
ingresv2.diff
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
I've been working on JBoss support on Ingres.
I've written an ingres-persistence-service.xml file for use with Ingres for inclusion
as part of JBoss Messaging
--
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