Piero Sartini wrote: > Am Samstag 10 Januar 2009 05:28:37 schrieb Niclas Hedhman: >> On Sat, Jan 10, 2009 at 1:41 AM, Piero Sartini <[email protected]> > wrote: >>> That gives me an >>> Exception in thread "main" org.qi4j.bootstrap.AssemblyException: May not >>> register EntityComposites as a >>> Composite:org.qi4j.library.rdf.repository.NativeConfiguration >> What a bummer, we don't have testcases for the "Assembly" helper classes... > > Just tried again and found the RdfMemoryStoreAssembler(). > Unfortunately, it gives me another error: > org.openrdf.query.UnsupportedQueryLanguageException: No factory available for > query language SPARQL
Sounds like a missing dependency. Are you using Maven? For indexing purposes it should be enough to have a dependency on the qi4j-indexing-rdf module, which *should* bring in the proper RDF libraries. > Guess I missed to configure something in my assemblers...? Mhmm. It's more > work to configure qi4j and putting all the pieces together than it is to > write > the application ;-) Why do I need to know about RdfIndexing, JdbmStore's, > Configuration Entities, and all this stuff? I hate XML configs, but such a > config file would be great now (because you can see what options are > available). > > Now I think we need a framework on top of qi4j that simplifies the > configuration, delivers suitable defaults and does some convention over > configuration for the assemblies as well (tapestry 5 style..). It sounds like what you need is a sample Maven project that sets up the minimal dependencies for a "typical" project (if such a thing exists). Isn't that what Maven archetypes is for? Anyone knows how to create those, and would it be a good idea to do so? /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
