I noticed that if I ready the PropertyDefintion.getName() outside of
the scope of the session, it returns an expanded name, rather than the
qualified name indicated in the JCR 2.0 specs.

I then observed that, in scope of a session, this returns the qualifed
name as advertised.  Incidentally, after being invoked in-session, it
also returns the qualifed name out of session.

My question is: is it a bad idea to use the JCR API out of the scope
of a session?

Reply via email to