Thanks for this Juan. I can see from the below code Interfaces what this was trying to achieve. It's a good idea, although ambitious. http://svn.apache.org/viewvc/jspwiki/branches/JSPWIKI_3_0_BRANCH/src/java/org/apache/wiki/api/
I do like the idea of an EntityManager [#3], but we'd need to decide which one to use. 1. Felix iPOJO = http://felix.apache.org/documentation/subprojects/apache-felix-ipojo.html (OSGI) 2. PicoContainer = http://picocontainer.codehaus.org - simple to use, but getting old 3. Tapestry IoC = http://tapestry.apache.org/ioc.html - might be too tied to Tapestry? 4. Spring Beans = http://www.tutorialspoint.com/spring/spring_architecture.htm - popular, and large support base (a little large) 5. EntityManager => build our own 6. Others = http://java-source.net/open-source/containers (use an existing one) Cheers, David V On Fri, Feb 13, 2015 at 10:45 PM, Juan Pablo Santos RodrÃguez < juanpablo.san...@gmail.com> wrote: > Hi, > > I think the original is in here > http://www.ecyrd.com/JSPWiki/wiki/JSPWiki3APIDesignProposal > > When JSPWiki first entered Apache incubator, one of the goals was to have a > stable API developers could code against, to ease the development of common > extensions (plugins, filters, etc). The related code went into [#1]. > > Later on, a second attempt to graduate from incubator was made, less > ambitious w.r.t. code (3.0 targetted the API, a new JCR backend, stripes > instead os JSPs, etc.). Later on, I did try to bring back the api package, > but so far is incomplete: I had in mind leaving [#2] without red squares, > so we could be able to split the main jar into several smaller modules > (i.e.: jspwiki-plugins, jspwiki-filters, etc.) The api package should then > arise by itself, but right now there is a cycle in that package, so it > smells like there is something in there which needs to be rethinked. > > Also related to this, JSPWIKI-806 [#3] aimed to simplify the WikiEngine, by > introducing an EntityManager, but the code in there needs to be completed. > > Finally, as most probably finishing this means breaking backwards > compatibility, we should change to 2.11 when this is undertaken. > > > hth, > juan pablo > > > [#1]: http://svn.apache.org/viewvc/jspwiki/branches/JSPWIKI_3_0_BRANCH/ > [#2]: > > https://analysis.apache.org/plugins/resource/139725?page=org.sonar.plugins.design.ui.page.DesignPage > [#3]: https://issues.apache.org/jira/browse/JSPWIKI-806 > > > > > > On Thu, Feb 12, 2015 at 3:32 PM, Harry Metske <harry.met...@gmail.com> > wrote: > > > I dont have it. I think it was originally from Janne and/or Andrew. > > > > Grtz. > > Harry > > Op 12 feb. 2015 09:35 schreef "David Vittor" <dvit...@gmail.com>: > > > > > Does anyone have the documentation that was originally here: > > > http://www.jspwiki.org/wiki/JSPWiki3APIDesignProposal > > > > > > This is referenced from issue JSPWIKI-303. > > > > > > I think the work was pretty massive, but I'd like to see the design to > > see > > > if it can be done in stages. Does anyone still have it? > > > > > > Cheers, > > > David V > > > > > >
