Greetings, I defined a custom JNDI implementation by providing a Initial Context Factory and a custom Context. My Context implementation allows the lookup and binding using a internal hashmap for that purpose as a database.
This JNDI implementation is just for providing cache, it's not for a real directory service (but it could be in future). 1- How do I deploy the my custom service implementation? I would handle the prefixes like "slr:" instead the default J2EE "java:". I know I must set the java.naming.factory.initial to my factory, but what about all the other steps I must do for deploy (classpath?,client JNDI invocation?, ...) 2- Since my JNDI implementation is made by pure java objects (hashmap), will I benefit from cluster environment? I mean, will my JNDI context be replicated by the cluster instances when a server instance starts to get a warmed up cache from the other instances? If not possible, are there any alternatives to do this? I thought putting the hashmap from my JNDI implementation in a singleton from a stateless EJB. That would manage the cache information for one server instance. But how could I replicated the state from another instances when a instance starts? (It's acceptable the replication only in the start like distributed independent caches, but I would like to avoid start from empty). Regards, Pedro Salazar. -- /ps ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
