Subjects
Home
Xalan extension functions
Fomatting question serializing DOM with pretty print
xalan with pull parser
Cannot find the declaration
Apache Xalan drop support to run on JRE 1 1 x
Why does Doctype change processing of a document
Node set to XML string via Java extensions in Xalan J: possible?
Templates/Transformers + thread safety???
Problem evaluating xpath with muliple prefix with different namespace
remove an arbitrary attribute from xsl output
Xalan3 XSLT 2 0 XPath 2 0 support?
Problem using compiled translets with Xalan !!
Xalan and jstl 1 1 problem with transform tag
NullPointer in DOM2DTM getLocalName
URIResolvers base parameter with xsltc and cascaded imports
Performance problem for Xalan J on intel dual core
Standard libraries in JAXP?
Serializing a DOM tree to XML file, customize entities replacement
Library Conflict Involving BCEL Library
A question on how users are using <xsl:message >
Kevin Cormier as a new Apache Xalan J committer
Struggling to iterate over tokenized string
Xalan count() trouble
Problem with recursive xpath
Error when switching to java 1 5
document( ' ')
Problem with Xalan2 7 0 transformation
cr/lf options
entity encoded XML
can xalan transform 2 xml using one xslt?
Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
xsl transform with cdata section elements
xslt parameters not expanded
Weird behavior of XPath evaluate()
How to avoid <xsl:message > instruction prints stylesheet file informations ?
Cannot find SimpleTransform subdirectory after installing Xalan J
recover from document not found exceptions
jdk1 5 and Xalan jar differences?
Performance Issue
Error/Bug adding floating point numbers
XPathAPI: eval exp using nodes with default namespace
modifying xalan to output invalid XML
NullPointerException
mege two separate xml nodes into one
Is this a XALAN document identification bug?
is StylesheetRoot really java io Serializable ?
transform() fails for DOMSource but succeeds for StreamSource
Thoughts on Transformer parameter passing
HELP, Xalan and jstl 1 1 problem with transformer
Problem with XPath namespace axis?
string utils:replace deleting search string if replacement string is an HTML
help with enumeration values pls
xalan 2 5 1 vs 2 7 performance question
How to insert/update in XML document
HTML Serialization and Handling of Ampersands in HREF Attributes
XHTML link tag stripping
SystemId Unknown; Line #24; Column #49; java lang NullPointerException
xpath text() help
Apostrophe problem with xalan 2 7 0
How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
xsl behavior

xsl behavior

2003-03-19       - By Santiago Pericas-Geertsen
Reply:     1     2     3     4     5     6     7  

Tim, Dimitry,

This looks like a problem in XSLTC. It is checking the context of an
xsl:attribute and trying to be smart as to whether is misplaced or not. The
requirement is for attributes to be output before children. The stylesheet
is OK, but in general a call to xsl:apply-templates *may* add children (e.g.
text nodes) to which an attribute cannot be associated.

Try commenting out line 142 in xsltc/compiler/XslAttribute.java and see
what happens (_ignore = true). Obviously, this heuristic must be revisited
(I think the warning is OK, ignoring the attribute is not).

-- Santiago

----- Original Message -----
From: "Tim Cronin" <tim@(protected)>
To: <xalan-j-users@(protected)>
Sent: Wednesday, March 19, 2003 1:41 PM
Subject: RE: xsl behavior


