You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Berin Loritsch <bl...@infoplanning.com> on 2000/08/01 14:10:14 UTC
Re: Cocoon and IE 5.5
Martin Erlandsson wrote:
>
> Greetings fellow Cocooners!
>
> I upgraded to IE 5.5 and now I am having troubles viewing my Cocoon files.
> IE 5.5 seems more picky about file extentions than IE 5.01.
>
> Example:
>
> When requesting the fo sample darkness-novel.xml like this:
>
> .../samples/fo/darkness-novel.xml
> and also
> .../samples/fo/darkness-novel.xml?
>
> I get a blank page.
>
> However,
>
> .../samples/fo/darkness-novel.xml?.pdf
>
> works, but is not a clean solution in the long run (I think).
>
> While waiting for Cocoon 2 to solve this, does anyone have a suggestion how
> to solve this nicely with Cocoon 1.x ?
Save your xml files with the PDF extension and have Cocoon process them.
Cocoon doesn't have a problem with extensions--IE does (not following spec
and forcing everyone to work around their stupidity).
The only problem with that solution is that you cannot store real PDF
documents in the same context as Cocoon.
So it would work like this:
rename darkness-novel.xml to darkness-novel.pdf, and set the servlet mapping
to have Cocoon process "*.pdf" as well as "*.xml".
Re: SV: Cocoon and IE 5.5
Posted by Donald Ball <ba...@webslingerZ.com>.
On Sat, 5 Aug 2000, Stefano Mazzocchi wrote:
> > yeah - pick an extension that IE doesn't choose to interpret instead of
> > examining the content-type mime header (stupid or malicious? you be the
> > judge) - say .iesux and use that instead of .xml. you can still use your
> > ?output= trick.
>
> what does IE5.5 do if you have a URL without an extention (such as
> /docs/news/today) but with the right MIME-type?
it goes by the mime type in that case - yet another argument in favor of
losing file extensions in URLs. you know, it'd be cool if someone could
puzzle out the best way to map extensionsless URLs to files in cocoon1 and
apache-jserv and/or tomcat and document it for the list...
- donald
Re: SV: Cocoon and IE 5.5
Posted by Stefano Mazzocchi <st...@apache.org>.
Donald Ball wrote:
>
> On Tue, 1 Aug 2000, Martin Erlandsson wrote:
>
> > >Cocoon doesn't have a problem with extensions--IE does (not
> > >following spec
> > >and forcing everyone to work around their stupidity).
> > >
> > >The only problem with that solution is that you cannot store real PDF
> > >documents in the same context as Cocoon.
> > >
> > >So it would work like this:
> > >
> > >rename darkness-novel.xml to darkness-novel.pdf, and set the
> > >servlet mapping
> > >to have Cocoon process "*.pdf" as well as "*.xml".
> >
> > Thanks for your prompt answer!
> >
> > I agree, that is *usually* a better solution than the "?.pdf".
> > However, I often use parameters to output one xml file to several different
> > stylesheets, like:
> >
> > .../document.xml?output=pdf
> > or
> > .../document.xml?output=html
> > or
> > .../document.xml?output=wap
> >
> > I port this through a parameter-testing stylesheet with dynamic processing
> > instructions.
> >
> > It would take one copy of the xml file for every type of stylesheet I want
> > to use, and that kind of kills the idea of parallel publishing. :)
> >
> > More suggestions, anyone?
>
> yeah - pick an extension that IE doesn't choose to interpret instead of
> examining the content-type mime header (stupid or malicious? you be the
> judge) - say .iesux and use that instead of .xml. you can still use your
> ?output= trick.
what does IE5.5 do if you have a URL without an extention (such as
/docs/news/today) but with the right MIME-type?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
Re: SV: Cocoon and IE 5.5
Posted by Donald Ball <ba...@webslingerZ.com>.
On Tue, 1 Aug 2000, Martin Erlandsson wrote:
> >Cocoon doesn't have a problem with extensions--IE does (not
> >following spec
> >and forcing everyone to work around their stupidity).
> >
> >The only problem with that solution is that you cannot store real PDF
> >documents in the same context as Cocoon.
> >
> >So it would work like this:
> >
> >rename darkness-novel.xml to darkness-novel.pdf, and set the
> >servlet mapping
> >to have Cocoon process "*.pdf" as well as "*.xml".
>
> Thanks for your prompt answer!
>
> I agree, that is *usually* a better solution than the "?.pdf".
> However, I often use parameters to output one xml file to several different
> stylesheets, like:
>
> .../document.xml?output=pdf
> or
> .../document.xml?output=html
> or
> .../document.xml?output=wap
>
> I port this through a parameter-testing stylesheet with dynamic processing
> instructions.
>
> It would take one copy of the xml file for every type of stylesheet I want
> to use, and that kind of kills the idea of parallel publishing. :)
>
> More suggestions, anyone?
yeah - pick an extension that IE doesn't choose to interpret instead of
examining the content-type mime header (stupid or malicious? you be the
judge) - say .iesux and use that instead of .xml. you can still use your
?output= trick.
- donald
RE: Cocoon and IE 5.5
Posted by Donald Ball <ba...@webslingerZ.com>.
On Wed, 2 Aug 2000, Mauro Canal wrote:
> The work around with Servlets or CGI-Scripts for the IE behavior is
> to use the PATH_INFO variable:
>
> .../YourServlet/iedummy.pdf?yourparam=yourvalue
> .../YourServlet/iedummy.html?yourparam=yourvalue
>
> But passing this to Cocoon it throws
>
> .../document.xml/iedummy.pdf?yourparam=yourvalue
>
> org.xml.sax.SAXParseException:
> File "file:/.../document.xml/iedummy.pdf" not found.
>
> Can someone explain this?
ick. well, take a look at the path munging code from cocoon1 sometime and
see if you think it's patchable. the problem is the different servlet
engines sometimes give you different results for getRequestURI,
getPathInfo, and getPathTranslated. the problem gets worse when you add
extension-invoked servlets (.xml invokes /servlet/org.apache.cocoon.Cocoon)
- donald
RE: Cocoon and IE 5.5
Posted by Mauro Canal <mc...@connext.ch>.
The work around with Servlets or CGI-Scripts for the IE behavior is
to use the PATH_INFO variable:
.../YourServlet/iedummy.pdf?yourparam=yourvalue
.../YourServlet/iedummy.html?yourparam=yourvalue
But passing this to Cocoon it throws
.../document.xml/iedummy.pdf?yourparam=yourvalue
org.xml.sax.SAXParseException:
File "file:/.../document.xml/iedummy.pdf" not found.
Can someone explain this?
Thanks
Mauro
> -----Original Message-----
> From: Martin Erlandsson [mailto:martin@inzide.se]
> Sent: Tuesday, August 01, 2000 2:43 PM
> To: cocoon-users@xml.apache.org
> Subject: SV: Cocoon and IE 5.5
>
>
> >Martin Erlandsson wrote:
> >>
> >> Greetings fellow Cocooners!
> >>
> >> I upgraded to IE 5.5 and now I am having troubles viewing my
> >Cocoon files.
> >> IE 5.5 seems more picky about file extentions than IE 5.01.
> >>
> >> Example:
> >>
> >> When requesting the fo sample darkness-novel.xml like this:
> >>
> >> .../samples/fo/darkness-novel.xml
> >> and also
> >> .../samples/fo/darkness-novel.xml?
> >>
> >> I get a blank page.
> >>
> >> However,
> >>
> >> .../samples/fo/darkness-novel.xml?.pdf
> >>
> >> works, but is not a clean solution in the long run (I think).
> >>
> >> While waiting for Cocoon 2 to solve this, does anyone have a
> >suggestion how
> >> to solve this nicely with Cocoon 1.x ?
> >
> >Save your xml files with the PDF extension and have Cocoon
> >process them.
> >
> >Cocoon doesn't have a problem with extensions--IE does (not
> >following spec
> >and forcing everyone to work around their stupidity).
> >
> >The only problem with that solution is that you cannot store real PDF
> >documents in the same context as Cocoon.
> >
> >So it would work like this:
> >
> >rename darkness-novel.xml to darkness-novel.pdf, and set the
> >servlet mapping
> >to have Cocoon process "*.pdf" as well as "*.xml".
>
> Thanks for your prompt answer!
>
> I agree, that is *usually* a better solution than the "?.pdf".
> However, I often use parameters to output one xml file to several
> different
> stylesheets, like:
>
> .../document.xml?output=pdf
> or
> .../document.xml?output=html
> or
> .../document.xml?output=wap
>
> I port this through a parameter-testing stylesheet with dynamic processing
> instructions.
>
> It would take one copy of the xml file for every type of stylesheet I want
> to use, and that kind of kills the idea of parallel publishing. :)
>
> More suggestions, anyone?
> Or do we have to wait for Cocoon 2 to come and save the day?
>
> /Martin Erlandsson
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
SV: Cocoon and IE 5.5
Posted by Martin Erlandsson <ma...@inzide.se>.
>Martin Erlandsson wrote:
>>
>> Greetings fellow Cocooners!
>>
>> I upgraded to IE 5.5 and now I am having troubles viewing my
>Cocoon files.
>> IE 5.5 seems more picky about file extentions than IE 5.01.
>>
>> Example:
>>
>> When requesting the fo sample darkness-novel.xml like this:
>>
>> .../samples/fo/darkness-novel.xml
>> and also
>> .../samples/fo/darkness-novel.xml?
>>
>> I get a blank page.
>>
>> However,
>>
>> .../samples/fo/darkness-novel.xml?.pdf
>>
>> works, but is not a clean solution in the long run (I think).
>>
>> While waiting for Cocoon 2 to solve this, does anyone have a
>suggestion how
>> to solve this nicely with Cocoon 1.x ?
>
>Save your xml files with the PDF extension and have Cocoon
>process them.
>
>Cocoon doesn't have a problem with extensions--IE does (not
>following spec
>and forcing everyone to work around their stupidity).
>
>The only problem with that solution is that you cannot store real PDF
>documents in the same context as Cocoon.
>
>So it would work like this:
>
>rename darkness-novel.xml to darkness-novel.pdf, and set the
>servlet mapping
>to have Cocoon process "*.pdf" as well as "*.xml".
Thanks for your prompt answer!
I agree, that is *usually* a better solution than the "?.pdf".
However, I often use parameters to output one xml file to several different
stylesheets, like:
.../document.xml?output=pdf
or
.../document.xml?output=html
or
.../document.xml?output=wap
I port this through a parameter-testing stylesheet with dynamic processing
instructions.
It would take one copy of the xml file for every type of stylesheet I want
to use, and that kind of kills the idea of parallel publishing. :)
More suggestions, anyone?
Or do we have to wait for Cocoon 2 to come and save the day?
/Martin Erlandsson