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.
annoying senseless warnings

annoying senseless warnings

2005-10-09       - By Sonja Löhr
Reply:     1     2     3  

Thanks, David.
The two apply-templates copy the two attributes (through a general
copying template matching "@*|node"). I will replace them with
<xsl:copy-of> or, as you say, just change the order of the elements
inside xsl:copy.
Just for technical interest: Since the output is fine, xalan seems to
not be able to predict that the result of the two apply-templates will
be just attributes?
Thanks again!
sonja



Am Sonntag, den 09.10.2005, 10:27 -0400 schrieb
david_marston@(protected):
> Sonja L?hr <sonjaloehr@(protected)> writes:
> <xsl:template match="map/area">
>     <xsl:copy>
>         <xsl:apply-templates select="@(protected)"/>
>         <xsl:apply-templates select="@(protected)"/>
>         <xsl:attribute name="href">
>             <xsl:value-of select="$country_url"/>etc.
>         </xsl:attribute>
>     </xsl:copy>
> </xsl:template>
> >With each area element I get the following warning:
> >That is: "attribute 'href' is not inside an element"
>
> The two apply-templates for @(protected) and @(protected) must only construct
> attributes or namespace
> declarations, because nodes of those two types must be constructed within
> an element before
> any text nodes, comments, child elements, or processing instructions.
>
> Since the order of the attributes is irrelevant, I suggest putting the
> xsl:attribute instruction before
> the  two apply-templates. Even so, you should review the templates that
> would be invoked by the
> two apply-templates to ensure that they finish constructing attributes
> before the other kinds of
> nodes.
> .................David Marston
--
Sonja L?hr <sonjaloehr@(protected)>