Kristian Marinkovic a écrit :
havent tried myself, but it should work this way...
you could create a Dispatcher and inject the Request service.
by analyzing the http headers you can determine the client and
set the content-type of the response accordingly
I think that the problem here is if Tapestry see "text/html", it
switches to its SGML renderer and so the input is not longer valid XHTML
(it's valid HTML).
Perhaps I misunderstood, but I believe that Christian
1/ want to render valid XHTML
2/ have to use "text/html" content type.
--
Francois Armand
Etudes & Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
-----------
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
