[
https://jira.jboss.org/jira/browse/JBPM-2627?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-2627:
-----------------------------------
heiko, for 4.2 it is sufficient that the reporting failure does not block proper working
of the rest of the console. reporting on tomcat is a known issue. so for us this is not
a blocker for 4.2 and it is ok to place this issue on 4.3.
is that also ok for you ?
if that's ok then the only thing we need to do now is to have the reporting fail
gracefully, not blocking the rest of the console.
Reporting on tomcat fails due to missing JNDI datasource
configuration
----------------------------------------------------------------------
Key: JBPM-2627
URL:
https://jira.jboss.org/jira/browse/JBPM-2627
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Console
Reporter: Heiko Braun
Fix For: jBPM 4.2
Currently the report generation fails because there is no JBPM datasource configured in
tomcat. Without the reports will be DB dependend and not work. In order to fix report
generation on tomcat a proper JNDI datasource ('java:/JbpmDS') would need to be
configured as described here:
http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html
--
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