Women in Technology

Hear us Roar



Article:
  Bringing the J2EE Cathedral to the Bazaar
Subject:   I don't know about this Aspire stuff.
Date:   2002-12-04 22:34:06
From:   anonymous2
Seems like it's useful mainly for simple Create-Retrieve-Update-Delete applications... the kind that MS Access will generate for you with a wizard. The whole idea of declaratively defining a middle tier in this way basically negates all the advantages of J2EE: distributed, componentized, heterogenous clients, (distributed) transactions, etc. I get the impression that Aspire isn't suitable for creating ColdFusion-class apps, much less your average J2EE app.


J2EE was designed to solve hard problems. If you're only going to attack the easy problems--i.e., the kind of problems where you can get away with having all the data in the database--then I'd say you're probably better off going with PHP or ColdFusion or whatever, than applying this type of facade over J2EE.


My $.02...

Full Threads Newest First

Showing messages 1 through 1 of 1.

  • On the contrary. Large complex systems can never be built with complexity
    2003-01-08 08:10:10  satyak [View]

    Thank you for taking the time to comment. As an author I sincerely appreciate it. I will try to answer the seeming simplicity of the proposition.

    Internet took off because of its inherent simplicity. Without simplified abstractions and loose coupling you can never build systems that are large.

    The goal of Aspire is to bring the simplicity and declarativity of PHP and ColdFusion with J2EE as its backbone and there by correcting some of eager steps that these RAD products took.

    Aspire is designed for large complex systems. Separated data access, declarative transactions, Hierarchical XML data sets, Automatic publishing of data as SOAP output goes a long way for corporations today.

    The referenced article titled "Transparent data pipelines for JSP" goes into the architectural foundations.

    All of the hard problems are expressed as built in parts coded in Java. So the users have always the opportunity code up the complexity as an underlying J2EE component. Once coded a programmer need only use declarative constructs.

    Due to the length of the article I might have missed some finer points. More recently there are additional articles at O'Reilly on using Aspire as a pure data engine for Tomcat applications.

    Hope that throws some additional light on the matter.