Forgot to mention that the JARs included in WEB-INF/lib were built from the trunk with JDK 1.5 on 10/31/2007.

Hi Neil,

I am using the latest Liferay Portal bundle "liferay-portal-tomcat-6.0-4.3.4" and forsome reason the attached war is not working with it, may be i am not properly launching it. However using the same bundle I have tested the inputRichText component with the dyn-chart (facelets version) demo with JDK 1.5, trunk built on 11/30/2007. The inputRichText component is working fine. Can you please retest your demo with the head.

Thanks,

Hi Neil,

Yes I did put it in the webapps folder directly. This is the first app I have tested with the portlets, that is why I was not sure if I launched it properly.

When I have downloaded the bundle I didn't get the liferay/deploy folders?

Thanks,

Adnan,

The $HOME/liferay/deploy folder is created by the Liferay+Tomcat bundle after you run the Tomcat startup.bat file.

On Windows, look for a folder like:
C:\Documents and Settings\adnan\liferay\deploy

On MacOS/Linux/Unix, look for something like:
/home/adnan/liferay/deploy

See "Installation Instructions" on this page:
http://www.liferay.com/web/guest/downloads/official_plugins

Neil

Hi Neil,

Thanks for the information and the link. After copying the plugin into the hot deploy directory, I can see the message "Portlets for icetest-portlet registered successfully" but when I launch the app using the following URL: http://localhost:8080/icetest-portlet/, I see the "HTTP Status 404 - /icetest-portlet/". Any idea?

Thanks,

Adnan,

Although a portlet is packaged like any other webapp, the portal will prevent you from trying to run it directly from a URL like that. Instead, visit http://localhost:8080 and login to the portal first. The username is test@liferay.com and the password is test. Then, click the "Add Page" button to add a new portal page. Then, under the "Welcome Joe Bloggs" menu, click on "Add Content". You can add the portlet to your portal page by clicking the "Add" button next to it. You'll find it it under the the "Sample" category. It is named "ICEfaces Test".

Neil

As of trunk revision 15355 on 12/12/2007 I'm now seeing a new error. When I have an <ice:inputRichText /> on the .xhtml page, I get the message "URI CREATED JUST ONE" in the console and the Facelet doesn't render at all.

I've just had an initial look at this. It appears that the InputRichText component registers the FCKEditor JavaScript files that need to be served up with BridgeFacesContext using the loadJavascriptCode() methods. These methods add the locations of the resources to be served when the component is rendered. However, these resources are actually written into the page in the DOMResponseWriter.enhanceHead() method which does not look like it gets executed in a portlet environment. It's likely we need a different mechanism so that the script resources are written into the portlet content directly.

The problem with this is more general and affects any component that depends on injecting 3rd party JavaScript while running in a portlet environment.

The common issue of injecting component-specific JavaScript has been fixed. The Rich Text Editor now works in a portlet environment. Resolving as fixed.