I've added a new Jira issue JCR-3188 including a patch for 2.3.5 that
might help
in some cases when a EJB tries to get a JCR Session from a JCA Jackrabbit.
The patch at least makes it possible to use repository.login() with no
credentials
inside an EJB if the user invoking the EJB already is authenticated.
/Pontus
On 2011-12-10 00:11, Pontus Amberg wrote:
Noticed https://issues.apache.org/jira/browse/JCR-3129 so the shutdown
problem seems to be fixed in a future release.
/Pontus
On 2011-12-09T14:24:22 CET, Gustavo Henrique Orair wrote:
I had similar issues using Glassfish 3.1.1.
But the Jcr Manager developer
(http://code.google.com/p/sptjcrmanager/) told me, Jcr Manager
(Webapp) worked out-of-box with JackRabbit JCA and JBoss6.
I would like to hear a discussion about this problem also.
BR, Orair
2011/12/9 Pontus Amberg<[email protected]>:
Hi
I've deployed Jackrabbit as a combination of JCA+Webapp as described
here
http://wiki.apache.org/jackrabbit/JackrabbitOnJBoss . I've also
updated the
repository.xml to use an existing domain already configured in jboss
login-config.xml as described here
http://wiki.apache.org/jackrabbit/JackrabbitOnJbossSecurity. I have
encountered 2 problems so far with this setup that I haven't found any
solution to
1. Accessing the repository remotely through the webapp and
Jcr2davRepositoryFactory don't work since I end up with a
LoginException
where the "CallbackHandler" doesn't support "NameCallback" . This
seems to
be a known problem ( https://issues.apache.org/jira/browse/JCR-1584 )
2. The repository shutdowns immediately when there's no active
sessions.
This also seems to be a known "problem"/feature.
Is there any solution/work around to these two problems? I know that
one way
to prevent the shutdown is to create an extra dummy session but I
really
dislike that solution.
/Pontus
