Hi Fabian, looks like you chose a big one for starting ;-)
LDCache plugs into the Sesame-Sail stack to automatically retrieve remote resources that are available in the local triple store. Sesame does not use CDI but the build-in Java ServiceLoader [1], so plugging in there is not as easy. On the other hand: why do you want to implement module similar to LDCache? What feature do you need that can't be solved using LDCache - for me, your "exteral datasource" module sounds exactly like LDCache in action... Best, Jakob [1] http://docs.oracle.com/javase/6/docs/api/java/util/ServiceLoader.html On 2 September 2014 09:06, Fabian Cretton <[email protected]> wrote: > Hi, > > I would like to implement a module that is similar to the LDCache (following > the previous discussions with Sergio about the overLOD project). > I am currently reading about the LDCache functionalities here > http://marmotta.apache.org/ldcache/ > and having a look at the code. > > (It is a pretty steep curve for me to apprehend the Marmotta project, but I > think it is worse it instead of starting from scratch) > > As I am new to this kind of project infrastructure, is there anything I > should read to better understand the all framework ? Maybe Java JEE > tutorials as the project description says "The Apache Marmotta Platform is > implemented as a light-weight Service-Oriented Architecture (SOA) using the > CDI/Weld service framework (i.e. the core components of Java EE 6). " > > Then, to create the new module, would it be a good idea to duplicate the > LDCache files (libraries and platform I guess) and modify them, or should I > better start from a new empty module as described here: > http://wiki.apache.org/marmotta/Customizing#Modules > > Thank you for any help > Fabian > > >>>> Sergio Fernández<[email protected]> 27.08.2014 16:31 >>> > Hi Fabian, > > On 27/08/14 14:49, Fabian Cretton wrote: >> My first goal was: to build the all project locally, run my locally >> built Marmotta, and then start adding components. >> But my first concern now that I am digging deeper, is that Marmotta is >> a pretty big project (about 80 projects), and so you might recommand me >> not to import the main "pom.xml" in my eclipse environment, but start >> smaller ? > > Then start from the platform modules. > >> If there is already a documentation about how to procede, thank you to >> point me there, I didn't find any by myself. > > Well, the overall build process is entirely manage by Maven, check > http://marmotta.apache.org/installation#source > >> Nevertheless, I do have problems and errors in Eclipse, and hope you >> can help me about that. > > Eclipse should be able to manage such king of size of modules with Maven. > >> The first problems I do have, are with many "Plugin execution not >> covered by lifecycle configuration" errors. > > Some plugin lifecycles might not be supported inside Eclipse. Just > ignore it, you should not need them. > >> Than I do have 6-7 : "Project build error: Non-resolvable parent POM: >> Could not find artifact >> org.apache.marmotta:marmotta-parent:pom:3.2.1-SNAPSHOT and >> 'parent.relativePath' points at wrong local POM pom.xml >> /marmotta-backend-sparql line 23 Maven pom Loading Problem" >> and here I am pretty confused: it seems that some POM files are not >> up-to-date in this 3.3.0 current version, as they do still point to a >> "3.2.1" parent POM file, but the parent is already in its "3.3.0" >> version ? > > Sorry for the error. Those modules are out of the default profile, so > the release plugin did not update the versions accordingly. It's already > fixed in the develop branch; please update your fork. > >> Then, apart from those Maven errors, I do have a few java errors with >> many "imports" or "types" which can't be resolved, and this seems very >> strange to me. But maybe solving the main Maven problems here above >> would correct that ? > > All dependencies are available from Maven central. Try to make a "maven > install" from the root. > >> A first goal for me would be to update the Marmotta's main menu so that >> under "Others", next to "Linked Data Caching", I could have a "External >> Data Sources" menu and then work an that new module as discussed earlier >> with you. > > Then you need to create a custom module and add it to your custom webapp > launcher. All the process is supported by Maven artifacts, as described at: > > http://wiki.apache.org/marmotta/Customizing#Modules > > Hope that helps. > > Cheers, > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 660 2747 925 > e: [email protected] > w: http://redlink.co
