jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hsp <piccina...@ibest.com.br>
Subject Re: Exception in adding mixin with same name property
Date Thu, 27 Feb 2014 19:20:18 GMT
I defined node types always with xml, basically can resume as:


 		

The name "prop:theme" is ambigous, but the values would be different. Let's
say that this was a "mistake" when defined the mixin types...
Initially the nodes (typePrimary) would only get one of those mixin, but now
the rule has changed and the node can get both mixin, but because the
constraint the use case is broken...

I Appreciate some ideas,
Best Regards!




--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Exception-in-adding-mixin-with-same-name-property-tp4660381p4660384.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Mime
View raw message