You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Brian Minchau <mi...@ca.ibm.com> on 2006/03/07 22:05:59 UTC
Fw: Xalan-J JIRA defect review - Tuesday February 7, 2006 from 2:00 to 3:30
pm EST - Minutes
====================================
====================================
==============
SUBJECT: Xalan-J JIRA defect
review
WHEN: Tuesday March 7, 2006
from 2:00 to 3:30 pm EST
INVITEES: Active Apache Xalan
contributors
PRESENT: Brian Minchau, Yash
Talwar, Henry Zongaro, Christine Li
CHAIR: Brian Minchau
WHERE: Teleconference
Phone for Toronto
Area: (***) ***-****
Phone for Others:
(***) ***-****
Conference ID for
all: *******
LAST MEETING WAS ON: Tuesday
February 7, 2006
Outline:
1. New issues since last meeting
2. Older issues
3. Round table discussion
====================================
1. New issues
2267 - Agreed to change behavior to
NEVER output newline after a PI
(this is a duplicate of 1497)
2268 - Henry agreed to look at this
one (dubious URI code).
2269 - agreed to make ToHTMLStream,
ToTextStream, ToXMLStream non-final,
but subject to performance
testing.
2270 - which distribution to pick. -
Brian to add a comment to the issue,
no document changes yet.
2271 - Issue is already fixed. Brian
will change the issue's status.
2272 - Henry Z. had already asked
user to try 2.7 (user is using the
old 2.2),
waiting for user to reply.
2273 - In Henry Z's hands. Probably
not a bug here because the input is
being created with namespace
awareness being set to true.
Under the covers an identity
transform is used.
With the interpretive
processors identity transform being
used there is
one behavior with the
non-namespace aware input.
If XSLTC is used there is a
different behavior. But this is
probably
is not a valid problem
because
2274 - Henry opened this, and agreed
to change the priority to minor.
Nobody will be looking at
this one for now.
====================================
2. Older issues
2264 - (xi:include) - There are two
factories, SAXParserFactory and
DocumentBuilderFactory.
SAXParserFactory has a
setFeature() method and SAXParser
has a setProperty() method,
so things can be set on
either the factory or the parser
itself.
Each has different ways of
setting features.
Each is created in different
locations in Xalan, so one bit of
code might have access to
options from Process command
line, but other locations in the
code where a factory is
created.
The FLAVOR can be set on the
Process command line and this also
affects which factories
are in use, and this could
influence the validity of what is
being set on the factory.
====================================
3. Round table discussion
611 - (HTML href attributes doesn't
expand '&' correctly) - Assign to
Brian.
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org