[
https://issues.jboss.org/browse/EMBJOPR-374?page=com.atlassian.jira.plugi...
]
Larry O'Leary moved JBPAPP-9474 to EMBJOPR-374:
-----------------------------------------------
Project: Embedded Jopr (was: JBoss Enterprise Application
Platform)
Key: EMBJOPR-374 (was: JBPAPP-9474)
Affects Version/s: 1.3.4.SP5
(was: EAP_EWP 5.1.2)
Release Notes Docs Status: (was: Not Yet Documented)
Release Notes Text: (was: Datasource type mapping property is now a text
field allowing the input of a type mapping to use with a datasource.)
Component/s: Plugin
(was: Embedded Jopr)
Security: (was: Public)
Fix Version/s: 1.3.4.SP6
(was: EAP_EWP 5.1.3)
Docs QE Status: (was: NEW)
MySQL datasource type mapping should be present
-----------------------------------------------
Key: EMBJOPR-374
URL:
https://issues.jboss.org/browse/EMBJOPR-374
Project: Embedded Jopr
Issue Type: Bug
Components: Plugin
Affects Versions: 1.3.4.SP5
Environment: JBoss EAP 5.1.2
Reporter: Larry O'Leary
Assignee: Larry O'Leary
Labels: admin-console, jopr
Fix For: 1.3.4.SP6
From Bugzilla RHQ Project Bug 791142 - Jan Martiska 2012-02-16 05:21:47 EST
When creating a datasource in EAP 5.1.2 admin console, it was found out there was no
choice 'MySQL' for type mapping. I wonder why this is not present currently? It is
a supported database.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira