Bug 4803 - Should we lose <properties> and <listeners> elements?
Should we lose <properties> and <listeners> elements?
Product: jbatch
Classification: Unclassified
Component: source
PC Windows
: P5 enhancement
: ---
Assigned To: cvignola
Depends on:
  Show dependency treegraph
Reported: 2013-03-16 13:53 UTC by ScottKurz
Modified: 2013-03-16 21:43 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description ScottKurz 2013-03-16 13:53:57 UTC
Without inheritance, we could lose the <properties> and <listeners> elements grouping <property> and <listener> children... which makes the JSL unnecessarily verbose.

I think we can still tweak the TCK pretty easily here with a find-replace, but I think we should give Mahesh a chance to weigh in on the impact to Glassfish tests.     

Comment 1 mminella 2013-03-16 14:46:51 UTC
I disagree with this.  Just because we are not supporting inheritance in this version of the spec does not mean that we will whenever the next version is addressed.  The grouping element provides an element of readabilitiy as well as minimizes the impact of the changes required to support inheritance.
Comment 2 cvignola 2013-03-16 21:43:39 UTC
I disagree, too, for same reasons as Michael.