Hello Oliver, James,

I can test it for you... I'll be back with a 'report' in a few minutes.

BRB, Miguel

-----Original Message-----
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] 
Sent: quarta-feira, 22 de Setembro de 2004 15:16
To: Slide Users Mailing List
Subject: Re: ldap configuration

Hi James,

there really was a pretty obvious bug in AbstractXMLResourceDescriptor. 
It should have shown up everytime the TxXMLFileDescriptorStore tried to 
create a new descriptor without the real object stored into it and later 
trying to re-read it. Nothing has changed for ages in 
AbstractXMLResourceDescriptor so I am wondering why this error did not 
show up earlier.

Anyway, it should be fixed now both in the HEAD as well as the release 
branch. Can anyone check, please?

Thanks,
Oliver

James Mason wrote:

> Oliver,
> 
> I don't know if it's really a problem or not. With 2.1M1 I configured 
> JNDIPrincipalStore to use a TxXMLFileDescriptorStore for the 
> SecurityStore and LockStore implementations. When I upgraded to 2.1b1 I 
> started getting errors with this configuration. I think it was the same 
> error that Miguel reported.
> 
> For reproducing I suppose you could try using the memory stores for 
> everything but security and locks. If you can't reproduce it that way 
> than the problem is probably obscure enough not worry about.
> 
> -James
> 
> Oliver Zeigermann wrote:
> 
>> Hi James!
>>
>> Could you describe how I can reproduce the problem? I would take care 
>> of it then...
>>
>> Oliver
>>
>>> This problem cropped up in 2.1b1. I'm not sure what causes it 
>>> (something changed with the TxFile stores) and I was too lazy to 
>>> track it down :). 
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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]
> 
> 


---------------------------------------------------------------------
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]

Reply via email to