Oleg,
I am not sure if one of the patches submitted fixed my
issue, but this is now working with the latest head.
Thanks for your help.
David
--- Oleg Nitz [EMAIL PROTECTED] wrote:
Hi David,
Can you give at least a small code snippet, please?
Regards,
Oleg
On Monday 01 March 2004 15:12, David Le Strat wrote:
Hello,
I am having the weirdest issue, any suggestion;
Basically, I want to add a collection of
properties to
a node.
In my test, I have only 1 property:
Properties: [[nodeId, 5], [propertyKeyId, 21],
[propertyKey,
[EMAIL PROTECTED],
[propertyValue, true], [creationDate, 2004-03-01
10:03:14.812], [modifiedDate, 2004-03-01
10:03:14.812]]
I open the transaction and do setNodeProperties on
the
node object.
The transaction is open, just before committing, I
check to see that the properties are set correctly
on
the object:
DEBUG:
org.apache.jetspeed.prefs.impl.PreferencesImpl
-
Node for update: [[parentNodeId, 4], [nodeName,
propertyset1], [fullPath,
/user/principal1/propertyset1], [nodeType, 0],
[nodeKeys,
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
631573,
[EMAIL PROTECTED],
[nodeProperties, [[[nodeId, 5], [propertyKeyId,
21],
[propertyKey,
[EMAIL PROTECTED],
[propertyValue, true], [creationDate, 2004-03-01
10:03:14.812], [modifiedDate, 2004-03-01
10:03:14.812]]]
], [creationDate, 2004-03-01 09:34:13.138],
[modifiedDate, 2004-03-01 10:03:14.812]]
As you can see [nodeProperties,...] is set, I also
change the [modifiedDate, ...].
When I close the transaction, I get
[nodeProperties,
[]]: the nodeProperties collection is gone...
But [modifiedDate, 2004-03-01 10:03:14.802] is
still
there.
I can't think of anything that would cause this
behavior. Any help is appreciated.
DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate : [[parentNodeId, 4], [nodeName,
propertyset1], [fullPath,
/user/principal1/propertyset1], [nodeType, 0],
[nodeKeys,
[EMAIL PROTECTED],
[EMAIL PROTECTED]
937cd,
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[nodeProperties, []], [creationDate, 2004-03-01
09:34:13.138], [modifiedDate, 2004-03-01
10:03:14.802]]
DEBUG:
org.apache.ojb.broker.accesslayer.JdbcAccessImpl -
executeUpdate : [[parentNodeId, 4], [nodeName,
propertyset1], [fullPath,
/user/principal1/propertyset1], [nodeType, 0],
[nodeKeys,
[EMAIL PROTECTED],
[EMAIL PROTECTED]
937cd,
[EMAIL PROTECTED],
[EMAIL PROTECTED],
[nodeProperties, []], [creationDate, 2004-03-01
09:34:13.138], [modifiedDate, 2004-03-01
10:03:14.802]]
Regards,
David.
--- Oleg Nitz [EMAIL PROTECTED] wrote:
On Sunday 29 February 2004 19:24, David Le Strat
wrote:
When I update the NodeImpl with new
nodeProperties
(a
collection), only the NodeImpl object gets
updated
and
the nodeProperies are not created.
I have done this in the past with PB with out
any
issues. Any suggestions?
With auto-update=true nodeProperties should be
creates, whatever you use,
PB or OTM. I've just done correspondent test
with
OTM, and all is okay.
So please send me code snippet or just try to do
the
same with PB.
OTM does nothing special when
auto-update=true, it
just calls
broker.store(). If you set auto-update=false
and
otm-dependent=true, then
OTM itself will take care about creation and
deletion of nodeProperties.
Regards,
Oleg
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster
http://search.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
