You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2010/12/15 12:30:18 UTC
Aries Documentation
Hi all,
Currently, I'm writing an architecture draft describing how to turn
ServiceMix into a complete OSGi applications server.
Of course, it heavily uses Aries, especially for Blueprint, JPA, JTA.
My purpose is to switch my existing applications (which uses "old" JEE
architecture with EJB (Entity CMP/BMP, Session, etc), JNDI, etc) to
OSGi enterprise.
I begun to make some patches on Aries (I'm gonna raise some Jira tasks
with the patches attached).
Especially, I haven't seen any documentation sub-project, presenting the
examples in a more user friendly way with a more architecture focus.
I would like to create a documentation sub-project using Scalate (like
we have in Karaf or ServiceMix).
WDYT ?
Thanks
Regards
JB
Re: Aries Documentation
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Awesome, thanks Charles.
On my side, it's more pure OSGi Bundles deployed into Karaf.
I'm migrating EJBs to bundles, replacing Entities CMP with JPA, etc.
Regards
JB
On 12/15/2010 04:38 PM, Charles Moulliard wrote:
> Hi JB,
>
> I have created a new camel tutorial using Aries JPA, Transaction and
> Blueprint on ServiceMix. I will come back to you soon to see what we can
> share together.
>
> Regards,
>
> Charles
>
> On 15/12/10 15:56, Jean-Baptiste Onofré wrote:
>> Hi Dan,
>>
>> definitely it sounds good.
>>
>> If we agree on CMS, I will work on it.
>>
>> Regards
>> JB
>>
>> On 12/15/2010 03:38 PM, Daniel Kulp wrote:
>>> On Wednesday 15 December 2010 6:30:18 am Jean-Baptiste Onofré wrote:
>>>> Hi all,
>>>>
>>>> Currently, I'm writing an architecture draft describing how to turn
>>>> ServiceMix into a complete OSGi applications server.
>>>> Of course, it heavily uses Aries, especially for Blueprint, JPA, JTA.
>>>> My purpose is to switch my existing applications (which uses "old" JEE
>>>> architecture with EJB (Entity CMP/BMP, Session, etc), JNDI, etc) to
>>>> OSGi enterprise.
>>>>
>>>> I begun to make some patches on Aries (I'm gonna raise some Jira tasks
>>>> with the patches attached).
>>>> Especially, I haven't seen any documentation sub-project, presenting
>>>> the
>>>> examples in a more user friendly way with a more architecture focus.
>>>>
>>>> I would like to create a documentation sub-project using Scalate (like
>>>> we have in Karaf or ServiceMix).
>>>>
>>>> WDYT ?
>>>
>>> Now that Zoe has everying working very well in the CMS, why not just
>>> use that?
>>> Seriously, it can be (might already be) setup so any Apache committer
>>> can
>>> edit and stage content (only an Aries committer can "publish") so you
>>> could
>>> edit away and avoid all the patch process and such.
>>>
>>>
Re: Aries Documentation
Posted by Charles Moulliard <cm...@gmail.com>.
Hi JB,
I have created a new camel tutorial using Aries JPA, Transaction and
Blueprint on ServiceMix. I will come back to you soon to see what we can
share together.
Regards,
Charles
On 15/12/10 15:56, Jean-Baptiste Onofré wrote:
> Hi Dan,
>
> definitely it sounds good.
>
> If we agree on CMS, I will work on it.
>
> Regards
> JB
>
> On 12/15/2010 03:38 PM, Daniel Kulp wrote:
>> On Wednesday 15 December 2010 6:30:18 am Jean-Baptiste Onofré wrote:
>>> Hi all,
>>>
>>> Currently, I'm writing an architecture draft describing how to turn
>>> ServiceMix into a complete OSGi applications server.
>>> Of course, it heavily uses Aries, especially for Blueprint, JPA, JTA.
>>> My purpose is to switch my existing applications (which uses "old" JEE
>>> architecture with EJB (Entity CMP/BMP, Session, etc), JNDI, etc) to
>>> OSGi enterprise.
>>>
>>> I begun to make some patches on Aries (I'm gonna raise some Jira tasks
>>> with the patches attached).
>>> Especially, I haven't seen any documentation sub-project, presenting
>>> the
>>> examples in a more user friendly way with a more architecture focus.
>>>
>>> I would like to create a documentation sub-project using Scalate (like
>>> we have in Karaf or ServiceMix).
>>>
>>> WDYT ?
>>
>> Now that Zoe has everying working very well in the CMS, why not just
>> use that?
>> Seriously, it can be (might already be) setup so any Apache
>> committer can
>> edit and stage content (only an Aries committer can "publish") so you
>> could
>> edit away and avoid all the patch process and such.
>>
>>
Re: Aries Documentation
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Dan,
definitely it sounds good.
If we agree on CMS, I will work on it.
Regards
JB
On 12/15/2010 03:38 PM, Daniel Kulp wrote:
> On Wednesday 15 December 2010 6:30:18 am Jean-Baptiste Onofré wrote:
>> Hi all,
>>
>> Currently, I'm writing an architecture draft describing how to turn
>> ServiceMix into a complete OSGi applications server.
>> Of course, it heavily uses Aries, especially for Blueprint, JPA, JTA.
>> My purpose is to switch my existing applications (which uses "old" JEE
>> architecture with EJB (Entity CMP/BMP, Session, etc), JNDI, etc) to
>> OSGi enterprise.
>>
>> I begun to make some patches on Aries (I'm gonna raise some Jira tasks
>> with the patches attached).
>> Especially, I haven't seen any documentation sub-project, presenting the
>> examples in a more user friendly way with a more architecture focus.
>>
>> I would like to create a documentation sub-project using Scalate (like
>> we have in Karaf or ServiceMix).
>>
>> WDYT ?
>
> Now that Zoe has everying working very well in the CMS, why not just use that?
> Seriously, it can be (might already be) setup so any Apache committer can
> edit and stage content (only an Aries committer can "publish") so you could
> edit away and avoid all the patch process and such.
>
>
Re: Aries Documentation
Posted by Guillaume Nodet <gn...@gmail.com>.
Personally, I think having people submitting patches to the doc is
better as their contribution is much more by providing patches and
they can gain committership much easily on both doc or code. Or we
could do the same for the code itself and allow anyone with an icla to
commit. I think having real committers, but a lower entry bar is the
best way to go.
On Wed, Dec 15, 2010 at 18:16, Daniel Kulp <dk...@apache.org> wrote:
> On Wednesday 15 December 2010 11:20:32 am Jeremy Hughes wrote:
>> On 15 December 2010 14:38, Daniel Kulp <dk...@apache.org> wrote:
>> > Now that Zoe has everying working very well in the CMS, why not just use
>> > that?
>> > Seriously, it can be (might already be) setup so any Apache committer
>> > can edit and stage content (only an Aries committer can "publish") so
>> > you could edit away and avoid all the patch process and such.
>>
>> You're right, any committer can take a patch to the Aries website and apply
>> it. To use the patch command line they'd have to have the website checked
>> out locally rather than using the CMS web UI.
>
> In confluence, we pretty much had it setup so that anyone with an ICLA filed
> could edit directly. We cannot really do that with the CMS, but we CAN make
> it that anyone with a committer account could. Basically, make the path to
> the site content open to committers:
>
> [incubator/aries/branches/site/trunk/]
> @committers = rw
>
> [incubator/aries]
> @aries = rw
>
> but leave:
>
> [/websites/production/aries]
> @aries = rw
>
> That would allow all committers to use the CMS web frontend (if they want to,
> it's kind of not the greatest frontend) (all committers need to have an ICLA
> so legally covered) to edit and commit changes directly. Buildbot would
> build it and stage it. But only an aries committer could do the final review
> and hit the "publish" button. I guess that's one nice thing about the new
> CMS in that the svn permissions can be used to control various things.
>
> BTW: that is how the main www.apache.org website is setup. @comitters can
> edit anything, but only @members/@pmc-chairs can publish it.
>
> Anyway, it's a thought.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Aries Documentation
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 15 December 2010 11:20:32 am Jeremy Hughes wrote:
> On 15 December 2010 14:38, Daniel Kulp <dk...@apache.org> wrote:
> > Now that Zoe has everying working very well in the CMS, why not just use
> > that?
> > Seriously, it can be (might already be) setup so any Apache committer
> > can edit and stage content (only an Aries committer can "publish") so
> > you could edit away and avoid all the patch process and such.
>
> You're right, any committer can take a patch to the Aries website and apply
> it. To use the patch command line they'd have to have the website checked
> out locally rather than using the CMS web UI.
In confluence, we pretty much had it setup so that anyone with an ICLA filed
could edit directly. We cannot really do that with the CMS, but we CAN make
it that anyone with a committer account could. Basically, make the path to
the site content open to committers:
[incubator/aries/branches/site/trunk/]
@committers = rw
[incubator/aries]
@aries = rw
but leave:
[/websites/production/aries]
@aries = rw
That would allow all committers to use the CMS web frontend (if they want to,
it's kind of not the greatest frontend) (all committers need to have an ICLA
so legally covered) to edit and commit changes directly. Buildbot would
build it and stage it. But only an aries committer could do the final review
and hit the "publish" button. I guess that's one nice thing about the new
CMS in that the svn permissions can be used to control various things.
BTW: that is how the main www.apache.org website is setup. @comitters can
edit anything, but only @members/@pmc-chairs can publish it.
Anyway, it's a thought.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: Aries Documentation
Posted by Jeremy Hughes <hu...@apache.org>.
On 15 December 2010 14:38, Daniel Kulp <dk...@apache.org> wrote:
> On Wednesday 15 December 2010 6:30:18 am Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > Currently, I'm writing an architecture draft describing how to turn
> > ServiceMix into a complete OSGi applications server.
> > Of course, it heavily uses Aries, especially for Blueprint, JPA, JTA.
> > My purpose is to switch my existing applications (which uses "old" JEE
> > architecture with EJB (Entity CMP/BMP, Session, etc), JNDI, etc) to
> > OSGi enterprise.
> >
> > I begun to make some patches on Aries (I'm gonna raise some Jira tasks
> > with the patches attached).
> > Especially, I haven't seen any documentation sub-project, presenting the
> > examples in a more user friendly way with a more architecture focus.
> >
> > I would like to create a documentation sub-project using Scalate (like
> > we have in Karaf or ServiceMix).
> >
> > WDYT ?
>
> Now that Zoe has everying working very well in the CMS, why not just use
> that?
> Seriously, it can be (might already be) setup so any Apache committer can
> edit and stage content (only an Aries committer can "publish") so you could
> edit away and avoid all the patch process and such.
>
You're right, any committer can take a patch to the Aries website and apply
it. To use the patch command line they'd have to have the website checked
out locally rather than using the CMS web UI.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
Re: Aries Documentation
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 15 December 2010 6:30:18 am Jean-Baptiste Onofré wrote:
> Hi all,
>
> Currently, I'm writing an architecture draft describing how to turn
> ServiceMix into a complete OSGi applications server.
> Of course, it heavily uses Aries, especially for Blueprint, JPA, JTA.
> My purpose is to switch my existing applications (which uses "old" JEE
> architecture with EJB (Entity CMP/BMP, Session, etc), JNDI, etc) to
> OSGi enterprise.
>
> I begun to make some patches on Aries (I'm gonna raise some Jira tasks
> with the patches attached).
> Especially, I haven't seen any documentation sub-project, presenting the
> examples in a more user friendly way with a more architecture focus.
>
> I would like to create a documentation sub-project using Scalate (like
> we have in Karaf or ServiceMix).
>
> WDYT ?
Now that Zoe has everying working very well in the CMS, why not just use that?
Seriously, it can be (might already be) setup so any Apache committer can
edit and stage content (only an Aries committer can "publish") so you could
edit away and avoid all the patch process and such.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog