On 2009-12-08 13.12, philippe van dyck wrote:
On 2009-12-07 23.19, philippe van dyck wrote:
Ok, I found something fishy, dunno if it is the only source of the problem.
In ValueCompositeType :
if (!value.getClass().getInterfaces()[0].getName().equals( type.name() ))
Values will only implement one interface, so order is not important. See
previous response on why it uses SerializableType.
Is this a good practice ? I modeled some values to have HasEmail or HasDetails
interfaces.
Those interfaces are then used on the wicket layer to draw the UI (adding a like to the
detail and an "email me" link too)
What I meant is that the ValueComposite will always only have one
interface (the ValueComposite interface), but that might in turn extend
others (like HasEmail and HasDetails). There is just one "root"
interface, which is the composite (same for services, entities and
transients).
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