> Thanks,
>
> Yes I'm using org.apache.xalan.xsltc.trax.TransformerFactoryImpl
>
> it's ignoring the attribute setting. the font never get set to
> red. If I remove the apply templates line it does work and
> of course the warning goes away.
>
> the font template is used to set other font attributes.
> the color attrib needs to be after it in order to over ride
> the default set by the font template.
>
> -----Original Message-----
> From: Voytenko, Dimitry [mailto:dvoytenko@(protected)]
> Sent: Wednesday, March 19, 2003 12:03 PM
> To: 'Tim Cronin'; xalan-j-users@(protected)
> Subject: RE: xsl behavior
>
>
> Hi,
>
> Is that XSLTC then? Interpretive Xalan works fine. XSLTC does output
warning
> saying:
> Compiler warning(s):
> file:///...../test/att.xsl: line 8: Attribute 'color' outside of
> element.
>
> The stylesheet is fine by XSLT specs, but potentially there can be a
> problem. May be that's what this message is intended to say. I don't see
any
> way how the _compiler_ can actually diagnose this kind of problem with
> xsl:apply-templates inside. Such an error can be only cought in run-time
in
> this case.
>
> Thanks,
> Dimitry
>
> -----Original Message-----
> From: Tim Cronin [mailto:tim@(protected)]
> Sent: Wednesday, March 19, 2003 09:40
> To: xalan-j-users@(protected)
> Subject: RE: xsl behavior
>
>
> 2.5D1
>
> -----Original Message-----
> From: Joseph Kesselman [mailto:keshlam@(protected)]
> Sent: Wednesday, March 19, 2003 11:36 AM
> To: Tim Cronin
> Subject: Re: xsl behavior
>
> ><xsl:attribute> must generate its output as the child of an element
> >(either literal result element or <xsl:element> and must precede any
> >non-attribute children.
>
> it is the child of an element, the font template just generates
attributes.
>
> >Try generating the attribute _before_ calling <xsl:apply-templates>.
>
> with the attrib before, the template always overrides it.
>
> the attrib was below the template in order to override what the template
set
> depending
> on the xsl:if.
>
>
> -----Original Message-----
> From: Voytenko, Dimitry [mailto:dvoytenko@(protected)]
> Sent: Wednesday, March 19, 2003 11:45 AM
> To: 'Tim Cronin'; xalan-j-users@(protected)
> Subject: RE: xsl behaviour
>
>
> Hi Tim,
>
> What's the version of Xalan you're using?
>
> Thanks,
> Dimitry
>
> -----Original Message-----
> From: Tim Cronin [mailto:tim@(protected)]
> Sent: Wednesday, March 19, 2003 08:29
> To: xalan-j-users@(protected)
> Subject: xsl behaviour
>
>
> given the following Stylesheet
>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>   <xsl:template match="/">
>   <FONT>
>     <xsl:apply-templates select="/Properties/Group[@(protected)='Data
> Properties']/Datum[@(protected)='Font']/Font"/>
>     <xsl:attribute name="color"><xsl:if
> test="Datum[@(protected)='QuantityShort']&lt;0">Red</xsl:if></xsl:attribute>
>     <xsl:value-of select="Datum[@(protected)='QuantityOnOrder']"/>
>   </FONT>
>   </xsl:template>
>   <xsl:template match="Font">
>     <xsl:attribute name="face"><xsl:value-of
> select="@(protected)"/></xsl:attribute>
>     <xsl:attribute name="color"><xsl:value-of
> select="@(protected)"/></xsl:attribute>
>     <xsl:attribute name="style">font-size:<xsl:value-of select="@(protected)"/>;
> font-style:<xsl:value-of select="@(protected)"/>;font-weight:<xsl:value-of
> select="@(protected)"/>;</xsl:attribute>
>   </xsl:template>
> </xsl:stylesheet>
>
> I get a transformation warning saying that "Attribute color is outside of
> element"
> refering to this line:
> <xsl:attribute name="color"><xsl:if
> test="Datum[@(protected)='QuantityShort']&lt;0">Red</xsl:if></xsl:attribute>
>
> the problem is within the font section
>   <FONT>
>     <xsl:apply-templates select="/Properties/Group[@(protected)='Data
> Properties']/Datum[@(protected)='Font']/Font"/>
>     <xsl:attribute name="color"><xsl:if
> test="Datum[@(protected)='QuantityShort']&lt;0">Red</xsl:if></xsl:attribute>
>     <xsl:value-of select="Datum[@(protected)='QuantityOnOrder']"/>
>   </FONT>
>
> under MS this worked OK...
> should I be able to do this?
>
>
> _____________________________________________________
> Revere Data, LLC, formerly known as Sector Data, LLC, is not affiliated
with
> Sector, Inc., or SIAC.
>
>
> _____________________________________________________
> Revere Data, LLC, formerly known as Sector Data, LLC, is not affiliated
with
> Sector, Inc., or SIAC.