[
https://issues.jboss.org/browse/RF-11952?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11952:
-------------------------------
Description:
Since Showcase uses JPA/JMS, {{jee6}} profile can't be deployed onto Glassfish.
It would be necessary to provide custom profile for Glassfish with custom
{{persistence.xml}} setup.
{code}
javax.naming.NameNotFoundException: No object bound to name java:/DefaultDS
{code}
{code}
Caused by: javax.naming.NamingException: Lookup failed for '/ConnectionFactory'
...
{code}
We also need to deal with he JMS setup
was:
Since Showcase uses JPA/JMS, {{jee6}} profile can't be deployed onto Glassfish.
It would be necessary to provide custom profile for Glassfish with custom
{{persistence.xml}} setup.
{code}
javax.naming.NameNotFoundException: No object bound to name java:/DefaultDS
{code}
{code}
Caused by: javax.naming.NamingException: Lookup failed for '/ConnectionFactory'
...
{code}
Showcase: Glassfish -specific profile
-------------------------------------
Key: RF-11952
URL:
https://issues.jboss.org/browse/RF-11952
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: showcase
Affects Versions: 4.2.0.CR1
Reporter: Lukáš Fryč
Fix For: 4.3-Tracking
Since Showcase uses JPA/JMS, {{jee6}} profile can't be deployed onto Glassfish.
It would be necessary to provide custom profile for Glassfish with custom
{{persistence.xml}} setup.
{code}
javax.naming.NameNotFoundException: No object bound to name java:/DefaultDS
{code}
{code}
Caused by: javax.naming.NamingException: Lookup failed for '/ConnectionFactory'
...
{code}
We also need to deal with he JMS setup
--
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