You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to osjava
I'm using the shared memory implementation of Simple JNDI 0.11.2 and
it's bizarre that a close call is causing an exception to be raised in
my application:
2008-03-10 09:17:13,953 DEBUG [MessageBean] Failed in lookup
javax.naming.NotContextException
at
org.osjava.sj.jndi.AbstractContext.destroySubcontext(AbstractContext.
java:529)
at
org.osjava.sj.jndi.AbstractContext.close(AbstractContext.java:697)
at javax.naming.InitialContext.close(InitialContext.java:490)
It appears that close() is actually destroying a subcontext here. So,
why does close() attempt to destroy anything, especially for a shared
memory context...
Henri Yandell
unread,
Mar 22, 2008, 1:32:01 PM3/22/08
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to osj...@googlegroups.com
The NotContextException was because in shared mode, data and subcontexts were using the same piece of data. I just committed a fix for that.
Whether anything should be in close() is an open question.