On Tue, Jan 13, 2009 at 8:45 AM, Piero Sartini <[email protected]> wrote:
> Just tried again and found the RdfMemoryStoreAssembler(). > Unfortunately, it gives me another error: > org.openrdf.query.UnsupportedQueryLanguageException: No factory available for > query language SPARQL I will look into this later today. > 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). You need to know of Assemblers, and as we discover "useful combos" we will create those, so that less tedious stuff is needed. The important view here is that the Assemblers are convenience provided by the 'library authors', and you can However, the explicity of Qi4j assembly is (believe it or not) a GoodThing. It not only gives the possibility to structure Layers and Modules, but also ensuring that you know what you think you are doing is actually what you are doing. > 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..). >From Qi4j's perspective, it can be done separately, and will never be a Core feature. Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
