I assume your need to to bind it into the 'local' or in-JVM tree (otherwise it will need to serialize/deserialize). Check out NonSerializableObjectFactory in jboss naming.
Thankyou for your reply ...
Yes I have no wish to serialize this object, or export it over some connector/RMI etc to another JVM.
I looked for NonSerializableObjectFactory on the web, and only found one link for it :
I am a little confused on how I should use this object. Would you be able to give me a pointer towards how I should implement the use of this class - ie how I should configure the deployment - there seems to be a wealth of .xml config files involved in JBoss, and even if you are a fairly competent Java programmer, I find the config files hard going if you step outside the standard deployment examples (in the purchased JBoss manual).
To give you an idea of how I configured Tomcat(4 & 5), for this kind of thing to work, I implemented javax.naming.spi.ObjectFactory, and then added under the server.xml tag a which fired this implemented factory class. This was the kind of thing I was looking for in JBoss, and the NonSerializableObjectFactory you mentioned seems to be along those lines, but I am unsure of the config files involved (I had tried adding these tag settings in the embedded tomcat config, but it seemed to ignore them) ...
Thanks again for any pointers.
I just did a search for NonSerializableObjectFactory in the jboss distribution (JBoss 3 and also 2), and can find no reference to that class at all ...
Just in case anyone runs into this prblem, I managed to fix it by :
Its not NonSerializableObjectFactory you need to use but NonSerializableFactory :
JBoss seems to maintain two JNDI trees - one in which objects bound to it must be serializable - this is the "normal" context returned by a "new InitialContext()" type call (from within the container). The other tree is a non-serializable map, on which you may bind objects via the helper class NonSerializableFactory. The two trees a separate, so if you bind an object under the non-serializable tree, these cannot be accessed via the normal JNDI tree.
Thanks to mikefinn who nudged in the right direction !