It may be easier to override the NameLookup service.
Look here for details: http://jakarta.apache.org/hivemind/override.html
Achim
Am Wed, 13 Jul 2005 17:49:02 -0300 schrieb Pablo Lalloni
<[EMAIL PROTECTED]>:
El Mié 13 Jul 2005 15:16, Carlos Lizarralde escribió:
I have the same problem!
Any clues?
Currently JNDI lookups are done through hivemind.lib.NameLookup service
which
doesn't support properties out of java.naming.factory.initial,
java.naming.factory.url.pkgs and java.naming.factory.provider.url
contributed
to be contributed.
I think your best shot is to implement your own NameLookup service that
accepts custom properties as contribution and then setup an
EJBProxyFactory
(copy&paste from hivemind-lib's hivemodule.xml) service with your
NameLookup
injected in place of hivemind.lib.NameLookup.
Then you can use this new EJBProxyFactory of your own for accessing your
EJBs.
Maybe this improvements to NameLookupImpl can be incorporated into
hivemind-lib's one.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
