Extending Jackrabbit/JCR support

[Anne Jessel]

Hi

We have a requirement to allow the user to upload files associated with
products. These files may need to be updated, and versioning would be
useful.

I would like to use the new JCR support for this, but of course the OOTB
support is currently basic (but welcome!) and doesn't support association
of the uploaded files with a product.

I therefore plan on implementing very simple support, based on the current
Content and ProductContent entity model. I'm thinking of new ContentJcr and
ProductContentJcr entities, with relevant CRUD services. Also a helper that
fetches the file referred to by a ContentJcr.

As our needs are simple, I don't plan on implementing all the features
currently found in the Content and ProductContent ecosystem, but I thought
our implementation might be a useful starting point for others to build on.

Would it be useful for me to create a Jira with this proposal, to which I
could attach patches once we've implemented it?

And more importantly, does anyone have comments or suggestions that might
make our implementation more useful to others?

Cheers,
Anne.

--
Coherent Software Australia Pty Ltd
PO Box 2773
Cheltenham Vic 3192
Phone: [phone]
Fax: [phone]
Web: http://www.cohsoft.com.au/
Email: [hidden email]

Bonsai ERP, the all-inclusive ERP system
http://www.bonsaierp.com.au/

[Sascha Rodekamp-3]

Hi Anne,
that is a great idea. The Association between products and content in
the JCR repository is one of the next steps which i plan to implement
so every help and ideas are welcome.

For all Jackrabbit related Tickets i created an Umbrella task, which
could be found under: https://issues.apache.org/jira/browse/OFBIZ-4659

This is the best starting point for any further discussion.

I haven't thought about an solution in detail yet. But i was wondering
if an entity that represent the connection between product and content
is really necessary. What if we assign a unique node path to each
product content?
I.e. /categoryOne/SubCategory/product-1701/long-description/en

If we define a node name pattern for these kind of content a database
entry is superfluous, isn't it?

Cheers
Sascha

2012/2/20 Anne <[hidden email]>:

> Hi
>
> We have a requirement to allow the user to upload files associated with
> products. These files may need to be updated, and versioning would be
> useful.
>
> I would like to use the new JCR support for this, but of course the OOTB
> support is currently basic (but welcome!) and doesn't support association
> of the uploaded files with a product.
>
> I therefore plan on implementing very simple support, based on the current
> Content and ProductContent entity model. I'm thinking of new ContentJcr and
> ProductContentJcr entities, with relevant CRUD services. Also a helper that
> fetches the file referred to by a ContentJcr.
>
> As our needs are simple, I don't plan on implementing all the features
> currently found in the Content and ProductContent ecosystem, but I thought
> our implementation might be a useful starting point for others to build on.
>
> Would it be useful for me to create a Jira with this proposal, to which I
> could attach patches once we've implemented it?
>
> And more importantly, does anyone have comments or suggestions that might
> make our implementation more useful to others?
>
> Cheers,
> Anne.
>
> --
> Coherent Software Australia Pty Ltd
> PO Box 2773
> Cheltenham Vic 3192
> Phone: [phone]
> Fax: [phone]
> Web: http://www.cohsoft.com.au/
> Email: [hidden email]
>
> Bonsai ERP, the all-inclusive ERP system
> http://www.bonsaierp.com.au/

--

Sascha Rodekamp
    Visit the new german OFBiz Blog: http://www.ofbiz.biz
    Lynx-Consulting GmbH
    Johanniskirchplatz 6
    D-33615 Bielefeld
    http://www.lynx.de

[Anne Jessel]

Thanks for the feedback, Sascha.

I was thinking that following the existing Content pattern might be easier
for others to understand and hence migrate to. It might also be a way to
support usage patterns I have not though of.

However if we can use this as an opportunity to both improve and simplify
things with a new improved design, that would be great.

I over-simplified my requirements in my last email. I'll create a sub-task
under OFBIZ-4659 <https://issues.apache.org/jira/browse/OFBIZ-4659> as you
suggested, and add some relevant detail there for further discussion.

Cheers,
Anne.

On 21 February 2012 20:38, Sascha Rodekamp <
[hidden email]> wrote:

