[
https://issues.jboss.org/browse/JBIDE-12491?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12491:
---------------------------------------------
Nonno - if we need a fix for this in tools this should be backported to 3.3.x/JBDS 5.
But my point is that if driver.type was what was used for driver.jar before why has this
changed ?
This is basically breaking the "API" (might be its a wrong API, but why change
it now in Seam 2.3 ?)
What i'm understanding is that if driver.type is used instead in the ds.xml template
things will work with old and new versions. Why don't we revert this in the
not-yet-released seam 2.3 ?
JBT Doesn't place the JDBC Driver correctly
-------------------------------------------
Key: JBIDE-12491
URL:
https://issues.jboss.org/browse/JBIDE-12491
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Environment: Juno, JBT Daily Plugin
Reporter: Daniel Hinojosa
Assignee: Daniel Azarov
Fix For: 3.3.2, 4.0.0.Alpha1
in the ds.xml file. the following gets generated under driver. Works fine under regular
seam-gen.
{code}
<?xml version="1.0" encoding="UTF-8"?>
<datasources
xmlns="http://www.jboss.org/ironjacamar/schema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.org/ironjacamar/schema
http://www.jboss.org/ironjacamar/schema/datasources_1_0.xsd">
<datasource
jndi-name="nationalparkDatasource"
enabled="true"
use-java-context="true"
pool-name="nationalparkDatasource_pool">
<connection-url>jdbc:hsqldb:MyDB</connection-url>
<driver>[Ljava.lang.String;@4633819a</driver>
<security>
<user-name>sa</user-name>
<password></password>
</security>
</datasource>
</datasources>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira