I vote for an improvement of the security documentation (Access and Login-Managers) too.
It would also be nice to include a little documentation on how to import the jackrabbit project in various IDEs, like eclipse or studio creator. This might get more people started to play around with the source code. Furthermore it would help to somehow unify to documentation. Currently the information is split up in the "first hops", the Wiki(which isnt easy to find), the FAQ and various documentation pages. I find this rather confusing. In the download section it would be nice to have a binary download too. Greetings David Am Montag, den 13.03.2006, 12:22 -0800 schrieb Soland, Michael: > +1 to the .war > > The reason I joined this list was the lack of documentation in the > configuration page on the incubation site. I believe this is the perfect > time to knock out some of those "TODO" markers on the site, especially the > sections dealing with AccessManagers and LoginModules. Concise documentation > really makes a difference when potential users evaluate Jackrabbit. > > Other than that, I'm really looking forward to the 1.0 release! > > Thanks, > -Michael > > > -----Original Message----- > > From: Martin Perez [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 13, 2006 12:00 PM > > To: jackrabbit-dev@incubator.apache.org > > Subject: Re: Improving the first impressions > > > > I agree with Roy suggestions. > > > > Michael, jLibrary (http://jlibrary.sourceforge.net) is using jackrabbit > > and > > is bundled on a .war dropable on several application server (tested on > > tomcat,jboss,geronimo,..). It's really easy to create your .war, simply > > look > > at the server contrib projects. I combined that with a customized startup > > servlet, and voilá. > > > > Personally I think that Jukka is addressing very good the process of > > making > > easier development startup with jLibrary. The last jira issues solved > > about > > that drastically decrease developer adoption time, and that is very good. > > Anyways, for a future release I think that currently Jackrabbit weakest > > point is security. Having custom login modules (ldap, database) will be a > > very interesting contribution and also will easy Jackrabbit adoption > > because > > many enterprises are not supporting JAAS but they really have databases or > > active directories. > > > > Martin > > > > On 3/13/06, Brian Moseley <[EMAIL PROTECTED]> wrote: > > > > > > On 3/13/06, Roy Russo <[EMAIL PROTECTED]> wrote: > > > > > > > STAY METAL! > > > > > > \m/ > > >
