|
I would also agree with Dieter's comments. If you want a scalable application that is accessible remotely, then why re-invent the wheel? J2EE does pretty much what you would need to implement by hand if you needed that capability. > Ivan, I don't know how far you've gone with your design, but for the > last several years the industry has been moving away from EJB. There are many big name companies across that rely on J2EE for their applications. Some examples are Toshiba, Xcel Energy, Husqvarna, Geac, Nintendo, and Panasonic to name a few. > Even Don Denoncourt, one of the early adopters of the EJB architecture, > will tell you that the EJB architecture simply adds too much overhead > for all but the simplest applications. I haven't read the statement you referring to, but I'm guessing that the "overhead" Don is talking about could be actual system performance, or development overhead. J2EE is an architecture that has traditionally advanced faster than the development tools for it. Our company has been fairly wary about jumping to EJBs until recently. But the environment for J2EE and EJB is changing rapidly. The balance is beginning to shift back to lighter weight components and simpler implementations. With the advent of EJB 2.0 support of local interfaces, EJBs can now be defined to have "local" interfaces which short circuit all of the remote logic that some implementation don't really need. This results in increased server performance, but still supports the scalability of EJB. Also, a traditional best practice with EJB has been to eschew use of Entity beans altogether in favor of Session beans. The Session beans act as reusable modules that hit against the database using traditional JDBC connections (through a connection pool, of course). With this model, your session beans could even interact with objects that use JDO as your persistence layer, and then simply pass them back to the client of your EJB. If development tooling is an issue, then there are some very popular tools available for increasing development speed. XDoclet has been very popular for easing the creation of EJBs by automating the creation of the necessary EJB interface classes so that you can write one class, and the tooling takes care of most of the rest. In fact, Sun is providing a similar functionality to XDoclet into the core of the Java 1.5 language. IDEs with integrated test J2EE containers are very good at shortening the Develop-Test cycle by giving each developer thier own small server to work with. Ant is the defacto standard for doing builds of large projects, and can really speed up the compile and deploy tasks of an application. > You really should consider another form of ORM. JDO is a relatively > lightweight model, and there are also a number of Open Source > persistence packages. Hibernate is one of the more popular options > today. Again, with EJBs, you could wrap whatever persistence layer you choose with Session beans. It seems to me that more often than not, application development is like trying to hit a moving target. J2EE is a framework that supports agile development practices by allowing you to create single JVM applications, all the way up to multi-server, cluster hosted applications that serve millions of people through many different interfaces. I'm not saying J2EE is the answer to everything, but it is good tool for some applications. It all ultimately depends on your requirements. J2EE is just another screwdriver in the toolbox. ---------------------------------------------------------------------- Chris DeLashmutt Senior R&D Analyst LeasePlan USA 1165 Sanctuary Pkwy., Alpharetta, GA 30004 Phone: 678-202-8695 Fax: 678-921-4895 ---------------------------------------------------------------------- Dieter Bender <dieter.bender@bend To: Java Programming on and around the iSeries / AS400 <java400-l@xxxxxxxxxxxx> er-dv.de> cc: Sent by: Subject: Re: Does jBoss work on iSeries? java400-l-bounces@m idrange.com 03/08/2004 10:39 AM Please respond to Java Programming on and around the iSeries / AS400 Joe, i would not agree with this statement. There are some drawbacks with EJBs, if you have other applications sitting on the same database, wich can't use your ejb layer, you might come in some trouble and for small applications the programmer overhead might be a contra argument. But you will get more scalability with ejbs than without and you will get some benefits for your design. Dieter Bender On Montag, 8. März 2004 16:34, Joe Pluta wrote: > > From: Ivan Hurtado > > > > I am interested in using jBoss 3.2.3 server on an > > iSeries, however, I recently read in Don Denoncourt's > > "Java at Work" book that the opensource J2EE/EJB > > servers (jBoss and jONas) don't work on iSeries JVM's. > > Is this still true? > > Ivan, I don't know how far you've gone with your design, but for the > last several years the industry has been moving away from EJB. Even Don > Denoncourt, one of the early adopters of the EJB architecture, will tell > you that the EJB architecture simply adds too much overhead for all but > the simplest applications. You really should consider another form of > ORM. JDO is a relatively lightweight model, and there are also a number > of Open Source persistence packages. Hibernate is one of the more > popular options today. > > Joe > -- mfG Dieter Bender DV-Beratung Dieter Bender Wetzlarerstr. 25 35435 Wettenberg Tel. +49 641 9805855 Fax +49 641 9805856 www.bender-dv.de eMail dieter.bender@xxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.