You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bu...@apache.org on 2008/11/05 10:06:20 UTC
DO NOT REPLY [Bug 46149] New: XSLT task only writes to an
outputstream
https://issues.apache.org/bugzilla/show_bug.cgi?id=46149
Summary: XSLT task only writes to an outputstream
Product: Ant
Version: 1.7.1
Platform: Macintosh
OS/Version: Mac OS X 10.3
Status: NEW
Severity: normal
Priority: P2
Component: Optional Tasks
AssignedTo: notifications@ant.apache.org
ReportedBy: shaunramos@gmail.com
Currently the xslt task only allows writing to an outputstream. It should be
more flexible to allow writing to a character-based output (writers). This is
helpful especially when emulating a servlet program that calls the method
transform and passes in a printwriter instead of an outputstream. Right now,
using the same source xml and stylesheet, the xslt task generated html output
is different from that of the generated output from a servlet program - the
latter uses a printwriter.
The catch though is that the source xml contains some nordic(latin?) characters
(øæå). In the generated html, within the script tag, the characters, were
transformed into numeric characters entities when using the printwriter
(servlet program). Using xslt task, the characters were rendered correctly
because the outputstream is always used.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 46149] XSLT task only writes to an outputstream
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46149
Stefan Bodewig <bo...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 46149] XSLT task only writes to an outputstream
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46149
Stefan Bodewig <bo...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution| |INVALID
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 46149] XSLT task only writes to an outputstream
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46149
christopher shaun ramos <sh...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|Mac OS X 10.3 |All
Platform|Macintosh |All
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 46149] XSLT task only writes to an outputstream
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46149
Stefan Bodewig <bo...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #1 from Stefan Bodewig <bo...@apache.org> 2008-12-04 01:44:37 PST ---
it really has to be an output stream because the transformer may decide to use
an encoding different from the one used by your writer (this is what you see).
I don't think the Ant task is well suited as a way to do general XSLT
transformations, I'd use TraX directly, which isn't really more difficult than
using the Ant API.
I don't really see how you currently use the Ant API at all since it doesn't
expose a method to write to a stream, but only to files - or am I missing
something?
Honestly, I think this is a WONTFIX case since it sounds as if you were trying
to force Ant into doing things that it doesn't need to do - and your live would
be much simpler of you chose a different approach.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.