On Mon, Nov 22, 2010 at 7:54 PM, Niclas Hedhman <[email protected]> wrote: > On Mon, Nov 22, 2010 at 4:28 PM, Rickard Öberg <[email protected]> wrote: > >> The idea is that common cases should be simple to do. I have lots of helpers >> in Inputs/Outputs/Transforms for the I/O API as well. I have recently also >> added Iterables and Specifications which function as mini-DSL's. > > Fair enough, but I don't think one is exclusionary of the other. That > said, I won't criticize more without a counter-proposal...
Question; ServiceQualifier has a DSL-like construct, but a. is that ever used?? b. AFAICT, it will also fail; ref = first( withTags( "SuperService" ).whereAvailable(), services ); will not produce the expected result.... I suggest that we go with the Query Builder pattern; ref = ServiceQualification.among(services).withTags( "SuperService").whereAvailable().first(); And isn't it reasonable to move the DSL style outside of Qi4j Core, and allow community evolution of DSL expressions? IIUIC, Qi4j Core only needs an interface with the qualifies() method... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
