Hi.
During my regression tests with JCR2SPI and my custom SPI implementation
I found a difference that may indicate a missing feature in SPI. Or not.
What happens is that I have a custom node type which internally holds a
potentially huge amount of property definitions, and for that reason,
hi
sorry. i reread you mail multiple times, and i don't get
your point.
here is what jsr170 defines:
- that PropertyDefinition.getRequiredType() may be one of
STRING, BINARY, DATE, LONG, DOUBLE, NAME, PATH, REFERENCE,
BOOLEAN or UNDEFINED.
- If PropertyDefinition.getRequiredType() is
Angela Schreiber schrieb:
hi
sorry. i reread you mail multiple times, and i don't get
your point.
Sorry, I'll try to do better this time.
here is what jsr170 defines:
- that PropertyDefinition.getRequiredType() may be one of
STRING, BINARY, DATE, LONG, DOUBLE, NAME, PATH, REFERENCE,
Jukka Zitting schrieb:
Hi,
On 11/22/06, Julian Reschke [EMAIL PROTECTED] wrote:
No, the point is that in JSR-170 it is possible that for a given node
type N, the NodeType interface will only return residual property
definitions (because the set of property definitions on this node type
may be
No, the point is that in JSR-170 it is possible that for a given node
type N, the NodeType interface will only return residual property
definitions (because the set of property definitions on this node type
may be very large), while Property.getPropertyDefinition() will return a
non-residual
