[
http://issues.apache.org/jira/browse/XALANJ-2073?page=comments#action_61970 ]
Brian Minchau commented on XALANJ-2073:
---------------------------------------
A question for the Xalan team is, what should the serializer do when it can't
load these property files, for whatever reason?
Perhaps it is a user configuration problem, perhaps it is a security issue that
causes them not to load. Should we issue a warning but continue with some
recovery? That recovery could be that the Java code itself knows the default
values held in those output_xml, output_html, output_text property files.
Before the serializers that were in Xalan-J interpretive and in XSLTC merged
into the current serializer, the XSLTC serializer had the default values within
the Java code, and they were not configurable in a property file.
That property file is in Xalan, and is now in the JRE. So just how realistic is
it for customers to tweak the contents of these property files? They are
documented and part of the public API, but shoud they be?
> The output format must have a '{http://xml.apache.org/xslt}content-handler'
> property!
> -------------------------------------------------------------------------------------
>
> Key: XALANJ-2073
> URL: http://issues.apache.org/jira/browse/XALANJ-2073
> Project: XalanJ2
> Type: Bug
> Components: Xalan
> Versions: 2.6, 2.4Dx
> Environment: Windows XP Professional, JBoss 3.2.3
> Reporter: Earl Bennett
>
> I am running a service (.SAR) under JBoss 3.2.3. My service is deployed
> "scoped" using <loader-repository> tag in jboss-service.xml. When attempting
> to run an XSL transformation I get
> org.apache.xml.utils.WrappedRuntimeException: The output format must have a
> '{http://xml.apache.org/xslt}content-handler' property!
> at
> org.apache.xalan.serialize.SerializerFactory.getSerializer(SerializerFactory.java:142)
> at
> org.apache.xalan.transformer.TransformerImpl.createResultContentHandler(TransformerImpl.java:1038)
> ...
> It appears SerializerFactory can not find the output-*.properties files when
> run under this configuration.
> Workaround is to add the xsl:content-handler attribute to all XSL files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
