I am building my application with the rar file (for easy replaceability with JCR updates and encapsulation of all the necessary jars) and a web application that supplies specific APIs (REST and SOAP) plus some nasty jsp pages for drilling down through the repository to make sure things are where they are supposed to be, to exercise the API for testing etc.
My application is much like an archive, stuff goes in and then gets viewed, the only updates are more additions. My API has only a few possible calls. I have thrown in 100K documents as a starter and it goes great. Ross Dhrubo <[email protected]> wrote on 30/03/2010 02:10:24 PM: > From: Dhrubo <[email protected]> > To: [email protected] > Date: 30/03/2010 02:11 PM > Subject: Re: Jackrabbit and web application > > How about embedding the repository in an web app and exposing remoting API - > Rest , SOAP etc for applications who are interested? > I am sure this has been tried. Comments will be highly appreciated. > > > On Mon, Mar 29, 2010 at 10:37 PM, ChadDavis <[email protected]>wrote: > > > On Mon, Mar 29, 2010 at 10:54 AM, Dhrubo <[email protected]> wrote: > > > Chad - > > > some examples / source will be appreciated > > > > The jackrabbit site has examples for all of this. The remoting wiki > > page is the best source for the remoting strategies, and the "same > > JVM" method is well documented also, again there are several options. > > They all make use of a servlet that is found in the jackrabbit-webapp > > module; this servlet inits the repository and makes it available in > > the servlet container. > > > > > > > > > > > > I guess embeded one is fastest but is there any data to prove it? > > > > There's no network layer . . . I'm not sure you need data to prove > > that it would be faster. But if you need specifics, you'll probably > > have to produce them yourself. I'd be interested to see the numbers > > you come up with. I'm going to release my own numbers when we get > > tests that would be meaningful to the community. > > > > > > > > ~ dhrubo > > > > > > On Mon, Mar 29, 2010 at 10:15 PM, ChadDavis <[email protected] > > >wrote: > > > > > >> On Sun, Mar 28, 2010 at 8:44 AM, Ilya Skorik <[email protected]> wrote: > > >> > > > >> > Hello. > > >> > > > >> > I plan to use jackrabbit in a Web application. Prompt, what strategy > > is > > >> > necessary for selecting for the connection organisation to base? > > >> > > > >> > > >> There are many options. Actually, it seems that a lot of people are > > >> running the repository inside the webapp. My team insists on a server > > >> style deployment of the repository, and I found that the spi/davex > > >> remoting is the most robust at this time; perhaps it's even considered > > >> the preferred remoting method. > > >> > > >> See: > > >> > > >> http://wiki.apache.org/jackrabbit/RemoteAccess > > >> > > >> Note, there's an RMI method on that same page but it's considered to > > >> lack production performance, and, in Jackrabbit 2.0, it's not even > > >> fully implemented. > > >> > > >> > > >> > > >> > Considering specificity of Web applications when the server handles > > set > > >> of > > >> > queries from different users. > > >> > > > >> > Whether there is something like connection pooling for jackrabbit? > > >> > -- > > >> > View this message in context: > > >> > > http://n4.nabble.com/Jackrabbit-and-web-application-tp1694146p1694146.html > > >> > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > > >> > > > >> > > > > > > > > > > > > -- > > > Thanks ... Dhrubo > > > My Book - http://www.apress.com/book/view/1430210095 > > > > > > My Blog - > > > http://www.jtraining.com/blogs/blogger/dhrubo/ > > > > > > LinkedIn - http://www.linkedin.com/in/dhrubo > > > > > > > > > -- > Thanks ... Dhrubo > My Book - http://www.apress.com/book/view/1430210095 > > My Blog - > http://www.jtraining.com/blogs/blogger/dhrubo/ > > LinkedIn - http://www.linkedin.com/in/dhrubo
-- This message contains privileged and confidential information only for use by the intended recipient. If you are not the intended recipient of this message, you must not disseminate, copy or use it in any manner. If you have received this message in error, please advise the sender by reply e-mail. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.
