On 15 December 2010 14:38, Daniel Kulp <[email protected]> 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 > [email protected] > http://dankulp.com/blog >
