[
https://issues.jboss.org/browse/RF-13119?page=com.atlassian.jira.plugin.s...
]
Sande Gilda updated RF-13119:
-----------------------------
Description:
The richfaces-quickstarts/kitchensink-rf/src/test/resources/test-ds.xml uses the same
datasource JNDI name and connection URL that the kitchensink quickstart test file uses:
<datasource jndi-name="java:jboss/datasources/KitchensinkQuickstartTestDS"
<connection-url>jdbc:h2:mem:kitchensink-quickstart-test;DB_CLOSE_DELAY=-1</connection-url>
This should be changed to a unique name, for example:
<datasource jndi-name="java:jboss/datasources/KitchensinkrfQuickstartTestDS"
<connection-url>jdbc:h2:mem:kitchensink-rf-quickstart-test;DB_CLOSE_DELAY=-1</connection-url>
was:
The richfaces-quickstarts/kitchensink-rf/src/test/resources/test-ds.xml uses the same
datasource JNDI name that the kitchensink quickstart test file uses: <datasource
jndi-name="java:jboss/datasources/KitchensinkQuickstartTestDS"
This should be changed to a unique name, for example:
<datasource jndi-name="java:jboss/datasources/KitchensinkrfQuickstartTestDS"
kitchensink-rf test-ds.xml does not use a unique datasource JNDI
name
---------------------------------------------------------------------
Key: RF-13119
URL:
https://issues.jboss.org/browse/RF-13119
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: examples
Reporter: Sande Gilda
The richfaces-quickstarts/kitchensink-rf/src/test/resources/test-ds.xml uses the same
datasource JNDI name and connection URL that the kitchensink quickstart test file uses:
<datasource jndi-name="java:jboss/datasources/KitchensinkQuickstartTestDS"
<connection-url>jdbc:h2:mem:kitchensink-quickstart-test;DB_CLOSE_DELAY=-1</connection-url>
This should be changed to a unique name, for example:
<datasource
jndi-name="java:jboss/datasources/KitchensinkrfQuickstartTestDS"
<connection-url>jdbc:h2:mem:kitchensink-rf-quickstart-test;DB_CLOSE_DELAY=-1</connection-url>
--
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