So, the solution is rebuild my own jackrabbit 1.4.8 with the classes afected patched in version 1.5, while I don't be able to upgrade to 1.5, this way all configurations will manage connection by JNDI, right? Thanks Thomas and Alexander.
Thomas Müller-2 wrote: > > Hi, > > And about other blocks "FileSystem" and the last "DataStore", I saw in [1] >> that you mentioned, the configuration for JNDI is possible by: >> "JNDI can be used to get the connection. In this case, use the >> javax.naming.InitialContext as the driver, and the JNDI name as the URL. >> If >> the user and password are configured in the JNDI resource, they should >> not >> be configured here. Example JNDI settings: >> >> < param name="driver" value="javax.naming.InitialContext" /> >> < param name="url" value="java:comp/env/jdbc/Test" /> >> " >> So, it was what I did in the blocks, are they right? > > > This is not supported yet in Jackrabbit 1.4.x. See > See https://issues.apache.org/jira/browse/JCR-1309 > and > http://jackrabbit.apache.org/api/1.4/org/apache/jackrabbit/core/fs/db/DbFileSystem.html > > Regards, > Thomas > > -- View this message in context: http://www.nabble.com/Change-the-PM-to-DbDataStore.-tp21919003p21935661.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
