Hi Michi,
On 8/26/06, Michael Wechner [EMAIL PROTECTED] wrote:
well, it might depend on how much one believes in JCR as one fits all
solution.
I don't believe that JCR is a one fits all, actually you'll find
many posts to jackrabbit ML from me where I try to explain problems I
faced while
Hi,
On 8/27/06, Edgar Poce [EMAIL PROTECTED] wrote:
On 8/26/06, Michael Wechner [EMAIL PROTECTED] wrote:
Even if JCR is a great thing, it might not fit all purposes and one
might be glad to have an alternative entry point,
I agree with you. However I tend to think JCR is a good match for
Hi,
On 8/27/06, Edgar Poce [EMAIL PROTECTED] wrote:
To name a few first hand problems I faced:
[...]
That's a very good summary of the problem areas I've been facing as
well. Would you like to follow up with that on the Jackrabbit mailing
list? I think it would make for a great discussion
Hi David,
On 8/26/06, David Sean Taylor [EMAIL PROTECTED] wrote:
If we decide that the Graffito API is redundant and no longer necessary
to maintain, then an effort would need to be made to deprecate the API,
and move the graffito portlet applications written to that API to the
JCR API.
Hi,
On 8/27/06, Jukka Zitting [EMAIL PROTECTED] wrote:
The JCR API is unfortunately not too easy to implement on top of
existing content repositories or content access mechanisms. My
understanding is that the goal of the API is more to provide a
standard and feature-rich platform for building
On 8/27/06, Jukka Zitting [EMAIL PROTECTED] wrote:
I'm not too familiar with the Alfresco
codebase, but that's also a possible alternative to look at.
IANAL but have you seen the license?, I don't think I could ever use it :(
from http://dev.alfresco.com/legal/licensing/apl/
.. However, in
