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.
Added META tag breaks Mozilla - resolved

Added META tag breaks Mozilla - resolved

2003-03-04       - By Paul Warner

Thanks to everyone who answered - you guys are great.

I found the error - in the servlet code I'm modifying,
the content type for the response object was being set
to "text/xml".  I missed that.  This was overriding
the setting in the xsl stylesheet, which is clearly
set to "html".  The link to:
http://xml.apache.org/xalan-j/usagepatterns.html#outputprops
mentioned that the Writer will override the setting in
the xsl file, so that's why I started looking for it.

Thanks again for the help - and sorry for the trouble.
I hope this thread helps someone.

Now that Mozilla knows its getting html, I've removed
the omit-meta-tag line from the xsl, and it's handling
the automatically inserted meta tag fine now.

Thanks,
Paul Warner


--- zongaro@(protected) wrote:
> Hi Paul,
>
>      Is the output of your transform supposed to be
> XML or HTML?  If the
> output method is html, an XSLT processor should
> output a META tag as part
> of the content of an HTML HEAD element.  Because
> META is an empty HTML
> element, it's written using the empty-tag syntax of
> HTML - namely:
>
>   <META attr=val attr=val ... >
>
> as opposed to the XML empty-tag syntax:
>
>   <META attr=val attr=val ... />
>
>
>      It sounds like the output of your
> transformation is an HTML document
> that is being treated by Mozilla as an XML input
> document, for some
> reason.
>
> Thanks,
>
> Henry
>
------------------------------------------------------------------
> Henry Zongaro      Xalan development
> IBM SWS Toronto Lab   Tie Line 969-6044;  Phone
> (905) 413-6044
> mailto:zongaro@(protected)
>
>
>
>
> Paul Warner <paulwwarner@(protected)>
> 03/04/2003 05:38 PM
>
>  
>         To:     xalan-j-users@(protected)
>         cc:
>         Subject:        Added META tag breaks
> Mozilla
>
>  
>
> Hello,
>
> I get this error when running a simple transform in
> a
> servlet:
>
> XML Parsing Error: mismatched tag. Expected:
> </META>.
> Location:
> http://localhost:8080/diaries/servlet/ParseDiaries
> Line Number 18, Column 3:
> </HEAD>
> --^
>
> Xalan is adding a META tag without adding a close -
> and it's refusing to display in Mozilla.  I tried
> inserting a </META> close in the xsl stylesheet, but
> that bombs of course.  How can I suppress that META
> tag?  Or force it to add the </META>?
> Interestingly,
> if I add my own meta tag with it's own close tag,
> Xalan will remove my </META> close tag then add it's
> own META tag (without close) just ahead of mine.
> Which leaves two identical META tags, neither with
> close tags, and this of course generates the same
> error.
>
> I looked for information on this in the archives and
> in Google, and I can see it's part of the spec to
> add
> this tag - but no one says how to suppress it or
> force
> it to be a complete tag with a close.
>
> Thanks for any help.
>
> Paul Warner
>
>
>