On Jul 22, 2011, at 3:06 PM, Sebastian Schaffert wrote: > Dear all, > > following up the discussion in the community workshop in Paris, I would like > to formally offer the integration of our Linked Media Framework into Apache > Stanbol.
Thanks for moving this forward Sebastian. I'm one of the people who asked for this merge to be discussed during the Paris Workshop, and I'm really happy that this is discussed now. > Difficulties I see at the moment (just to mention these...): > - technological issue: LMF is currently not using OSGi, but it uses a Gradle > build system, OSGi is not a build system (ok, there is a build system specific to OSGi, called BND, and maybe that's what people who are really committed to OSGi should be using - but that's another story). Stanbol uses Maven. I don't think there is anything fundamentally wrong with Gradle (and there are many things that are wrong with Maven, but that's also another story), but Maven is pretty much the standard, and it makes sense to migrate the LMF build system to Maven. Apparently, there's a plugin for that, so that shouldn't be too much work: http://www.gradle.org/maven_plugin.html > Java 6 EE dependency injection (CDI) and a typical Java EE architecture which > is incompatible with OSGi for now; Yes, this is probably more intrusive. > one of our selling points is also "easy setup" and "lightweight", so I would > not really like to change this for a complicated architecture ... Some people would argue that there isn't much that's not "lightweight" with OSGi (OSGi services are just POJOs), and I don't think OSGi (for the part we're using in Stanbol at least), is more "complicated" that CDI. They probably should not be seen as competing, but as complementary approaches, and actually using DI with OSGi services is something that's already covered with SCR or iPOJO. I don't have experience mixing CDI and OSGi, though (and that's something that could be useful for Nuxeo, so we're willing to investigate). Googling for "OSGi+CDI" gives some interesting links: http://blogs.oracle.com/sivakumart/entry/typesafe_injection_of_dynamic_osgi http://mathieuancelin.github.com/weld-osgi/ So it's definitively something people are wanting to do. > - license issue: LMF might still use libraries that are released under > incompatible licenses, so this needs to be checked. In particular, Hibernate > is still licensed under LGPL, and it is one of the core libraries of the LMF; > porting to other persistence frameworks might require a lot of effort I don't know what's the ASF view on Hibernate. What are the alternatives ? EclipseLink is a viable alternative, I think, but it's licensed under the EPL. Does the ASF have a JPA project that's mature enough to replace Hibernate (OpenJPA ?) ? > - organisational issue: LMF is developed in several projects that have their > specific goals; we will in some way need to still be able to follow our goals > in these projects, e.g. by appropriate Stanbol extensions; all software > developed in these projects is Open Source though... I think this would be very good for the project, because it would definitively allow us to check the mark "doesn't depend on IKS to move forward". S. -- Stefane Fermigier, Founder and Chairman, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com/ - +33 1 40 33 79 87 - http://twitter.com/sfermigier Join the Nuxeo Group on LinkedIn: http://linkedin.com/groups?gid=43314 New Nuxeo release: http://nuxeo.com/dm54 "There's no such thing as can't. You always have a choice."
