George, Funny you bring up this topic this week. I was planning to propose a Seam Content module this week, mostly because my schedule is finally clear enough to allow me to work on it. At this point, I have basic capabilities to inject the necessary JCR objects into CDI beans and that all works. I will admit though, I am a little biased towards ModeShape as that is the other JBoss project I work on. Cross platform support would work correctly using the service loader + repository factory approach. In addition to basic injection support, I was also looking to provide the equivalent of a SeamManagedPersistenceContext for JCR. There are also some ModeShape specific features I was bouncing around, including CDI enabled connectors, sequencers; as well as connecting their event model w/ CDI's event model. What do you think about those ideas? John On Sat, Feb 26, 2011 at 10:06 AM, George Gastaldi <gegastaldi(a)gmail.com&gt;wrote: > I was thinking to create a Seam JCR module to allow JCR (Java Content > Repositories) to be injected in code. It should work for jackrabbit as > well as modeshape or any other jcr 2.0 compliant implementation. Any > suggestions ? Comments appreciated. > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev >

George, Funny you bring up this topic this week. I was planning to propose a Seam Content module this week, mostly because my schedule is finally clear enough to allow me to work on it. At this point, I have basic capabilities to inject the necessary JCR objects into CDI beans and that all works. I will admit though, I am a little biased towards ModeShape as that is the other JBoss project I work on. Cross platform support would work correctly using the service loader + repository factory approach. In addition to basic injection support, I was also looking to provide the equivalent of a SeamManagedPersistenceContext for JCR. There are also some ModeShape specific features I was bouncing around, including CDI enabled connectors, sequencers; as well as connecting their event model w/ CDI's event model. What do you think about those ideas? John On Sat, Feb 26, 2011 at 10:06 AM, George Gastaldi <gegastaldi(a)gmail.com&gt;wrote: > I was thinking to create a Seam JCR module to allow JCR (Java Content > Repositories) to be injected in code. It should work for jackrabbit as > well as modeshape or any other jcr 2.0 compliant implementation. Any > suggestions ? Comments appreciated. > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev >

Excelent! I am thrilled to start working on it. Shane, if you could please create the project that would help. John, do you have anything implemented to push into this repository ? Em 26/02/2011, às 18:12, Shane Bryzak <sbryzak(a)redhat.com&gt; escreveu: It's great to see this collaboration take place, and it's quite obvious to me that the idea of a Seam JCR module would be appealing to many developers. George and John, would you both be willing to work on this module together? For the time being I propose that we create a Seam JCR project at github (and treat it as a sandbox for now) which you can both commit to. I can put the basic project skeleton in place so that it conforms in structure to the other Seam modules. What do you think? On 27/02/11 04:08, George Gastaldi wrote: Excelent idea. I was thinking also to connect the JCR event model to CDI. An integration with Seam Security should also be planned. I am also available to work on it. 2011/2/26 John D. Ament < <john.d.ament@gmail.com&gt;john.d.ament(a)gmail.com&gt; > George, > > Funny you bring up this topic this week. I was planning to propose a Seam > Content module this week, mostly because my schedule is finally clear enough > to allow me to work on it. At this point, I have basic capabilities to > inject the necessary JCR objects into CDI beans and that all works. I will > admit though, I am a little biased towards ModeShape as that is the other > JBoss project I work on. Cross platform support would work correctly using > the service loader + repository factory approach. In addition to basic > injection support, I was also looking to provide the equivalent of a > SeamManagedPersistenceContext for JCR. > > There are also some ModeShape specific features I was bouncing around, > including CDI enabled connectors, sequencers; as well as connecting their > event model w/ CDI's event model. > > What do you think about those ideas? > > John > > On Sat, Feb 26, 2011 at 10:06 AM, George Gastaldi <&lt;gegastaldi(a)gmail.com&gt; > gegastaldi(a)gmail.com&gt; wrote: > >> I was thinking to create a Seam JCR module to allow JCR (Java Content >> Repositories) to be injected in code. It should work for jackrabbit as >> well as modeshape or any other jcr 2.0 compliant implementation. Any >> suggestions ? Comments appreciated. >> _______________________________________________ >> seam-dev mailing list >> <seam-dev@lists.jboss.org&gt;seam-dev(a)lists.jboss.org >> <https://lists.jboss.org/mailman/listinfo/seam-dev> >> https://lists.jboss.org/mailman/listinfo/seam-dev >> > > _______________________________________________ seam-dev mailing list <seam-dev@lists.jboss.org&gt;seam-dev(a)lists.jboss.org <https://lists.jboss.org/mailman/listinfo/seam-dev>https://lists.jboss....

