jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Mazzitelli" <john.mazzite...@jboss.com>
Subject RE: JCR, RMI & WebDAV - draft HOWTO - revison 0.2
Date Mon, 12 Dec 2005 19:10:06 GMT
Oh, one other thing - when deploying in JBoss, you'll get some error
stack traces and the log4j messages come out on STDOUT.

By default, log4j will already be in the classloader of the webapp  - I
commented out the deployment of the Logging servlet in the jackrabbit
war's web.xml and I deleted all the log4j.* config files and jar from
the jackrabbit war.  The log4j messages came out "nicer" when I did this
and no errors about failing to create appenders and such.

I'll just modify the log4j config in the JBoss config directory if I
want to tweek how the log4j messages come out for Jackrabbit stuff.

--
John Mazz  

> -----Original Message-----
> From: John Mazzitelli [mailto:john.mazzitelli@jboss.com] 
> Sent: Monday, December 12, 2005 1:21 PM
> To: jackrabbit-dev@incubator.apache.org
> Subject: RE: JCR, RMI & WebDAV - draft HOWTO - revison 0.2
> 
> To deploy the WebDAV .war in JBoss (as opposed to standalone Tomcat),
> copy the war to the deploy/ directory.  To get it running 
> quickly, just
> go to conf/login-config.xml and setup the default webapp JAAS 
> policy to
> authenticate using the same user/role properties as that of the
> jmx-console (this "other" policy is at the bottom - this is 
> the default
> JAAS policy that war's deployed in the internal Tomcat use, unless
> overridden in the war itself):
> 
>     <application-policy name = "other">
>        <authentication>
>           <login-module code =
> "org.jboss.security.auth.spi.UsersRolesLoginModule"
>              flag = "required">
>             <module-option
> name="usersProperties">props/jmx-console-users.properties</mod
> ule-option
> >
>             <module-option
> name="rolesProperties">props/jmx-console-roles.properties</mod
> ule-option
> >
>           </login-module>
>        </authentication>
>     </application-policy>
> 
> Go to 
> http://localhost:8080/jackrabbit-server/repository/default and log
> in with admin/admin (if you didn't modify the default jmx-console
> credentials).
> 
> You'll notice that a "jackrabbit" directory will be created under the
> JBoss's bin directory.  I'd like to get this to go in the 
> data directory
> - anyone know off hand how I can get the default parent 
> directory of the
> repo file system to be server/default/data as opposed to bin/ ?
> 
> --
> John Mazz  
> 
> > -----Original Message-----
> > From: Peter Darton [mailto:peterd@intrinsica.co.uk] 
> > Sent: Monday, December 12, 2005 12:42 PM
> > To: jackrabbit-dev@incubator.apache.org
> > Subject: RE: JCR, RMI & WebDAV - draft HOWTO - revison 0.2
> > 
> > > Step 5 - in the maven command mentioned "copy_deps" - the 
> > > underscore should be a dash ... "copy-deps".
> > 
> > Oops.
> > Note to self: Must use Cut & Paste _even_ if it'd be quicker to type
> > it...
> > 
> > 
> > > I'm thinking the "cd jackrabbit/contrib/jcr-server" should be 
> > > "cd jackrabbit/contrib/jcr-server/server".  But I'm not sure 
> > > since that would imply the other subprojects like webdav, 
> > > webapp and client won't be built.
> > 
> > Ok, I think we'll have to go back to the 4-stage build that I 
> > originally
> > described in "version 0.1" of my "howto".
> > I'd been informed (after my whinge-list included a rant 
> about default
> > build targets) that the default target of 
> > jackrabbit/contrib/jcr-server
> > was sufficient in itself to build everything, so I tried 
> > that, and I had
> > some success.
> > That said, it's possible I hadn't cleaned up properly after previous
> > successful builds and it only built successfully because of those.
> > In _theory_ doing a default build in jackrabbit/contrib/jcr-server
> > should result in the whole project being built 
> successfully, although
> > that won't build the documentation (and building the top-level
> > documentation doesn't build the sub-projects' documentation).
> > 
> > So I guess we need to replace stage 7 with:
> > 
> > 
> > 7) Build jackrabbit WebDAV:
> >  cd jackrabbit/contrib/jcr-server
> >  maven clean
> >  maven
> >  cd webdav
> >  maven dist
> >  cd ../server
> >  maven dist
> >  cd ../client
> >  maven dist
> >  cd ../webapp
> >  maven dist
> >  cd ../../../..
> >  - Note: Although not necessary to run WebDAV, I found it useful to
> > build "dist" as well because the JavaDocs are the only documentation
> > you'll get (and they're not built by default).
> > 
> > 
> > Regards,
> > 
> >   Peter
> > 
> > 
> _____________________________________________________________________
> > This e-mail has been scanned for viruses by MCI's Internet 
> > Managed Scanning Services - powered by MessageLabs. For 
> > further information visit http://www.mci.com
> > 
> 

Mime
View raw message