On Fri, Aug 1, 2008 at 11:32 PM, Richard Wallace
<[EMAIL PROTECTED]> wrote:
> Hmm... I'm not sure on that one. We do need to override the
> PropertyAccessor so we don't have to use the lame JavaBean conventions, but
> I'm not sure how we can do it for all Objects. Isn't that ok though? Is it
> even possible to have a Property or Association on something that isn't a
> Composite?
If we have this setup.
public interface Item extends Nameable
{
}
public interface ItemEntity extends Item, Entity
{
}
QueryExpressions#templateFor( Item.class ), will not return a proxy
that is cast-able to Composite.
And, I'm not sure whether EntityBuilder#stateOfComposite() will return
a proxy instance of EntityComposite
if we do uow.newEntityBuilder( Item.class ), instead of
uow.newEntityBuilder( ItemEntity.class )
Regards,
Edward Yakop
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
