An EJB container will generally not give you better performance than a non EJB container (other than it might be a more efficient...but that will not be because it is an EJB container). The main difference is that you will be able to use EJB's and the other Java EE goodies that a J2EE container provides, like persistence and distributed transaction management. Unless you are going to go with Glassfish (there may be one or two other obscure ones) you will not be using EJB 3.0 and it is generally not recommended to use < EJB 3.0--see Rod Johnson's J2EE without EJB as well as tons of other books. You are better off going with tomcat and combination of Spring and Hibernate or something. There is an RMI searcher in Lucene and you should be able to easily use it with a servlet container. Apaches XML-RPC 3.0 java extension also has a remote object proxy system and will allow you to pass serial objects back from remote methods although it does not seem to support dynamic remote loading of implementations. Jini might also be worth looking into, although it seems that it is not possible to use Jini in tomcat securley without modifing both Jini and Tomcat. Glassfish is supposedly better suited to this.
In the end, a million documents is nothing to lucene if you have even remotley decent hardware (probably even if you don't). Lucene will spit around a million documents in her sleep. I'd develop in Tomcat (or similiar) and check out solutions like Spring and Hibernate as you need J2EE (or JEE) solutions. - Mark On 10/13/06, Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
Gecko? ;) My advice: stay away from EJBs as much as you can. They are too complicated and too heavy for most systems. Servlet containers like Jetty, Tomcat, or Resin are often perfectly suitable for the job and a lot simpler. Otis ----- Original Message ---- From: "Chenini, Mohamed " <[EMAIL PROTECTED]> To: java-user@lucene.apache.org Sent: Thursday, October 12, 2006 10:25:44 AM Subject: a design question Hello, This is a design question: For Lucene to be able to process a million documents and in the purpose for the search application to be scalable and still have a good response time do we need to use an EJB container such as Weblogic or is a Servlet container such as Tomcat sufficient to do the job? This design should take into consideration remote searching. Thanks, Mohamed ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
