ItÂ’s most likely that somewhere along the way in the future one might decide to modify the source code but in any case what are the constraints or difficulties involve in making a move to JPOX (JDO 2.0)? We also may have to look into Roller being able to integrate well with other programs that may be building with open standards. For example I realized that the demo version of Roller with wiki can co-exist nicely in some environment. Upon recent development at the ASF with JackRabbit and Derby almost and out of incubator status it will be good to build ASF model. I read to good articles that made use theses technologies; A simple wiki built on a solid foundation I wrote an article to both of these Authors to see if we can open up a project space at www.java.net and start a project name Qwiki; building wiki app on open standards that makes it easier to integrate with other applications such as Roller. Below is the email I sent to these Authors.
Hello Titus/Daniel, How are you? I have read both your articles posted on IBM Developers website. I have been looking at other wiki such as JSPwiki at www.jspwiki.org and I realized the advantages of using and integrating both your example implement in a single application. The reason for this is that Titus's example is built upon industry standard's Apache JackRabbit content repository (http://www-128.ibm.com/developerworks/java/library/j-jcr/#4) whereas Daniel's is built upon Apache Derby (https://www6.software.ibm.com/developerworks/education/os-ad-wiki/). These two approaches complements each other in the respect that if the wiki application is built upon the JackRabbit with underlying Derby database it makes this application robust since it is built upon a much more solid foundation. With this underling foundation adding additional applications such as the Roller Blog application is easier and thus creates value as additional application can be added. This could be a start of a killer application and other good ideas that are likely to be incorporated in the future. However I am an intermediate Java programmer and more of a management information systems and a venture person. I am thinking of opening up a project space at www.java.net where both of your examples will be integrated. Also I would like to know if any of you may have some free time to contribute to this project since it is both your works. Thanks -Ransford Matt Raible <[EMAIL PROTECTED]> wrote:On 10/20/05, Henri Yandell wrote: > On 10/20/05, paksegu wrote: > > Hello Roller World, > > What's the advantages and disadvantages of using JPOX (JDO 2.0) verses > > Hibernate? > > One difference is the licence of the software. > > Hibernate is LGPL, JPOX is Apache 2. > > The difference to the user is that if you wish to ship a modified > version of Apache Roller called Paksegu Blog Server (as Apache and > Roller are not usable in your product name); then with JPOX you can > just modify their code and ship it with your Paksegu Blog Server > (again, not calling it JPOX; but you would probably just inline it > into PBS) whereas with Hibernate the legalities are less > clear/favourable to the downstream rebrander. It's my understanding that "shipping" with Hibernate is only an issue if you modify Hibernate's code. If you don't modify it, there's no issues. Matt > > So for some of our users, having less questions on the licence of the > dependencies simplifies things a lot. Allowing our users to ship > versions of our software as the basis of their own is one of the major > foundation stones of the ASF. > > Obviously there are technical differences too; but the ASF's awareness > of downstream rebranding is the major reason for pressure to have > alternatives to Hibernate. > > That sound right to everybody? > > Hen > Ransford Segu-Baffoe [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.noqturnalmediasystems.com/ --------------------------------- Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
