You are viewing a plain text version of this content. The canonical link for it is here.
Posted to graffito-dev@incubator.apache.org by Christophe Lombart <ch...@gmail.com> on 2005/06/08 20:47:33 UTC
Google Summer of Code: Graffito Subjects
Hi all,
I would like to start some discussions on the Google Summer of code.
Do you have some ideas for Graffito ?
Here is my first ideas :
1. The Jcr Mapping tools : we need more developer in this area.
Sandro, Oliver : do you have some feedbacks to give us ? What do you
think if we propose this tools to the Google Summer code ?
2. CMS workflow engine
3. Content cache
4. Content replication engine (David, you certainly have some comments :-) )
5 Graffito application like forum, new management, article
management, .. (maybe less interesting for the Summer code).
What do you think about thoses topics ?
Raphaël, can you help us to add some topics on the Apache Google
Summer of code wiki page ? My english is so bad :-)
Kind regards,
Christophe
Re: Google Summer of Code: Graffito Subjects
Posted by Oliver Kiessler <ol...@gmail.com>.
> Here is my first ideas :
> 1. The Jcr Mapping tools : we need more developer in this area.
> Sandro, Oliver : do you have some feedbacks to give us ?
I just started working on the jcr-mapping code again this week. I have
some jira issues open that I am working on, mainly switching the code
to the new JCR spec and dynamic repository creation. From what I have
read on the jackrabbit list JSR-170 is very close to be final, so I
have been patient to see what happens. The constant spec and
Jackrabbit API changes have been a little frustrating, so this
situation should improve very soon. I think next week I will have
some first code to commit.
> What do you think if we propose this tools to the Google Summer code?
+1
Re: Google Summer of Code: Graffito Subjects
Posted by Christophe Lombart <ch...@gmail.com>.
Ok I forget the timeframe :-)
2 months is too short for my proposals.
Thanks
Christophe
On 6/9/05, Raphaël Luta <ra...@apache.org> wrote:
> Christophe Lombart wrote:
> > Hi all,
> >
> > I would like to start some discussions on the Google Summer of code.
> >
> > Do you have some ideas for Graffito ?
> >
> > Here is my first ideas :
> > 1. The Jcr Mapping tools : we need more developer in this area.
> > Sandro, Oliver : do you have some feedbacks to give us ? What do you
> > think if we propose this tools to the Google Summer code ?
> > 2. CMS workflow engine
> > 3. Content cache
> > 4. Content replication engine (David, you certainly have some comments :-) )
> > 5 Graffito application like forum, new management, article
> > management, .. (maybe less interesting for the Summer code).
> >
> > What do you think about thoses topics ?
> >
> > Raphaël, can you help us to add some topics on the Apache Google
> > Summer of code wiki page ? My english is so bad :-)
> >
>
> I sure can help but you'd need to have something that could work along
> the Summer of Code rules, ie a module that can be developped more or less
> standalone by a student within a 2 months timeframe.
>
> Also note that end of application is June 14th, so this needs to go
> to the SummerOfCode2005 wiki page *ASAP*.
>
> Also, are you OK to do the mentoring for any the above project ?
> I've already volunteered one subject (and be mentor for one student) but will
> not have bandwidth available for more.
>
>
> --
> Raphaël Luta - raphael@apache.org
> Apache Portals - Enterprise Portal in Java
> http://portals.apache.org/
>
Re: Google Summer of Code: Graffito Subjects
Posted by Raphaël Luta <ra...@apache.org>.
Christophe Lombart wrote:
> Hi all,
>
> I would like to start some discussions on the Google Summer of code.
>
> Do you have some ideas for Graffito ?
>
> Here is my first ideas :
> 1. The Jcr Mapping tools : we need more developer in this area.
> Sandro, Oliver : do you have some feedbacks to give us ? What do you
> think if we propose this tools to the Google Summer code ?
> 2. CMS workflow engine
> 3. Content cache
> 4. Content replication engine (David, you certainly have some comments :-) )
> 5 Graffito application like forum, new management, article
> management, .. (maybe less interesting for the Summer code).
>
> What do you think about thoses topics ?
>
> Raphaël, can you help us to add some topics on the Apache Google
> Summer of code wiki page ? My english is so bad :-)
>
I sure can help but you'd need to have something that could work along
the Summer of Code rules, ie a module that can be developped more or less
standalone by a student within a 2 months timeframe.
Also note that end of application is June 14th, so this needs to go
to the SummerOfCode2005 wiki page *ASAP*.
Also, are you OK to do the mentoring for any the above project ?
I've already volunteered one subject (and be mentor for one student) but will
not have bandwidth available for more.
--
Raphaël Luta - raphael@apache.org
Apache Portals - Enterprise Portal in Java
http://portals.apache.org/
Re: Google Summer of Code: Graffito Subjects
Posted by Oliver Kiessler <ol...@gmail.com>.
> this does not fit into the google summer of code context. I have a
> question regarding the mapping tool from jcr to java objects.
> What's your approach there? I think a simple mapping to nodetypes is
> quite easy but how do you include the more powerful features of jsr170
> like locking, versioning, observation etc into the mapping as these
> are the things that make jsr170 really interesting?
hi markus,
so far we only have a quick prototype. I think we definately need to
do some conceptual work upfront about the advanced features you are
talking about. Do you have any input?
regards,
oliver
Re: Google Summer of Code: Graffito Subjects
Posted by Sandro Böhme <s....@inovex.de>.
Hello Markus,
a basic idea is to have a good definition for a mapping between JCR
semantics and Java semantics (node types and classes; methods and
childnodes and so on) with the mapping model (GRFT 22).
With the node type registration component (GRFT-23) we can register new
node types out of this model.
After that it should be possible to pass the JCR features through from
classes to node types. E.g. if you want to version an image you can call
our persistence manager (GRFT-24) with your image object. Because we
know the mapping between your image class and an image node type, we can
use the versioning functionality of the image node type to version the
image object.
Regards,
Sandro
Markus Joschko wrote:
> Hi guys,
> this does not fit into the google summer of code context. I have a
> question regarding the mapping tool from jcr to java objects.
> What's your approach there? I think a simple mapping to nodetypes is
> quite easy but how do you include the more powerful features of jsr170
> like locking, versioning, observation etc into the mapping as these
> are the things that make jsr170 really interesting?
>
> Regards,
> Markus
>
> On 6/9/05, Sandro Böhme <s....@inovex.de> wrote:
>
>>Hello
>>
>> > 1. The Jcr Mapping tools : we need more developer in this area.
>> > Sandro, Oliver : do you have some feedbacks to give us ? What do you
>> > think if we propose this tools to the Google Summer code ?
>>+1
>>Maybe some well defined parts like annotations/xdoclet for generating
>>the mapping config file.
>>
>>Regards,
>>
>>Sandro
>>
>>
>>Christophe Lombart wrote:
>>
>>>Hi all,
>>>
>>>I would like to start some discussions on the Google Summer of code.
>>>
>>>Do you have some ideas for Graffito ?
>>>
>>>Here is my first ideas :
>>>1. The Jcr Mapping tools : we need more developer in this area.
>>>Sandro, Oliver : do you have some feedbacks to give us ? What do you
>>>think if we propose this tools to the Google Summer code ?
>>>2. CMS workflow engine
>>>3. Content cache
>>>4. Content replication engine (David, you certainly have some comments :-) )
>>>5 Graffito application like forum, new management, article
>>>management, .. (maybe less interesting for the Summer code).
>>>
>>>What do you think about thoses topics ?
>>>
>>>Raphaël, can you help us to add some topics on the Apache Google
>>>Summer of code wiki page ? My english is so bad :-)
>>>
>>>Kind regards,
>>>Christophe
>>>
>>>
>>
>>
>
>
Re: Google Summer of Code: Graffito Subjects
Posted by Christophe Lombart <ch...@gmail.com>.
On 6/9/05, Markus Joschko <ma...@gmail.com> wrote:
> Hi guys,
> this does not fit into the google summer of code context. I have a
> question regarding the mapping tool from jcr to java objects.
> What's your approach there? I think a simple mapping to nodetypes is
> quite easy but how do you include the more powerful features of jsr170
> like locking, versioning, observation etc into the mapping as these
> are the things that make jsr170 really interesting?
>
What kind of problem do you see ?
We want a mapping between some POJO classes (like article, news, ...)
to the JCR object model (nodes, propertie & items).
Our main idea is to have a mapping config file in which we can specify
all node types to use for each POJO/simple java classes and relations
between POJO.
Christophe
> Regards,
> Markus
>
> On 6/9/05, Sandro Böhme <s....@inovex.de> wrote:
> > Hello
> >
> > > 1. The Jcr Mapping tools : we need more developer in this area.
> > > Sandro, Oliver : do you have some feedbacks to give us ? What do you
> > > think if we propose this tools to the Google Summer code ?
> > +1
> > Maybe some well defined parts like annotations/xdoclet for generating
> > the mapping config file.
> >
> > Regards,
> >
> > Sandro
> >
> >
> > Christophe Lombart wrote:
> > > Hi all,
> > >
> > > I would like to start some discussions on the Google Summer of code.
> > >
> > > Do you have some ideas for Graffito ?
> > >
> > > Here is my first ideas :
> > > 1. The Jcr Mapping tools : we need more developer in this area.
> > > Sandro, Oliver : do you have some feedbacks to give us ? What do you
> > > think if we propose this tools to the Google Summer code ?
> > > 2. CMS workflow engine
> > > 3. Content cache
> > > 4. Content replication engine (David, you certainly have some comments :-) )
> > > 5 Graffito application like forum, new management, article
> > > management, .. (maybe less interesting for the Summer code).
> > >
> > > What do you think about thoses topics ?
> > >
> > > Raphaël, can you help us to add some topics on the Apache Google
> > > Summer of code wiki page ? My english is so bad :-)
> > >
> > > Kind regards,
> > > Christophe
> > >
> > >
> >
> >
>
Re: Google Summer of Code: Graffito Subjects
Posted by Markus Joschko <ma...@gmail.com>.
Hi guys,
this does not fit into the google summer of code context. I have a
question regarding the mapping tool from jcr to java objects.
What's your approach there? I think a simple mapping to nodetypes is
quite easy but how do you include the more powerful features of jsr170
like locking, versioning, observation etc into the mapping as these
are the things that make jsr170 really interesting?
Regards,
Markus
On 6/9/05, Sandro Böhme <s....@inovex.de> wrote:
> Hello
>
> > 1. The Jcr Mapping tools : we need more developer in this area.
> > Sandro, Oliver : do you have some feedbacks to give us ? What do you
> > think if we propose this tools to the Google Summer code ?
> +1
> Maybe some well defined parts like annotations/xdoclet for generating
> the mapping config file.
>
> Regards,
>
> Sandro
>
>
> Christophe Lombart wrote:
> > Hi all,
> >
> > I would like to start some discussions on the Google Summer of code.
> >
> > Do you have some ideas for Graffito ?
> >
> > Here is my first ideas :
> > 1. The Jcr Mapping tools : we need more developer in this area.
> > Sandro, Oliver : do you have some feedbacks to give us ? What do you
> > think if we propose this tools to the Google Summer code ?
> > 2. CMS workflow engine
> > 3. Content cache
> > 4. Content replication engine (David, you certainly have some comments :-) )
> > 5 Graffito application like forum, new management, article
> > management, .. (maybe less interesting for the Summer code).
> >
> > What do you think about thoses topics ?
> >
> > Raphaël, can you help us to add some topics on the Apache Google
> > Summer of code wiki page ? My english is so bad :-)
> >
> > Kind regards,
> > Christophe
> >
> >
>
>
Re: Google Summer of Code: Graffito Subjects
Posted by Sandro Böhme <s....@inovex.de>.
Hello
> 1. The Jcr Mapping tools : we need more developer in this area.
> Sandro, Oliver : do you have some feedbacks to give us ? What do you
> think if we propose this tools to the Google Summer code ?
+1
Maybe some well defined parts like annotations/xdoclet for generating
the mapping config file.
Regards,
Sandro
Christophe Lombart wrote:
> Hi all,
>
> I would like to start some discussions on the Google Summer of code.
>
> Do you have some ideas for Graffito ?
>
> Here is my first ideas :
> 1. The Jcr Mapping tools : we need more developer in this area.
> Sandro, Oliver : do you have some feedbacks to give us ? What do you
> think if we propose this tools to the Google Summer code ?
> 2. CMS workflow engine
> 3. Content cache
> 4. Content replication engine (David, you certainly have some comments :-) )
> 5 Graffito application like forum, new management, article
> management, .. (maybe less interesting for the Summer code).
>
> What do you think about thoses topics ?
>
> Raphaël, can you help us to add some topics on the Apache Google
> Summer of code wiki page ? My english is so bad :-)
>
> Kind regards,
> Christophe
>
>