You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2010/06/14 15:02:13 UTC
[jira] Commented: (SLING-1556) Add optional imports for JDBC
packages used by Jackrabbit Core persistence managers
[ https://issues.apache.org/jira/browse/SLING-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878563#action_12878563 ]
Justin Edelson commented on SLING-1556:
---------------------------------------
This shouldn't be necessary and I'd suggest rolling it back. jackrabbit-server already has DynamicImport-Package: * to handle these type of extensions.
> Add optional imports for JDBC packages used by Jackrabbit Core persistence managers
> -----------------------------------------------------------------------------------
>
> Key: SLING-1556
> URL: https://issues.apache.org/jira/browse/SLING-1556
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Jackrabbit Server 2.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Jackrabbit Server 2.0.8
>
>
> Currently the Jackrabbit Server bundle only has an optional import for the Derby JDBC driver package. To support simpler replacment of Derby as the Jackrabbit persistence manager, optional imports should be created for all JDBC driver packages of the persistence managers included with the Jackrabbit Core library.
> Particulary this is the list of optional imports to be added:
> org.h2
> com.microsoft.sqlserver.jdbc
> org.gjt.mm.mysql
> oracle.jdbc
> org.postgresql
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (SLING-1556) Add optional imports for JDBC packages used by Jackrabbit Core persistence managers
Posted by Ian Boston <ie...@tfd.co.uk>.
I think some of our community have deployed on both Oracle and MySQL with no modifications to the import statements of the server bundle. I can check if you want firm confirmation, or they could respond here.
(ping Stuart F, didnt you do an Oracle deploy ?)
Ian
On 14 Jun 2010, at 07:02, Justin Edelson (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SLING-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878563#action_12878563 ]
>
> Justin Edelson commented on SLING-1556:
> ---------------------------------------
>
> This shouldn't be necessary and I'd suggest rolling it back. jackrabbit-server already has DynamicImport-Package: * to handle these type of extensions.
>
>> Add optional imports for JDBC packages used by Jackrabbit Core persistence managers
>> -----------------------------------------------------------------------------------
>>
>> Key: SLING-1556
>> URL: https://issues.apache.org/jira/browse/SLING-1556
>> Project: Sling
>> Issue Type: Improvement
>> Components: JCR
>> Affects Versions: JCR Jackrabbit Server 2.0.6
>> Reporter: Felix Meschberger
>> Assignee: Felix Meschberger
>> Fix For: JCR Jackrabbit Server 2.0.8
>>
>>
>> Currently the Jackrabbit Server bundle only has an optional import for the Derby JDBC driver package. To support simpler replacment of Derby as the Jackrabbit persistence manager, optional imports should be created for all JDBC driver packages of the persistence managers included with the Jackrabbit Core library.
>> Particulary this is the list of optional imports to be added:
>> org.h2
>> com.microsoft.sqlserver.jdbc
>> org.gjt.mm.mysql
>> oracle.jdbc
>> org.postgresql
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>