Le vendredi 04 f�vrier 2005 � 21:17 +0100, Erik Bruchez a �crit :
> It looks like it's trying to access the resource as HTML. To fix this,
> use <content-type>application/xml</content-type>, and use
> <force-content-type>true</force-content-type>.
Hmmm... Which processor does support these parameters?
Right now, I was accessing this resource through either XSLT or the
identity processor!
> This said, the initial resource should have the correct content-type
> header...
Yes, and Microsoft should support the correct content-type header for
XHTML too, otherwise people that want to be conform to the spec miss 80%
of their visitors :-( ...
Eric
--
Weblog:
http://eric.van-der-vlist.com/blog?t=category&a=English
------------------------------------------------------------------------
Eric van der Vlist http://xmlfr.org http://dyomedea.com
(ISO) RELAX NG ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
orbeon-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
