Data sources in Activiti 1.5 - JNDI support

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Active Member II

Data sources in Activiti 1.5 - JNDI support

Jump to solution

In Activiti 1.5 provides support for Data Sources -- but we need to ender URL/Username/Password.

Can this support supplying a JNDI name for the data source instead?

1 Solution

Accepted Solutions
Highlighted
Intermediate

Re: Data sources in Activiti 1.5 - JNDI support

Jump to solution

Ah yes, the devil is always in the detail.

The data model feature first exposed in 1.5 does not support JNDI datasources.

Greg

View solution in original post

3 Replies
Intermediate

Re: Data sources in Activiti 1.5 - JNDI support

Jump to solution

Johnny,

Yes, you can use a configured JNDI datasource that will take precedence over a configured URL/user/password combination.

If you open the activiti-app.properties where you configure your database, you will notice the following commented out section:

# JNDI CONFIG

# If uncommented, the datasource will be looked up using the configured JNDI name.
# This will have preference over any datasource configuration done below that doesn't use JNDI
#
# Eg for JBoss: java:jboss/datasources/activitiDS
#
#datasource.jndi.name=jdbc/activitiDS

# Set whether the lookup occurs in a J2EE container, i.e. if the prefix "java:comp/env/" needs to be added if the JNDI
# name doesn't already contain it. Default is "true".
#datasource.jndi.resourceRef=true

Uncomment the datasource.jndi.name property ans set it to a properly configured container datasource.

Cheers,

Greg

Highlighted
Active Member II

Re: Data sources in Activiti 1.5 - JNDI support

Jump to solution

Yes, I'm aware of that, but that wasn't my question.

1.5 allows you to set additional data sources (on the tenants tab, go to Data Sources, and see the below screen)

(Incidentally, even adding a data source with this information is failing for us on 1.5.2)

Highlighted
Intermediate

Re: Data sources in Activiti 1.5 - JNDI support

Jump to solution

Ah yes, the devil is always in the detail.

The data model feature first exposed in 1.5 does not support JNDI datasources.

Greg

View solution in original post