Dain Sundstrom wrote:
On Oct 24, 2006, at 10:45 PM, Christopher M. Cardona wrote:
2. JSR77.3.5.0.1 the deploymentDescriptor attribute must provide a
full deployment descriptor based on any partial deployment descriptor
plus deployment annotations.
That doesn't sound like it will be easy. Do they mean that you must
build a full deployment descriptor backwards out of the annotations?
I’m not exactly sure how to interpret it either. Looks like the
objective is to make sure the value for 'deploymentDescriptor' attribute
of J2EEDeployedObject is always set to the combined or full DD (partial
DD plus deployment annotations). Our current implementation passes the
DD values to the constructors of the concrete classes that implement
J2EEDeployedObject. So my guess is checking and manipulation of DD
should be done inside the classes that call those constructors. Thoughts?
My first question is do we even have to update our current JSR 77
implementation to become JEE 5 compliant.
JSR 77 is a weird spec in that is had very few Java APIs specified.
The bulk of the spec described the names of fields and operations to
be exposed via JMX. You should check if the Java APIs were updated for
Java5 generics.
Looking at the latest specs there are no API changes. I’ll update this
thread if I find anything…
Thanks,
chris
-dain
