>
>
> byte[] logIdentity = logfile.getTxRecord(). getJNDIName();
>>
>>
>> But we don't have a real JNDI name, of course we could provide some
>> opaque identifier for the logfile,
>> but I think we should avoid the term JNDI here.
>>
>
> ok. Our internal API actually uses the term EISName since the RM is not
> always a database, but given your feelings on the JCA spec I'm guessing
> you're not going to be a big fan of that choice either. Care to pick
> something else?
>
> The point I'm trying to capture in the name is that it should be usable as
> a key into whatever configuration mechanism the environment is using. An
> administrator reading it in the logs should be easily able to determine
> which RM instance is the source. JNDI name is useful for that in most Java
> EE app servers, which is the dominant use case.
>
What about "EISIdentifier" ?
Christian Romberg
Chief Engineer | Versant GmbH
(T) +49 40 60990-0
(F) +49 40 60990-113
(E) cromberg_at_versant.com
www.versant.com<
http://www.google.com/url?q=http%3A%2F%2Fwww.versant.com%2F&sa=D&sntz=1&usg=AFrqEzeeEBc_gN_8mxtt8xDB0tjXDXQVlw>|
www.db4o.com<
http://www.google.com/url?q=http%3A%2F%2Fwww.db4o.com%2F&sa=D&sntz=1&usg=AFrqEzdo3Q40RwKQPBtnPIuBYQd1diFxJQ>
--
Versant
GmbH is incorporated in Germany. Company registration number: HRB
54723, Amtsgericht Hamburg. Registered Office: Halenreie 42, 22359
Hamburg, Germany. Geschäftsführer: Bernhard Wöbker, Volker John
CONFIDENTIALITY
NOTICE: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential or
proprietary information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
immediately contact the sender by reply e-mail and destroy all copies of
the original message.