Started this thread in users but it's getting a bit nasty now:
We got jackrabbit 1.4 here and are running it as a webdav server.
When I try to add a property to a collection using PROPPATCH the new
property is not persisted. The modification date is update.
I looked at the ItemImpl.save method a
>From what I've seen in the code so far jackrabbit's error logging consists
mostly of logging the messages of the exceptions. In a production system I'd
consider that a bit scary. I think it would be better to log the
stacktraces.
Just my A$ 0.02
What do you think
Cheers
roland
Migrate to Lucene 2.3
-
Key: JCR-1363
URL: https://issues.apache.org/jira/browse/JCR-1363
Project: Jackrabbit
Issue Type: Task
Affects Versions: 1.4
Reporter: tomoharu fujita
Fix For: 1.4.1, 1
[
https://issues.apache.org/jira/browse/JCR-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Schmidt updated JCR-1362:
---
Component/s: sql
jackrabbit-core
> DatabaseJournal improperly finds tables in external
[
https://issues.apache.org/jira/browse/JCR-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565982#action_12565982
]
Chris Schmidt commented on JCR-1362:
More of a refactoring request, but could the code th
[
https://issues.apache.org/jira/browse/JCR-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565980#action_12565980
]
Chris Schmidt commented on JCR-1362:
I have an implementation that I can include for this
DatabaseJournal improperly finds tables in external schemas when used on Oracle
---
Key: JCR-1362
URL: https://issues.apache.org/jira/browse/JCR-1362
Project: Jackrabbit
Lock test assumes that changes in one session are immediately visible in
different session
--
Key: JCR-1361
URL: https://issues.apache.org/jira/browse/JCR-1361
Pr
Tuesday 05 February 2008 22:50:14 Christophe Lombart написав:
[skip]
> I know
> I have the first (and very small) tutorial. I plan to publish it this week
> but I need more time due to my daily activities :-)
> Jackrabbit OCM will be more adopted if we find more contributors. They are
> still many
On Feb 5, 2008 9:06 PM, Alex Lukin <[EMAIL PROTECTED]> wrote:
> Tuesday 05 February 2008 20:53:46 Christophe Lombart написав:
> [skip]
> > Alex,
> >
> > Jackrabbit OCM is also supporting the annotation like JCROM since a long
> > time.
> > XML support is not mandatory.
> Christophe,
> I know becau
Tuesday 05 February 2008 20:53:46 Christophe Lombart написав:
[skip]
> Alex,
>
> Jackrabbit OCM is also supporting the annotation like JCROM since a long
> time.
> XML support is not mandatory.
Christophe,
I know because I already use it. It works somehow for me and I prefer official
things even w
We've been using the OCM libraries with a certain amount of success.
We have heavily leveraged using the spring modules for configuration
and have used the repository pattern with a few base classes which
handle most of the OCM specific implementations. Our domain model maps
fairly cleanly
Hi,
On Feb 5, 2008 8:53 PM, Christophe Lombart <[EMAIL PROTECTED]> wrote:
> Concerning JPA, we can make a small study to check if JPA is really a good
> solution for a JCR backend ... if someone have time :-)
One very interesting use case for that would be to make Apache Roller
run on top of Jac
On Feb 5, 2008 6:21 PM, Alexandru Popescu ☀ <
[EMAIL PROTECTED]> wrote:
>
> (to Christophe)
>
> > There are commons points between both solutions in term of annotations
> but
> > JCROM doesn't support lazy loading, interface and ínheritance, custom
> > converter, Futhermore Jackrabbit OCM mak
Tuesday 05 February 2008 19:24:16 Alexandru Popescu ☀ написав:
> Oops... it looks like I've left something unfinished...
>
> On Feb 5, 2008 7:21 PM, Alexandru Popescu ☀
>
> <[EMAIL PROTECTED]> wrote:
> > (to Alex Lukin):
> > > 2) JPA is based on relational approach and does not work properly with
>
Oops... it looks like I've left something unfinished...
On Feb 5, 2008 7:21 PM, Alexandru Popescu ☀
<[EMAIL PROTECTED]> wrote:
>
> (to Alex Lukin):
>
> > 2) JPA is based on relational approach and does not work properly with
> > tree-like structures we use often with JCR
>
> That's partly correct
I am trying to summarize my comments below...
(to Alex Lukin):
> 1) Current ocm in jackrabbit source tree does not have anything in common
> with JPA annotation and/or ideology
Because it started on that direction. That doesn't mean it is the best
approach. But falling back again to the Hiberna
Alex Lukin wrote:
Sounds good again but:
1) Current ocm in jackrabbit source tree does not have anything in common with
JPA annotation and/or ideology
2) JPA is based on relational approach and does not work properly with
tree-like structures we use often with JCR
3) JPA is monstrous as curre
[
https://issues.apache.org/jira/browse/JCR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565754#action_12565754
]
Esteban Franqueiro commented on JCR-1154:
-
The following javadoc comment should be re
hi alex,
> I don't want to sound as I don't appreciate this effort, but I would
> have thought that people looking into
> this direction would firstly consider the JPA annotations firstly and
> then introduce new/custom annotations for special cases (I think a
> parallel with Hibernate and its JPA
Tuesday 05 February 2008 14:12:03 Alexandru Popescu ☀ написав:
[skip]
> I do believe that this initiatives are helpful for the JCR community,
> but I would encourage people to check how much is possible to be done
> in the JPA direction.
[skip]
Sounds good again but:
1) Current ocm in jackrabbit
There are commons points between both solutions in term of annotations but
JCROM doesn't support lazy loading, interface and ínheritance, custom
converter, Futhermore Jackrabbit OCM makes more abstraction on the JCR
API which is not the case of JCROM.
I personnally perfer to maximize this kind
Hi,
On Feb 5, 2008 2:12 PM, Alexandru Popescu ☀
<[EMAIL PROTECTED]> wrote:
> I do believe that this initiatives are helpful for the JCR community,
> but I would encourage people to check how much is possible to be done
> in the JPA direction.
+1 JPA support would go a long way simplifying JCR int
Hi David and thanks for sharing this!
I don't want to sound as I don't appreciate this effort, but I would
have thought that people looking into
this direction would firstly consider the JPA annotations firstly and
then introduce new/custom annotations for special cases (I think a
parallel with Hi
hi all,
Olafur Gauti Gudmundsson pointed me today to his effort called JCROM
(pronounced "Jack-rom"). [1]
I am excited about the refreshing, quick and simple annotation based
approach [2]
and would like to find out what everybody's thoughts are on possibly
finding synergies
with the ocm framework
[
https://issues.apache.org/jira/browse/JCR-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565704#action_12565704
]
Sébastien Deleuze commented on JCR-1043:
Hi,
After working on this with Christophe,
[
https://issues.apache.org/jira/browse/JCR-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1300:
Component/s: jackrabbit-jcr-server
> spi2dav Improve performance for large binary properties
> --
[
https://issues.apache.org/jira/browse/JCR-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1300:
Component/s: (was: jackrabbit-spi)
contrib
(wrong component)
> spi2dav Improve performance for
[
https://issues.apache.org/jira/browse/JCR-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1348:
Component/s: jackrabbit-jcr-server
> simple-webdav: DAV:auto-version property not handled properly
>
[
https://issues.apache.org/jira/browse/JCR-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565694#action_12565694
]
angela commented on JCR-1352:
-
i don't have any preference. the only thing you have to make sure
[
https://issues.apache.org/jira/browse/JCR-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1345:
---
Fix Version/s: 1.4.1
Merged to the 1.4 branch in revision 618604.
> ClassCastException when updating p
[
https://issues.apache.org/jira/browse/JCR-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1335:
---
Affects Version/s: 1.0
1.0.1
1.1
1.
[
https://issues.apache.org/jira/browse/JCR-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1360:
Summary: Parsing built-in CND and XML nodetypes does not result in equal
nt-definitions (was: Parsing built-in CND a
[
https://issues.apache.org/jira/browse/JCR-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1360:
Attachment: 1360.patch
test
> Parsing built-in CND and XML nodetypes does not result in equal NodeType
> definition
[
https://issues.apache.org/jira/browse/JCR-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1357:
---
Fix Version/s: (was: 1.4.1)
1.5
> Create "quick start" developer bundles for mod
Parsing built-in CND and XML nodetypes does not result in equal NodeType
definitions
Key: JCR-1360
URL: https://issues.apache.org/jira/browse/JCR-1360
Project: Jackr
[
https://issues.apache.org/jira/browse/JCR-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1346.
Resolution: Fixed
Resolving as fixed based on comments above.
> InternalValue.createCopy for binary
[
https://issues.apache.org/jira/browse/JCR-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1351.
Resolution: Duplicate
Fix Version/s: (was: 1.4.1)
Resolving this as a duplicate of JCR-134
[
https://issues.apache.org/jira/browse/JCR-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1330:
---
Component/s: jackrabbit-site
Fix Version/s: 1.4.1
> repository.xml DTD doesn't allow element
> -
[
https://issues.apache.org/jira/browse/JCR-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565682#action_12565682
]
Jukka Zitting commented on JCR-1046:
Merged to the 1.4 branch in revision 618599.
> Non-
Hi,
On Feb 5, 2008 11:58 AM, Dominique Pfister <[EMAIL PROTECTED]> wrote:
> I was hoping that the following would make it into 1.4.1 too:
>
> [JCR-1358] Cluster revision file not closed on repository shutdown
>
> When running a lot of tests that start up and shutdown a repository
> very often, it
Hi,
On Feb 5, 2008 11:44 AM, Alexander Nesterov <[EMAIL PROTECTED]> wrote:
> I would like to know whether it's feasible to fix JCR-1359 in 1.4.1
> release as it's quite critical case for our project? If not, then
> could someone give at least rough estimates when JCR-1359 is planned
> to be fixed?
Hi Jukka,
I was hoping that the following would make it into 1.4.1 too:
[JCR-1358] Cluster revision file not closed on repository shutdown
When running a lot of tests that start up and shutdown a repository
very often, it can become quite a nuisance.
WDYT?
Kind regards
Dominique
On 30/01/2008
[
https://issues.apache.org/jira/browse/JCR-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565678#action_12565678
]
Jukka Zitting commented on JCR-1323:
Merged to the 1.4 branch in revision 618589.
> When
Hello,
On Jan 30, 2008 4:55 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> Hi,
> Let me know if any other issues should be included. I'd like to target
> already next week for this patch release.
>
I would like to know whether it's feasible to fix JCR-1359 in 1.4.1
release as it's quite critical
45 matches
Mail list logo
