You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Roger Ruttimann <ro...@earthlink.net> on 2004/02/29 03:04:08 UTC
[J2] build failures & TestCapability
When we are loading the client classes all associated collections mimtypes
(from table: CLIENT_TO_MIMETYPE) and capabilities are populated. The
populated values are half-way ok. It fails for ID's with the value of 0
(Zero).
With other words, when the clients are loaded
JetspeedCapabilities.getClients() brings in the client class and the
associated classes for mimetypes and capabilities.
The mimtypes values are correct and the ID's are correct except for the ID =
0!
The capabilities are correct and the ID's are correct except for ID = 0!
It seems that OJB/Persistence plugin fails on the ID value of 0. It assigns
the next available value. It worked before so I don't think it's a problem
in HSQL.
Solutions:
--> All the entries in the capability tables should have ID's != 0. We would
have tio check other tables as well.
--> Checking why ID's of 0 are treated differently in the Persistence
plugin.
I run out of time right now but I'll continue on this tomorrow.
Any comments
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [J2] build failures & TestCapability
Posted by Serge Huber <sh...@jahia.com>.
At 03:04 AM 2/29/2004, Roger Ruttimann wrote:
>--> Checking why ID's of 0 are treated differently in the Persistence
>plugin.
I'm not entirely sure about this but I think that OJB uses the ID=0 to
indicate that an object exists in memory only and hasn't yet been stored.
Regards,
Serge Huber.
- -- --- -----=[ shuber2 at jahia dot com ]=---- --- -- -
www.jahia.org : A collaborative source CMS and Portal Server
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [J2] build failures & TestCapability
Posted by David Sean Taylor <da...@bluesunrise.com>.
Hey Roger,
On Saturday, February 28, 2004, at 06:04 PM, Roger Ruttimann wrote:
> When we are loading the client classes all associated collections
> mimtypes
> (from table: CLIENT_TO_MIMETYPE) and capabilities are populated. The
> populated values are half-way ok. It fails for ID's with the value of 0
> (Zero).
>
That seemed to be the problem.
Guess the new OJB or Persistence service has some issues with ID == 0...
Great catch, thanks!
Will check it in a few minutes
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: [J2] build failures & TestCapability
Posted by David Sean Taylor <da...@bluesunrise.com>.
That was it , see my response on dev list
On Saturday, February 28, 2004, at 06:04 PM, Roger Ruttimann wrote:
> When we are loading the client classes all associated collections
> mimtypes
> (from table: CLIENT_TO_MIMETYPE) and capabilities are populated. The
> populated values are half-way ok. It fails for ID's with the value of 0
> (Zero).
>
> With other words, when the clients are loaded
> JetspeedCapabilities.getClients() brings in the client class and the
> associated classes for mimetypes and capabilities.
>
> The mimtypes values are correct and the ID's are correct except for
> the ID =
> 0!
> The capabilities are correct and the ID's are correct except for ID =
> 0!
>
> It seems that OJB/Persistence plugin fails on the ID value of 0. It
> assigns
> the next available value. It worked before so I don't think it's a
> problem
> in HSQL.
>
> Solutions:
> --> All the entries in the capability tables should have ID's != 0. We
> would
> have tio check other tables as well.
> --> Checking why ID's of 0 are treated differently in the Persistence
> plugin.
>
> I run out of time right now but I'll continue on this tomorrow.
>
> Any comments
>
> Roger
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org