Featured Article: An Adventure with J2EE 1.4 Blueprints


News: Featured Article: An Adventure with J2EE 1.4 Blueprints

  1. Debu Panda has written about the latest addition to the Java Blueprints program, the Adventure Builder. He reviews the architecture, and the portability issues that he found when porting to OC4J.

    Read Debu in An Adventure with J2EE 1.4 Blueprints
  2. As the engineering manager for the Java BluePrints team, I am very glad to see the Java Adventure Builder Reference application getting more attention.

    Thanks very much for your comments.

    I wanted to let everyone know that the portability bugs that Debu mentioned in the blog have already been fixed in the latest release (version 1.0.1): http://java.sun.com/blueprints/code/index.html and that version 1.0.1 has been verified using the Java Application Verification Kit (AVK): http://java.sun.com/j2ee/verified/avk_enterprise.html.

    Stay tune for the upcoming J2EE 1.4 BluePrints book: http://www.aw-bc.com/catalog/academic/product/0,1144,0321205219,00.html


  3. yes, Sun released an updated version of the Adventure Builder application (release 1.0.1) just around the same time I wrote this article. I've verified that following issues has been resolved

    1) The portability issues reported by me to them has been fixed

    2) The sample is now bundled separately from the J2EE 1.4 demo bundles.

  4. I have been working on J2EE projects for a few years now, still I has so much difficulty understanding WAF (web application framework) used in the pet store example. I haven't gone through the Java Adventure Builder yet but would strongly suggest J2EE team to consider using Struts as the default framework.

    Secondly, the number of UML diagrams available for pet store example is not sufficient for understanding the architecrue of the system in the first go. And I am not alone. Look at the number of questions posted on the java forum looking for the UML diagrams.

    All said and one , I'm sure thousands have benefitted from the blueprints.

    Thank You.
    - Roger
  5. article hard to understand[ Go to top ]

    Some good points, but the article was hard to understand in some places, particularly as English obviously wasn't the author's main language. I would suggest the author gets someone to proof-read and grammatically correct his future offerings before publishing. Makes this site look unprofessional.
  6. Thanks very much! I'm just developing with J2EE for 3 months.The blueprints will help me design J2EE applications much better, making a good design on the J2EE platform is not easy for starters, I think the blueprints will help a lot.
  7. The adventure app uses a servlet filter to demarcates JTA transaction boundaries.

    According to the J2EE spec this is not allowed?!:
    Java 2 Platform Enterprise Edition Specification v1.4, chapter 4.2.1 says

    "Servlet filters and web application event listeners must not demarcate transactions using the javax.transaction.UserTransaction interface. Servlet filters may use transactional resources in a local transaction mode within their doFilter methods, but should not use any transactional ressource in the methods used to wrap the request or response object."

    Do I misunderst something or does the bluprint app violate the spec ?!
  8. We did have a JTA transaction in a filters in an early access version of the Adventure Builder. The final code shipment versions of the application 1.0 and the 1.0.1 the transactions are now being performed
    within the service method of a serlvet.

    For the latest Adventure Builder see: