You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by ICM S CP guest 5 <IC...@icn.siemens.de> on 2001/10/23 14:34:26 UTC

RE: REVISION Content-Type mismatch using hasMediaType ()

The hasMediaType is working correct - but some kind of methode adds the content-type wml/html to portlets without any content-type.

The getType methode has nothing to do with the content-type.




-----Original Message-----
From: ICM S CP guest 5 [mailto:ICM-S-CP.guest-5@icn.siemens.de]
Sent: Dienstag, 23. Oktober 2001 14:21
To: jetspeed-user@jakarta.apache.org
Subject: Content-Type mismatch using hasMediaType ()


Hi,

the result of the hasMediaType () methode is useless.
When I make a selection for wml portlets I get all wml portlets BUT I also get all portlets without a content-type.

Well, you could say - ok, if no content-type is set, it's for both html and wml - but it isn't.
I inserted such a portlet in a wml psml file manually and it doesn't work.

Btw. the hasMediaType() search methode is case-sensitiv this means a selection with "wml" is different to "WML"

So I am trying to fix this bug using the PortletEntry.getType() methode and a String.equalsIgnoreCase compare.

Andreas

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

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