I prefer the latter also. seam content is also a strong name than seam jcr Em 26/02/2011, às 19:46, "John D. Ament" <john.d.ament(a)gmail.com <mailto:john.d.ament@gmail.com>> escreveu: > George, > > Yes, I have basic structure that can be put into both api and impl. > No test cases right now though. We can argue over annotation names > if you'd like :-) > > Shane, > > What top level package do you suggest? org.jboss.seam.jcr ? > org.jboss.seam.content ? I'd prefer the latter, especially if we do > eventually look at implementation specific features. > > John > > On Sat, Feb 26, 2011 at 5:17 PM, George Gastaldi > <gegastaldi(a)gmail.com <mailto:gegastaldi@gmail.com>> wrote: > > Excelent! I am thrilled to start working on it. Shane, if you > could please create the project that would help. > John, do you have anything implemented to push into this repository ? > > > > Em 26/02/2011, às 18:12, Shane Bryzak <sbryzak(a)redhat.com > <mailto:sbryzak@redhat.com>> escreveu: > >> It's great to see this collaboration take place, and it's quite >> obvious to me that the idea of a Seam JCR module would be >> appealing to many developers. George and John, would you both >> be willing to work on this module together? For the time being >> I propose that we create a Seam JCR project at github (and treat >> it as a sandbox for now) which you can both commit to. I can >> put the basic project skeleton in place so that it conforms in >> structure to the other Seam modules. What do you think? >> >> On 27/02/11 04:08, George Gastaldi wrote: >>> Excelent idea. I was thinking also to connect the JCR event >>> model to CDI. An integration with Seam Security should also be >>> planned. >>> I am also available to work on it. >>> >>> 2011/2/26 John D. Ament <john.d.ament(a)gmail.com >>> <mailto:john.d.ament@gmail.com>> >>> >>> George, >>> >>> Funny you bring up this topic this week. I was planning to >>> propose a Seam Content module this week, mostly because my >>> schedule is finally clear enough to allow me to work on >>> it. At this point, I have basic capabilities to inject the >>> necessary JCR objects into CDI beans and that all works. I >>> will admit though, I am a little biased towards ModeShape >>> as that is the other JBoss project I work on. Cross >>> platform support would work correctly using the service >>> loader + repository factory approach. In addition to basic >>> injection support, I was also looking to provide the >>> equivalent of a SeamManagedPersistenceContext for JCR. >>> >>> There are also some ModeShape specific features I was >>> bouncing around, including CDI enabled connectors, >>> sequencers; as well as connecting their event model w/ >>> CDI's event model. >>> >>> What do you think about those ideas? >>> >>> John >>> >>> On Sat, Feb 26, 2011 at 10:06 AM, George Gastaldi >>> <gegastaldi(a)gmail.com <mailto:gegastaldi@gmail.com>> wrote: >>> >>> I was thinking to create a Seam JCR module to allow JCR >>> (Java Content >>> Repositories) to be injected in code. It should work >>> for jackrabbit as >>> well as modeshape or any other jcr 2.0 compliant >>> implementation. Any >>> suggestions ? Comments appreciated. >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> >>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >>> >>> >>> >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org <mailto:seam-dev@lists.jboss.org> >>> https://lists.jboss.org/mailman/listinfo/seam-dev >> >

I think that the word 'content' is very overloaded. People will see 'Seam JCR' and most will immediately recognize what it is, however 'Seam Content' is more ambiguous. My +1 is for Seam JCR, but I'm open to what other people think. On 27/02/11 09:44, George Gastaldi wrote: > > I prefer the latter also. > seam content is also a strong name than seam jcr > > Em 26/02/2011, às 19:46, "John D. Ament" <john.d.ament(a)gmail.com&gt; escreveu: > >> George, >> >> Yes, I have basic structure that can be put into both api and impl. No test cases right now though. We can argue over annotation names if you'd like :-) >> >> Shane, >> >> What top level package do you suggest? org.jboss.seam.jcr ? org.jboss.seam.content ? I'd prefer the latter, especially if we do eventually look at implementation specific features. >> >> John >> >> On Sat, Feb 26, 2011 at 5:17 PM, George Gastaldi <gegastaldi(a)gmail.com&gt; wrote: >> Excelent! I am thrilled to start working on it. Shane, if you could please create the project that would help. >> John, do you have anything implemented to push into this repository ? >> >> >> >> Em 26/02/2011, às 18:12, Shane Bryzak <sbryzak(a)redhat.com&gt; escreveu: >> >>> It's great to see this collaboration take place, and it's quite obvious to me that the idea of a Seam JCR module would be appealing to many developers. George and John, would you both be willing to work on this module together? For the time being I propose that we create a Seam JCR project at github (and treat it as a sandbox for now) which you can both commit to. I can put the basic project skeleton in place so that it conforms in structure to the other Seam modules. What do you think? >>> >>> On 27/02/11 04:08, George Gastaldi wrote: >>>> >>>> Excelent idea. I was thinking also to connect the JCR event model to CDI. An integration with Seam Security should also be planned. >>>> I am also available to work on it. >>>> >>>> 2011/2/26 John D. Ament <john.d.ament(a)gmail.com&gt; >>>> George, >>>> >>>> Funny you bring up this topic this week. I was planning to propose a Seam Content module this week, mostly because my schedule is finally clear enough to allow me to work on it. At this point, I have basic capabilities to inject the necessary JCR objects into CDI beans and that all works. I will admit though, I am a little biased towards ModeShape as that is the other JBoss project I work on. Cross platform support would work correctly using the service loader + repository factory approach. In addition to basic injection support, I was also looking to provide the equivalent of a SeamManagedPersistenceContext for JCR. >>>> >>>> There are also some ModeShape specific features I was bouncing around, including CDI enabled connectors, sequencers; as well as connecting their event model w/ CDI's event model. >>>> >>>> What do you think about those ideas? >>>> >>>> John >>>> >>>> On Sat, Feb 26, 2011 at 10:06 AM, George Gastaldi <gegastaldi(a)gmail.com&gt; wrote: >>>> I was thinking to create a Seam JCR module to allow JCR (Java Content >>>> Repositories) to be injected in code. It should work for jackrabbit as >>>> well as modeshape or any other jcr 2.0 compliant implementation. Any >>>> suggestions ? Comments appreciated. >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>> >>>> >>>> >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >> > _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Totally agree with Emmanuel. Having some kind of CMS "stub" would be a great asset for Seam. It's something that often lack in small project. In my shop the only answer to this issue is to build all these project that need a light CMS around a portal (mostly Liferay :-( ). It's overkill. Perhaps it's beyond Seam mission, but I think that high level tools like a CMS, a wiki (what happened (or didn't happened) to wiki example in Seam 2 was very frustrating for me) or something original like Tohu can make the difference in a framework choice.