• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Is J2EE not robust??

 
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am working for a client, which uses its own well defined architecture, defining some set of strong base components,services..which help us to develop our applications faster.
This architecture...using a lot of J2EE standards, design patterns and aims at bringing a common practice and way of developing enterprise apps among all projects..
One of the introductory documents to the architecture, says "J2EE does not enforce robust application architecture, and it remains possible to to develop dirty and poorly structured applications using J2EE"..
i wanted to know ,is it true...
can i get some help....
 
Bartender
Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Absolutely. And its also true of every technology ever designed. What the introduction is probably alluding to is three things:
  • J2EE breaks much of the clean design OO tends to enforce
  • J2EE tend to include loosly coupled components, so integration testing is more important in a J2EE environment than it might be in a single application.
  • The J2EE spec. itself includes some standards which are counter productive and just plainly badly thought through (Entity Beans! I'm looking at you). A slavish devotion to the standards will produce applications which are just not as good as they could be.

  • Many of the problems of J2EE are general problems for "Enterprise" applications as a rule. I can't think of any technology which claims to fit this space and is a standard, and doesn't suffer from these problems (proprietory custom builds may well avoid this, but will introduce a whole different set of issues).

    Remember, there is nothing implicit in a technology which will avoid the dangers your introduction alludes to. Applications are only as good as the engineers who design and build them, regardless of technology.
    [ November 18, 2004: Message edited by: Paul Sturrock ]
     
    Been there. Done that. Went back for more. But this time, I took this tiny ad with me:
    Smokeless wood heat with a rocket mass heater
    https://woodheat.net
    reply
      Bookmark Topic Watch Topic
    • New Topic