We store serializable object by default. Yes it is a feature we might add. Also I believe that Rickard coded a VM only namespace under java: (? rickard) marc |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Adam Rabung |Sent: Tuesday, November 21, 2000 4:47 PM |To: jboss |Subject: [jBoss-User] Sharing a single object instance with JNDI | | |Hi all, |Two questions: |1. Is TomcatService still worthwhile, or is it totally replaced by |EmbeddedTomcatService at this point? | |2. I've downloaded FINAL, but I still have problems binding an object in |JNDI and retrieving that _same |instance_ from a JSP. I'm successfully running the TomcatService, so |everything is in-VM. At startup, I |bind a (non-serializable) object to the JNDI tree. After startup, I have a |JSP which attempts to read |this object from the JNDI tree. The call fails because the object is not |serializable. I definitely |understand why this is happening - from my what I've seen, JNDI |implementations need only support RMI-based |objects, JNDI reference objects, and serializable objects. So, what I'm |asking for is probably beyond J2EE/JNDI |spec. I've used this ability to store singleton-type objects on the JNDI |tree on other app-servers |and I find it pretty useful. Oddly enough, this seems to be the default |behavior of Weblogic JNDI. Is this a |feature jBoss may have in the future? Or does it already have it and I'm |screwing something up? | |Any input would be appreciated. | |Thanks, |Adam | | | |-- |-------------------------------------------------------------- |To subscribe: [EMAIL PROTECTED] |To unsubscribe: [EMAIL PROTECTED] |Problems?: [EMAIL PROTECTED] | | -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
