There has been a change between b3 and b4 relative to encoding : Here's how jetspeed looks for the encoding to use now, if you use the right way to grab parameters (see next) : 1) the character encoding used in the body of the request. 2) character-set parameter in media.xreg 3) content.defaultencoding in JetspeedResources.properties 4) US-ASCII
so check all those parameters to see if one may be wrong for you. Although there is two ways to "grab" your request parameters in your portlets : data.getRequest().getParameter(aParameterName) : WRONG data.getParameters().getString(aParameterName) : RIGHT Cause Servlet 2.2 API is known to be buggy when encoding is different from ISO8859-1, so you should better use the parameterparser provided in jetspeed (second method). So check all this parameters and see where your trouble comes from. HTH, Aurelien PS : if you're using tomcat 3, then you're meeting a specific bug from it, and right now jetspeed is still buggy with tomcat 3. Ivan a ecrit : > Hello everybody, > > I got a problem and I'm not sure if it's a bug or a > misconfiguration of my system. > > I had a 1.4b3 portal working ok, and after the upgrade > to 1.4b4 some portlets are not sending the form post info well. > > this is where It sent "Ivan" now it sends "IvC!n", it > looks like some ascii to hex change... > > Anyone knows what can it happen??? > > Many thanks in advance. > Ivan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
