Also, can't really claim that it is "completed"... On Sep 28, 2015 09:34, "Niclas Hedhman" <[email protected]> wrote:
> I should probably send you the while larger app that was created in > parallel... > > I'll try to do that when I get back to hotel and hopefully get the laptop > to behave well enough. > On Sep 27, 2015 18:00, "Paul Merlin" <[email protected]> wrote: > >> Niclas Hedhman a écrit : >> > Well, I don't have my laptop until Saturday. >> > But that sounds like a regular Indexing module set up problem... >> > >> > I.e. Config layer's module needs the RDF indexer's configuration type. I >> > thought that was part of the library and not my app, but I could be >> wrong. >> > Or maybe because RDF shouldn't be hardwired as needed by the Restlet >> lib. >> >> Well, that was how the restlet library use the layered assembly that was >> just wrong, part of the assembly was done *after* creating the app-model >> plus uses were simply not set up ... once I fixed this the app started. >> >> BUT, it stopped immediately as no HTTP service is assembled at all. >> Looks like this new restlet library is in a dangling state. >> Either some code is missing or I did miss something obvious. >> >> /Paul >> >> >> >> > Cheers >> > Niclas >> > On Sep 23, 2015 01:14, "Paul Merlin" <[email protected]> wrote: >> > >> >> Hey, >> >> >> >> I tried to run the sample app based on the new restlet library but it >> >> fails: >> >> >> >> Could not find an EntityComposite of type >> >> org.apache.zest.library.rdf.repository.NativeConfiguration in module >> >> [Indexing Module]. >> >> >> >> I added a gradle task to run the sample app based on the new restlet >> >> library. >> >> You can reproduce by issueing: >> >> >> >> ./gradlew >> >> org.apache.zest.libraries:org.apache.zest.library.restlet:runSample >> >> >> >> I didn't take much time looking at it and didn't find the culprit. >> >> >> >> @Niclas: could you take a look? >> >> >> >> /Paul >> >> >> >> >> > >> >
