Hi,
Alexander Klimetschek schrieb:
> On Mon, Nov 30, 2009 at 14:23, Thomas Müller wrote:
>> As I already wrote, it doesn't make sense to do that now. We can still
>> do that later on, when there is actually somebody that needs it.
>
> AFAIU the workaround done in Sling wrt the package exports is
On Mon, Nov 30, 2009 at 14:23, Thomas Müller wrote:
> As I already wrote, it doesn't make sense to do that now. We can still
> do that later on, when there is actually somebody that needs it.
AFAIU the workaround done in Sling wrt the package exports is a bit
ugly, hence there is some need for it
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783742#action_12783742
]
premkumar commented on JCR-2414:
I added schemaObjectPrefix to all components as you said an
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783698#action_12783698
]
Thomas Mueller commented on JCR-2414:
-
> Do I need to add schemaObjectPrefix in all DB co
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved JCR-2414.
-
Resolution: Invalid
> Problem with multiple SCHEMA
>
>
>
[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783677#action_12783677
]
Stefan Guggisberg commented on JCR-1456:
> I'd keep the non-pooled stuff around just
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783676#action_12783676
]
premkumar commented on JCR-2414:
Yes all the permissions have been set to SCOTT1.
I'm able v
[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783675#action_12783675
]
Jukka Zitting commented on JCR-1456:
OK, let's go with the separate package. Should we do
Hi,
>> I would not move the API to the Jackrabbit API. Just moving the
>> interfaces into sepatate packages, eg. below o.a.j.core.api would
>> suffice it to export this space and leave the implementation private.
>
> +1
>
> Moving the persistence manager interface and co (basically everything
> th
[
https://issues.apache.org/jira/browse/JCR-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2413:
--
Resolution: Fixed
Fix Version/s: 2.0.0
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783640#action_12783640
]
Stefan Guggisberg commented on JCR-2414:
are you sure that you/ve set up permisisons
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783627#action_12783627
]
premkumar commented on JCR-2414:
Yes I manually set schemaObjectPrefix to SCOTT.(dot)
All t
[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783628#action_12783628
]
Martijn Hendriks commented on JCR-1456:
---
> are there any known issues?
Besides the mi
On Mon, Nov 30, 2009 at 11:09, Felix Meschberger wrote:
>>> It's worth to move some of the internal API to jackrabbit-api
>>> for other bundle to provide different implementation. Tt could well
>>> documented and better for third party to extend the jackrabbit.
>>
>> I would do that only if there
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783616#action_12783616
]
Stefan Guggisberg commented on JCR-2414:
> Caused by: java.sql.SQLException: ORA-0094
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg updated JCR-2414:
---
Priority: Major (was: Critical)
adjusting priority
> Problem with multiple SCHEMA
> -
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
premkumar updated JCR-2414:
---
Attachment: workspace.xml
Changed schemaObjectPrefix to scott1, Still getting same exception.
Have attached wor
On Mon, Nov 30, 2009 at 10:44 AM, Thomas Müller wrote:
> I would wait until it's a real problem. Trying to solve _potential_
> problems in advance is usually the wrong path.
I understand it will take effort/risk to do it.
Thanks for the discussion and all your hard works!
-Guo
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783607#action_12783607
]
Thomas Mueller commented on JCR-2414:
-
I guess you need to change the schemaObjectPrefix
Hi,
Marcel Reutegger schrieb:
> On Mon, Nov 30, 2009 at 10:02, Felix Meschberger wrote:
>> This leaves just xerces and lucene (and a few smaller libraries) inside
>> the jackrabbit-bundle. Lucene is ok, because Jackrabbit IIRC is closes
>> knitted with Lucene.
>
> actually not at all. it is perf
Hi,
> I don't have another implementation at the moment for any of them.
OK, good to know.
> I can think of it's might be possible to add key/value store as bundle
> persistence store in future.
I would wait until it's a real problem. Trying to solve _potential_
problems in advance is usually t
[
https://issues.apache.org/jira/browse/JCR-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
premkumar updated JCR-2414:
---
Attachment: repository.xml
Attached Jackrabbit configuration file
> Problem with multiple SCHEMA
> ---
Problem with multiple SCHEMA
Key: JCR-2414
URL: https://issues.apache.org/jira/browse/JCR-2414
Project: Jackrabbit Content Repository
Issue Type: Bug
Environment: Oracle 9i, Windows XP/Linux
[
https://issues.apache.org/jira/browse/JCR-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2413:
--
Status: Patch Available (was: Open)
> AlreadyClosedException on initial index creation
> ---
[
https://issues.apache.org/jira/browse/JCR-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2413:
--
Attachment: JCR-2413.patch
Proposed fix.
> AlreadyClosedException on initial index creation
> --
On Mon, Nov 30, 2009 at 9:59 AM, Thomas Müller wrote:
> I would do that only if there is an actual need for it. Do you have
> another implementation? Persistence manager, data store, or journal?
> If yes, would it be enough to just move the persistence manager
> interface, or do we need to do some
On Mon, Nov 30, 2009 at 10:02, Felix Meschberger wrote:
> This leaves just xerces and lucene (and a few smaller libraries) inside
> the jackrabbit-bundle. Lucene is ok, because Jackrabbit IIRC is closes
> knitted with Lucene.
actually not at all. it is perfectly hidden behind the QueryHandler
int
Hi,
Guo Du schrieb:
> On Mon, Nov 30, 2009 at 9:02 AM, Felix Meschberger wrote:
>> The problem of Jackrabbit Core is, that apart from implementing the
>> Jackrabbit API (which is imported in the bundle), it has its internal
>> API (for example the PersistenceManager interface or others). This
>>
Hi,
Thomas Müller schrieb:
> Hi,
>
>> It's worth to move some of the internal API to jackrabbit-api
>> for other bundle to provide different implementation. Tt could well
>> documented and better for third party to extend the jackrabbit.
>
> I would do that only if there is an actual need for it
Hi,
> It's worth to move some of the internal API to jackrabbit-api
> for other bundle to provide different implementation. Tt could well
> documented and better for third party to extend the jackrabbit.
I would do that only if there is an actual need for it. Do you have
another implementation? P
AlreadyClosedException on initial index creation
Key: JCR-2413
URL: https://issues.apache.org/jira/browse/JCR-2413
Project: Jackrabbit Content Repository
Issue Type: Bug
Components:
On Mon, Nov 30, 2009 at 9:02 AM, Felix Meschberger wrote:
> The problem of Jackrabbit Core is, that apart from implementing the
> Jackrabbit API (which is imported in the bundle), it has its internal
> API (for example the PersistenceManager interface or others). This
> internal API is not properl
Hi,
> The problem of Jackrabbit Core is, that apart from implementing the
> Jackrabbit API (which is imported in the bundle), it has its internal
> API (for example the PersistenceManager interface or others). This
> internal API is not properly separated (in terms of Java Packages) from
> impleme
HI,
Guo Du schrieb:
> On Sat, Nov 28, 2009 at 6:22 PM, Felix Meschberger wrote:
>> That's what we currently do in the Sling embedded repository bundle [1]
> Hi Felix,
>
> Thanks for the reply during weekend:)
>
> I saw all dependencies jars are embedded to jackrabbit-server bunlde.
Yes, this w
34 matches
Mail list logo
