[
https://issues.apache.org/jira/browse/SLING-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878573#action_12878573
]
Justin Edelson commented on SLING-1556:
---------------------------------------
> And then we should probably remove the DynamicImport-Package statement
> completely.
Pretty sure we need DynamicImport-Package for other types of extensions to
Jackrabbit. For example, a custom DataStore or a Sybase PM.
At least at one point, there were issues extending the package import space via
a fragment and so we needed DynamicImport-Package to make this work.
I guess it is fair to say that since Jackrabbit has explicit support for these
libraries, we should list them, so I retract what I said above about removing
them. Let's just not remove DynamicImport-Package. OK?
> 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.
