| |
 |
Thursday, March 18, 2004 |
Dragged back to the Petstore
I had the good fortune to revisit
Ye'Olde Petstore again recently, needing to rebuild it from scratch so
it'd deploy to OC4J 904. Besides the actual complexity of the sample
application (which is by no means something you'd want to point folks
who are new to J2EE at) what struck me as missing was a simple
description of the resources required to wire the thing together,
allowing it to be more easily configured for deployment to other J2EE
containers.
There's a fairly comprehensive
documentation set (and a book too I think) which describes how to get
it to work against the Sun J2EE Reference Implementation, and a design
and implementation document which describes design decisions and how it
was implemented. There's also the Sun reference descriptors which map
the various logical names used in the app to the physical resources.
But there's nothing that either lists out or depicts in a diagram what
queues and topics are needed for each component, either as a listener
or as a sender to enable it to work. With the asynchronous nature
of this design, the wiring is quite important. If you configure a
component to post to the wrong Queue, or have an MDB listen on the
wrong Queue, then it won't qork.
While I understand the necessity of
providing this app prebuilt to work on the Sun J2EE RI, it would also
seem to be in the best interest of J2EE, which promotes itself as a
platform and vendor portable infrastructure, to provide some level of
documentation that would enable it to be rebuilt for deployment to
another J2EE implementation in as simple a manner as possible.
2:24:05 PM 
|
|
© Copyright 2004 buttso.
|
|
|
|
|