> Hi Anne,
> that is a great idea. The Association between products and content in
> the JCR repository is one of the next steps which i plan to implement
> so every help and ideas are welcome.
>
> For all Jackrabbit related Tickets i created an Umbrella task, which
> could be found under: https://issues.apache.org/jira/browse/OFBIZ-4659
>
> This is the best starting point for any further discussion.
>
> I haven't thought about an solution in detail yet. But i was wondering
> if an entity that represent the connection between product and content
> is really necessary. What if we assign a unique node path to each
> product content?
> I.e. /categoryOne/SubCategory/product-1701/long-description/en
>
> If we define a node name pattern for these kind of content a database
> entry is superfluous, isn't it?
>
> Cheers
> Sascha
>
> 2012/2/20 Anne <[hidden email]>:
> > Hi
> >
> > We have a requirement to allow the user to upload files associated with
> > products. These files may need to be updated, and versioning would be
> > useful.
> >
> > I would like to use the new JCR support for this, but of course the OOTB
> > support is currently basic (but welcome!) and doesn't support association
> > of the uploaded files with a product.
> >
> > I therefore plan on implementing very simple support, based on the
> current
> > Content and ProductContent entity model. I'm thinking of new ContentJcr
> and
> > ProductContentJcr entities, with relevant CRUD services. Also a helper
> that
> > fetches the file referred to by a ContentJcr.
> >
> > As our needs are simple, I don't plan on implementing all the features
> > currently found in the Content and ProductContent ecosystem, but I
> thought
> > our implementation might be a useful starting point for others to build
> on.
> >
> > Would it be useful for me to create a Jira with this proposal, to which I
> > could attach patches once we've implemented it?
> >
> > And more importantly, does anyone have comments or suggestions that might
> > make our implementation more useful to others?
> >
> > Cheers,
> > Anne.
> >
> > --
> > Coherent Software Australia Pty Ltd
> > PO Box 2773
> > Cheltenham Vic 3192
> > Phone: [phone]
> > Fax: [phone]
> > Web: http://www.cohsoft.com.au/
> > Email: [hidden email]
> >
> > Bonsai ERP, the all-inclusive ERP system
> > http://www.bonsaierp.com.au/
>
>
>
> --
>
> Sascha Rodekamp
>     Visit the new german OFBiz Blog: http://www.ofbiz.biz
>     Lynx-Consulting GmbH
>     Johanniskirchplatz 6
>     D-33615 Bielefeld
>     http://www.lynx.de
>

--
Coherent Software Australia Pty Ltd
PO Box 2773
Cheltenham Vic 3192
Phone: [phone]
Fax: [phone]
Web: http://www.cohsoft.com.au/
Email: [hidden email]

Bonsai ERP, the all-inclusive ERP system
http://www.bonsaierp.com.au/

[Anne Jessel]

Created https://issues.apache.org/jira/browse/OFBIZ-4709

We will rethink and discuss the design in-house, ignoring the current
Content pattern, and I'll update Jira with our thoughts tomorrow. More
advice from others is very welcome.

Cheers,
Anne.


On 22 February 2012 14:07, Anne <[hidden email]> wrote:

> Thanks for the feedback, Sascha.
>
> I was thinking that following the existing Content pattern might be easier
> for others to understand and hence migrate to. It might also be a way to
> support usage patterns I have not though of.
>
> However if we can use this as an opportunity to both improve and simplify
> things with a new improved design, that would be great.
>
> I over-simplified my requirements in my last email. I'll create a sub-task
> under OFBIZ-4659 <https://issues.apache.org/jira/browse/OFBIZ-4659> as
> you suggested, and add some relevant detail there for further discussion.
>
> Cheers,
> Anne.
>
>
> On 21 February 2012 20:38, Sascha Rodekamp <
> [hidden email]> wrote:
>
>> Hi Anne,
>> that is a great idea. The Association between products and content in
>> the JCR repository is one of the next steps which i plan to implement
>> so every help and ideas are welcome.
>>
>> For all Jackrabbit related Tickets i created an Umbrella task, which
>> could be found under: https://issues.apache.org/jira/browse/OFBIZ-4659
>>
>> This is the best starting point for any further discussion.
>>
>> I haven't thought about an solution in detail yet. But i was wondering
>> if an entity that represent the connection between product and content
>> is really necessary. What if we assign a unique node path to each
>> product content?
>> I.e. /categoryOne/SubCategory/product-1701/long-description/en
>>
>> If we define a node name pattern for these kind of content a database
>> entry is superfluous, isn't it?
>>
>> Cheers
>> Sascha
>>
>> 2012/2/20 Anne <[hidden email]>:
>> > Hi
>> >
>> > We have a requirement to allow the user to upload files associated with
>> > products. These files may need to be updated, and versioning would be
>> > useful.
>> >
>> > I would like to use the new JCR support for this, but of course the OOTB
>> > support is currently basic (but welcome!) and doesn't support
>> association
>> > of the uploaded files with a product.
>> >
>> > I therefore plan on implementing very simple support, based on the
>> current
>> > Content and ProductContent entity model. I'm thinking of new ContentJcr
>> and
>> > ProductContentJcr entities, with relevant CRUD services. Also a helper
>> that
>> > fetches the file referred to by a ContentJcr.
>> >
>> > As our needs are simple, I don't plan on implementing all the features
>> > currently found in the Content and ProductContent ecosystem, but I
>> thought
>> > our implementation might be a useful starting point for others to build
>> on.
>> >
>> > Would it be useful for me to create a Jira with this proposal, to which
>> I
>> > could attach patches once we've implemented it?
>> >
>> > And more importantly, does anyone have comments or suggestions that
>> might
>> > make our implementation more useful to others?
>> >
>> > Cheers,
>> > Anne.
>> >
>> > --
>> > Coherent Software Australia Pty Ltd
>> > PO Box 2773
>> > Cheltenham Vic 3192
>> > Phone: [phone]
>> > Fax: [phone]
>> > Web: http://www.cohsoft.com.au/
>> > Email: [hidden email]
>> >
>> > Bonsai ERP, the all-inclusive ERP system
>> > http://www.bonsaierp.com.au/
>>
>>
>>
>> --
>>
>> Sascha Rodekamp
>>     Visit the new german OFBiz Blog: http://www.ofbiz.biz
>>     Lynx-Consulting GmbH
>>     Johanniskirchplatz 6
>>     D-33615 Bielefeld
>>     http://www.lynx.de
>>
>
>
>
> --
> Coherent Software Australia Pty Ltd
> PO Box 2773
> Cheltenham Vic 3192
> Phone: [phone]
> Fax: [phone]
> Web: http://www.cohsoft.com.au/
> Email: [hidden email]
>
> Bonsai ERP, the all-inclusive ERP system
> http://www.bonsaierp.com.au/
>
>

--
Coherent Software Australia Pty Ltd
PO Box 2773
Cheltenham Vic 3192
Phone: [phone]
Fax: [phone]
Web: http://www.cohsoft.com.au/
Email: [hidden email]

Bonsai ERP, the all-inclusive ERP system
http://www.bonsaierp.com.au/

[Jacques Le Roux]

Hi Anne,

Did you finally work on this?

Thanks

Jacques


Le 21/02/2012 à 10:38, Sascha Rodekamp a écrit :

> Hi Anne,
> that is a great idea. The Association between products and content in
> the JCR repository is one of the next steps which i plan to implement
> so every help and ideas are welcome.
>
> For all Jackrabbit related Tickets i created an Umbrella task, which
> could be found under: https://issues.apache.org/jira/browse/OFBIZ-4659
>
> This is the best starting point for any further discussion.
>
> I haven't thought about an solution in detail yet. But i was wondering
> if an entity that represent the connection between product and content
> is really necessary. What if we assign a unique node path to each
> product content?
> I.e. /categoryOne/SubCategory/product-1701/long-description/en
>
> If we define a node name pattern for these kind of content a database
> entry is superfluous, isn't it?
>
> Cheers
> Sascha
>
> 2012/2/20 Anne <[hidden email]>:
>> Hi
>>
>> We have a requirement to allow the user to upload files associated with
>> products. These files may need to be updated, and versioning would be
>> useful.
>>
>> I would like to use the new JCR support for this, but of course the OOTB
>> support is currently basic (but welcome!) and doesn't support association
>> of the uploaded files with a product.
>>
>> I therefore plan on implementing very simple support, based on the current
>> Content and ProductContent entity model. I'm thinking of new ContentJcr and
>> ProductContentJcr entities, with relevant CRUD services. Also a helper that
>> fetches the file referred to by a ContentJcr.
>>
>> As our needs are simple, I don't plan on implementing all the features
>> currently found in the Content and ProductContent ecosystem, but I thought
>> our implementation might be a useful starting point for others to build on.
>>
>> Would it be useful for me to create a Jira with this proposal, to which I
>> could attach patches once we've implemented it?
>>
>> And more importantly, does anyone have comments or suggestions that might
>> make our implementation more useful to others?
>>
>> Cheers,
>> Anne.
>>
>> --
>> Coherent Software Australia Pty Ltd
>> PO Box 2773
>> Cheltenham Vic 3192
>> Phone: [phone]
>> Fax: [phone]
>> Web: http://www.cohsoft.com.au/
>> Email: [hidden email]
>>
>> Bonsai ERP, the all-inclusive ERP system
>> http://www.bonsaierp.com.au/
>
>