Convert OJB to use a spring managed datasource as opposed to directly setting
the JNDI name in OJB.properties.
--------------------------------------------------------------------------------------------------------------
Key: JS2-308
URL: http://issues.apache.org/jira/browse/JS2-308
Project: Jetspeed 2
Type: Improvement
Components: Assembly/Configuration
Versions: 2.0-M4
Reporter: Scott T Weaver
Assigned to: Scott T Weaver
Fix For: 2.0-M4, 2.0-FINAL
Convert OJB to use a Spring managed datasource as opposed to directly setting
the JNDI name in OJB.properties.
The procedure for this is outlined here:
http://www.springframework.org/docs/reference/orm.html#d0e7571.
This allows for developers to easily override the datasource in use within
Spring as opposed to having to mess with OJB ( IMO, this a good thing). The
deafult will work exactly like the existing implementation in that it will use
a JNDI datasource. I will also include a commented-out datasource bean
definition that uses a simple DBCP Pooled datasource as opposed to a JNDI one.
On a side note. I have been using this approach for internal projects and it
is working out very well. The only difference as I use Hibernate on internal
projects as opposed to OJB, but the logic is still very similar and the results
are the same, a datasource managed in Spring as opposed the ORMs proprietary
configuration format.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
