Hi!
Am 15.04.2008 um 13:32 schrieb Marcel Reutegger:
why is that an issue? repository construction and destruction is not
specified in JSR 170 nor in JSR 283. applications will always have
to write implementation specific code to shutdown a repository.
JSR 283 will have a standardized mechanism to 'connect' to a
repository. whether that also include repository construction is
probably implementation dependent. repository shutdown is not
mentioned at all.
Things not mentioned in the spec != useless ideas.
Jackrabbit's goal should not only be spec-compliance, but also
usability for the developers/frameworks using it!
Let's compare this to the JDBC API (as an example).
but this is about getting a connection and closing it again, which
is equivalent to obtaining a JCR session and logging out when your
done. that's already standardized in JSR 170.
Embedded JDBC solutions use parameters in the connection URL for
starting databases (like "...START=true" at the end). One could do
that via session attributes in JCR/Jackrabbit, but the spec prevents
this by having the additional Repository interface, which has to be
fetched via JNDI for repository startup in JSR-283.
Just my 2 cents,
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
>> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<
