You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by bu...@apache.org on 2003/04/03 22:41:41 UTC

DO NOT REPLY [Bug 17046] - XSL portlet fails to display transformed content

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17046>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17046

XSL portlet fails to display transformed content





------- Additional Comments From caius1440@hotmail.com  2003-04-03 20:41 -------
I just noticed that a new bug was placed that seems very similar to this one.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18666

>From what I remember, something very similar to this was taking place in the XSL
portlet.  If you have no other stylesheet parameters except for 

<parameter name="stylesheet" value="somestylesheet.xsl"/>

then this could be a problem.

The default stylesheet parameter was placed into a map with
MimeType.HTML.toString() as the key.

Later, when trying to determine what stylesheet to use, it uses
CapabilityMap.getPreferredType().toString() to determine the stylesheet.

Obviously, "text/html" != "text/html; charset=UTF-8", and no stylesheet is
chosen since there are no other stylsheets defined in the portlet.

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org