jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Douglass" <douglass.d...@gmail.com>
Subject Re: model 2 jackrabbit deployment on JBoss, missing user.properties?
Date Fri, 15 Sep 2006 17:03:57 GMT
Well, 5 minutes of research and "going with my gut" proved successful.

For posterity: the users.properties (and roles.properties) either go in the
webapp or, I put them in the JBoss server conf directory. The
users.properties file requires an entry (username=password) with values that
match those that are used to configure the credentials of the JcrTemplate.

Sincere apologies for posting before I did more research,

On 9/15/06, Doug Douglass <douglass.doug@gmail.com> wrote:
> I've just gotten our jackrabbit deployed into JBoss as a model 2
> deployment and I'm getting "javax.jcr.LoginException: Missing
> users.properties file.". Searching around I see references to this error
> message, but no resolution.
> Some more specifics:
>   We're using JBoss Spring Deployer to deploy a JCR-backed DAO layer into
> JBoss for access from several web applications. The deployer loads our
> Spring context, which configures a JcrTemplate (from Spring modules) to
> access Jackrabbit and registers the context into JNDI. This all works fine,
> the JBoss logs show the jackrabbit repository starting without problem.
>   From within our webapps, we get the loaded Spring context via a JNDI
> lookup and, from the Spring context, our DAO layer.
>   But, trying to use the DAO layer to query jackrabbit produces the
> exception noted above.
> I think this is more related to JBoss and JAAS than JCR/Jackrabbit, but
> I'm confused as to why the credentials in our Spring context are not being
> used.
> TIA,
> Doug

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message