Reusing code is always a good thing to do. On the XSLTC side, some of the
utility classes such as IntegerArray, Hashtable can also go into the common
package.
Morris Kwan
XSLT Development
IBM Toronto Lab
Tel: (905)413-3729
Email: [EMAIL PROTECTED]
Bhakti Mehta
<[EMAIL PROTECTED]
.COM> To
[EMAIL PROTECTED]
11/26/2003 04:38 cc
PM Santiago Pericas-Geertsen
<[EMAIL PROTECTED]>
Subject
Please respond to Proposal for moving reused code to
xalan-dev independent packages
Hi,
I wanted to put forth the following proposal.
There are cases when we may reuse the code from xalan in xsltc. For e.g
for one of the bugfixes in xsltc related to getAssociatedStylesheets I
had reused org.xml.xalan.processor.StylesheetPIHandler and
StopParseException classes which were doing a great job in xalan.
However such classes do not get included in the xsltc.jar if the
xsltc.jar target is invoked on the Apache codebase. I am sure there may
be other cases where we may be reusing code.
We can identify and move such code under a common package
such as org.apache.xml.utils or somewhere else where it could
get picked by both xalan or xsltc jars.
Advantages
==========
1)This would help identifying and decoupling common parts so that they
could be reused more efficiently.
2)It would help create complete jars which could be used independently.
3)It would help easier maintainence in the future.
Please can you let me know your views on this. It would be nice to initiate
and incorporate these changes in our future releases.
Thanks,
Bhakti
