Status

()

Core
XSLT
RESOLVED INVALID
11 years ago
10 years ago

People

(Reporter: Erick Fauquette, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

6.19 KB, application/x-zip-compressed
Details
(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007120205 Minefield/3.0b2pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007120205 Minefield/3.0b2pre

I publish on a unix server and no xslt transformation is done even if the files
xslt and xml are in the same directory.
In same environment transformation works with IE 7.x, Safari.
With tomcat web server on windows transformation works.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
view of the xml file as text file ...
Please provide a testcase. XSLT works fine for me.
(Reporter)

Comment 2

11 years ago
Created attachment 291180 [details]
test case
Works fine for me, the transform seems to run (can't tell if it runs correctly or not given that the testcase is pretty big).

What is it that doesn't work for you?

Could the problem be that you don't have the server configured properly, what mimetype is it sending for the xml and the xslt files? 
(Reporter)

Comment 4

11 years ago
The xml appear as a text file for simple case (xml& xslt)

For transformation using a javascript nothing happen, and if i try twice I get a browser crash ...
Again, please provide testcases. The one you attached works fine for me, is it not for you?

We can't debug this at all without a failing testcase or a very detailed description of what is failing.
(Reporter)

Comment 6

11 years ago
The one I provide works well as local file, with tomcat 6.x on my desktop and wit IE 7.x on the Unix server.
It does  not work only with Mozilla on the Unix server, so I ask my information system engineer to verify mime type.
Given that it works locally and with some servers, but fails with other servers, this seems like a configuration issue.
(Reporter)

Comment 8

11 years ago
I investigate in that way ...
(Reporter)

Comment 9

11 years ago
Server :
  OS : UNIX
  application Server : Websphere
  Web Server : Iplanet 4.2

XML transformation works in such configuration with browsers :

  IE 7.0.5730.13 
  Opera 9.24 
  Opera 9.5 Béta

doesn't work with with browsers :
  FireFox 2.0.0.7
  Minefield 3.0b3 
  Netscape 8.1.3 
  Netscape 9.0.0.4 
  Mozilla 1.7.13 
  SeaMonkey 2.0a1pre

works with all those browsers :
   in file mode (file://)
   using tomcat 6.0 (http://localhost:8080/

On the unix server we add mime types for xsl and xml and the result was unchanged ...

What mime-type did you use. How did you check that the mimetype you try to use is actually used? What happens if you load the url of the stylesheet directly in the browser, what do you see?
(Reporter)

Comment 11

11 years ago
If I try to access the stylesheet with such link :
http://jade.clb.tcfr.thales/sbl/cs_s/en/public/informat/normes/asd/S2000M-xml/styles/s2000m_descript.xsl

I see the content of the stylesheet. 

If I try to access xml file with such link :
http://jade.clb.tcfr.thales/sbl/cs_s/en/public/informat/normes/asd/S2000M-xml/data_modules/DMC-S2000MA00000000A003AA_000.xml
I see the content of the xml file
Exactly what does the stylesheet look like? Do you see it as plain text? Or as the 'xml view' with the description "This XML file does not appear to have any style information associated with it. The document tree is shown below." at the top and the ability to collapse and open elements?

If you're not seeing the xml view you are using the wrong mimetype.

Again, are you sure you have the mimetype configured properly? How are you testing it? What mimetype are you getting?
      
(Reporter)

Comment 13

11 years ago
I see both xml and xsl files as plain text.

Just indented text without possibility to collapse elements.
Then you probably still have a mimetype problem. Please check the mimetype with Page Info (Tools -> Page Info).
(Reporter)

Comment 15

11 years ago
Yes, in both cases the Type is text/plain.
Then this is INVALID, it should be an XML one like text/xml or application/xml. If the server sends the right mimetype, you should try clearing the cache.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
(Reporter)

Comment 17

11 years ago
It works when the server has the mimetype configured to take in account xml and xsl files.

Thanks for your time.
When working with local files, both text/xml by Page Info, the XSL transformation fails to occur.


The XML file leads with:
<?xml version = "1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="../Site.xsl.xml"?>

The XSL file leads with:
<?xml version="1.0" encoding="utf-8"?>
<!--========================================================================-->

<!-- XSL html template for Site output files (10)                           -->

<!--========================================================================-->
<xsl:stylesheet version="1.0" 
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

XSL transformations from the web seem to operate correctly.
       
Comment 18 is not related to this bug but to bug 397894.
You need to log in before you can comment on or make changes to this bug.