XSLT MIMEtype

I hope someone can help me out. I’m using an agent to print out some XML for a co-worker to use in generating a web page. He uses a XSL stylesheet,

and it works fine in IE. In Firefox we get this error:

Error loading stylesheet: An XSLT stylesheet does not have an XML

mimetype:

We’ve tried a couple of things, including putting an entry in the "File

Identifications". Is there a line I can add that will provide Firefox with

a MIMEtype?

Thanks,

Brian

Subject: XSLT MIMEtype

Not really sure where “File Identifications” lives and how and why you need to set it, but if you use agent to generate XML, you should first print http headers, then the rest of your output:’ print header(s)

Print “Content-type:text/xml”

’ print one empty line to tell Domino that the header is done (it will probably understand it anyway, but just in case)

Print “”

Print "< … here goes your output text…

Subject: RE: XSLT MIMEtype

This is in my agent:

Set doc = view.GetFirstDocument

Print "Content-type: text/xml"	

Print |<?xml version="1.0" encoding="utf-8"?>|

Print |<?xml-stylesheet type="text/xsl" href="test.xsl"?>|

Print "<AIRCATALOG>"

This is the start of my test.xsl doc:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsl:for-each select=“AIRCATALOG/PLANE”>

File Identifications are in the names.nsf > Configuration>Web>File Identifications.

Even with a blank line, I’m Firefox isn’t displaying. I’m totally new at this. Any guidence would be most appreciated.

Cheers,

Brian

Subject: RE: XSLT MIMEtype

ok, right. Of course, your agent has nothing to do with this. It’s the XSL file that do not have a correct Mime type. So it depends how your colleague is providing this XSL.

In your case it looks like it’s some page or another agent as it has the same path as an agent (unless you use some kind of mapping/redirection). It definitely is not a file in filesystem. So if it’s a page you just set Content type, Other text/xml, else could you explain how do you provide this XSL file.

Subject: RE: XSLT MIMEtype

The XSL is a page in the database:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsl:for-each select=“AIRCATALOG/PLANE”>

	<tr style="color:000066;">

		<td style="width:150px; ">

			<div>

				<xsl:value-of select="Type"/>

			</div>

		</td>

		<td style="width:150px;">

			<div>

				Year: 

				<xsl:value-of select="Year"/>

			</div>

		</td>

		<td align="center" style="width:150px;">

			<div>

				<xsl:value-of select="Price"/>

			</div>

		</td>

		<td align="right" style="width:150px;">

			<div>

				S/N: 

				<xsl:value-of select="SerialNumber"/>

			</div>

		</td>

	</tr>
	<tr>

		<td valign="top" style="width:100px;">

			<div style="margin-bottom:10px; ">

			<a><xsl:attribute name="href">

				  http://vmdomino.xx.com:8088/AirSale.nsf/c60c335374583bd68625727a007a7142/<xsl:value-of select="unid"/></xsl:attribute><img height="100" border="0">

				  <xsl:attribute name="src"><xsl:text/>

				  <xsl:value-of select="ThumbnailPic" />

				  </xsl:attribute>

				</img>

			</a>

			</div>

		</td>

		<td style="margin-left:15px; width:450px; vertical-align:top;">

			<div>

				<xsl:value-of select="Description"/>

			</div>

		</td>

	</tr>

	<tr>

		<td colspan="2">

			<div align="right" style="text-decoration:none;">

				<a><xsl:attribute name="href">

				  http://vmdomino.xx.com:8088/AirSale.nsf/c60c335374583bd68625727a007a7142/<xsl:value-of select="unid"/></xsl:attribute>More Info..

				</a>

			</div>

		</td>

	</tr>

</xsl:for-each>

Averit Air Inc. * P.O. Box 17305 * Nashville, TN 37217

ph 800.519.4222 / 615.360.2177 * fax 615.360.7174 * www.xx.com

Subject: RE: XSLT MIMEtype

Not clear what you call “a page”; if it’s a page as “design element Page” then you should be able to fix it as described in my previous answer.

If it’s a Notes document you open using a form, then you can modify the form it gets rendered with; on propeller-hat tab you can enter Content type property for a form.

Subject: RE: XSLT MIMEtype

Yes, a design element page. And changing it on the propeller=hat tab does it.

Thank you very much.

Brian