i think this is only a theoretical problem. usualy the application
knows with what kind of properties it deals.
regards, toby
On 6/20/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 6/20/06, Marcel Reutegger <[EMAIL PROTECTED]> wrote:
> On 6/19/06, David Kennedy <[EMAIL PROTECTED]> wrote:
Hi,
On 6/20/06, Marcel Reutegger <[EMAIL PROTECTED]> wrote:
On 6/19/06, David Kennedy <[EMAIL PROTECTED]> wrote:
> If I have a node, the name of a property and a single value, how can I
> determine if I need to add the value to an array and use the multivalue
> setter or not?
You'll have to ask
On 6/19/06, David Kennedy <[EMAIL PROTECTED]> wrote:
If I have a node, the name of a property and a single value, how can I
determine if I need to add the value to an array and use the multivalue
setter or not?
You'll have to ask the NodeType of the node:
NodeType nt = node.getPrimaryNodeType(
The only solution to your problem would be to have some metadata info about
them, and so you could look if the property was single or multivalued.
Obviously the real problem is how to find if a property is single/multiple
if such property does not exist so I cannot agree more with Jukka. Having a
Hi,
On 6/20/06, David Kennedy <[EMAIL PROTECTED]> wrote:
If I have a node, the name of a property and a single value, how can I
determine if I need to add the value to an array and use the multivalue
setter or not?
Good question. Perhaps we should add something like a
getPropertyDefinition(Str