Strange Javascript Transfert using Jetspeed : encoding issue ?

Hi all, here's my problem : I have javascript files I'm using within a webapp that I wanted to use with Jetspeed. But there's seem to be transfert errors when I try to get them from jetspeed servlet instead of my servlet... Both servlets are running on the same tomcat (3.3.1 Final) so I really d

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

This is probably because you kept your default Jetspeed encoding as UTF-8. Since this is a variable length encoding, when encountering non-ASCII characters it uses 2 bytes instead of 1... 2 ways around it: - either, make sure you never end a line with an accentuated character to make you're not

RE: Customizing the maximized content ?

Thanks for the reply, Raphael. I'll try over-riding those methods - buildNormalContent(), buildCustomizeContent() and buildMaximizedContent - and see what happens. Btw, may I ask why you say that one should probably use the VelocityPortlet as a basis for our own custom portlets when starting

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

That seems right, but how do I change the default encoding of Jetspeed (I'd prefer to be using iso-8859-1 or 15 encoding) ? I dind't change anything on encoding properties in ressourcesproperties files and I don't remember having this issue with Jetspeed 1.3a2 Thank you for help. Aurélien Perno

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

That's the tricky question :) it actually depends on how you include the js code into the portal but my best guess is: TurbineResources.properties: services.VelocityService.input.encoding=8859_1 > -Message d'origine- > De : Aurélien Pernoud [mailto:[EMAIL PROTECTED]] > Envoyé : jeudi

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

Well i tried including it within the getcontent of a portlet, didn't work. So I tried to modify the default.vm template to include them after the body : Didn't work. Then I tried changing the meta content of the webpage and set it to iso 8859-1, no success :-( Finally I just tried yo

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

Mmm... if you use then your browser loads the js file independantly from the main HTML page so it's the browser responsibility to ensure encoding compatibility between the files. - Try using a direct HTTP request (or wget) on your js file to check if the raw content sent by the servlet engine

RE: Jetspeed neophyte - initial comments.

> I've been playing with Jetspeed for the better part of a day > and am pleased to report that I haven't encountered any real > problems (yet!) - it started fine, and I was surprised how > easy it is to create a rudimentary portlet. > > Some initial comments and questions come to mind. > > 1. F

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

Well done ! Direct access via telnet is ok. On every browser tried I have the issue (IE, Netscape, Mozilla) But when I get the "page info" in mozilla, the default encoding is UTF8 when using jetspeed, and ISO-8859-1 with my other servlet... on the same server (tomcat 3.3.1 final). Any idea ?

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

Looking at the code, it seems that the issue is in the MimeType class that has been changed to hard code the charset to UTF-8 for text/html (with a FIXME note but that's still not an excuse...) You can try removing the hard-coded UTF-8 reference and recompile. This will probably fix your issue bu

RE: Strange Javascript Transfert using Jetspeed : encoding issue ?

Thanks for help, I was getting mad ! I'm reporting a bug right now cause I think it's important and I need ISO-8859 in my webapp :/ Right now i'll just try to rewrite JS Files without accentuated characters and see what happens, because I'm afraid of "I'm unsure what other side effects this may

portlet.setAttribite

Hi, i have a question regarding the parameters of a portlet: When i do a portlet.setAttribute() it sets that just for the user that is viewing the portlet. I would like to set that for all users. (example, only an admin can configure a protlet that users can only view so they should see tha change

RE: portlet.setAttribite

You will need to alter the portlet at the registry level as opposed to the profile level. // retrieve the portlet in question from the registry PortletEntry entry = (PortletEntry) Registry.getEntry("Registry.PORTLET", "MyPortlet"); // retrieve the parameter we want to change Parameter param = e

Re: portlet.setAttribite

Ok works, Thanks. <=- Raffaele Ragni -=> - Original Message - From: "Weaver, Scott" <[EMAIL PROTECTED]> To: "'Jetspeed Users List'" <[EMAIL PROTECTED]> Sent: Subject: RE: portlet.setAttribite -- To unsubscribe, e-mail: For additional commands, e-mail: <

Charset handling in WebPagePortlet

Hi,all I'm using WebPagePortlet and placing 2 web pages in a pane. But if 2 pages have different Japanese charset (ex.Shift-Jis and EUC-JP),it's not displayed correctly. (Jetspeed1.4b1/Tomcat4.1/JDK1.4.0/WindowsXP) So I doubt handling of charset encoding in WebPagePortlet. In WebPagePortlet.java