On Sat, Oct 25, 2008 at 17:56, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> So the "real use-case" (once all the noise and "solutions" are filtered out)
> is;
>
> "Initialization of immutable private mixins are cumbersome and needs a
> better solution."
>
> I suspect this is currently not supported, but a lot easier to bring
> up for discussion than tossing Property out, placing implementation
> details in context interfaces and what not.
For completeness. Query will look like this:
interface HabbaZootEntity extends HabbaZoot, EntityComposite
{
}
interface HabbaZoot extends Habba, Zoot
{
}
interface HabbaState
{
Property<Date> prop1();
}
interface ZootState
{
Property<Date> prop2();
}
QueryBuilder builder = unitOfWorkFactory.newQueryBuilder( HabbaZoot.class );
HabbaState habbaState = builder.stateFor( HabbaState.class );
ZootState zootState = builder.stateFor( ZootState.class );
builder.where( QueryExpressions.and(
QueryExpressions.equals( habbaState.prop1(), value1 ),
QueryExpressions.equals( zootState.prop2(), value2 )
);
Query query = builder.newQuery();
Regards,
Edward Yakop
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
