Hi! A few months ago some folks had put a question related to WML portlets that nobody had answered. That question was: why some WML portlets do not work when accessing the portal through a WML browser, lauching the error that follows?
org.apache.turbine.util.TurbineException: Error rendering Velocity template: null This error appears in the middle of the WML code, in the place of the WML card that would correspond to the failing portlet. After some experiments I've found the root of the problem (but not the solution!). Let's try to explain: - when you add a new portlet through the WML customizer, this portlet never works (launching the above error); - the portlets that come in the Jetspeed default installation (MyWeather and StockQuote) both work fine; - if you try to remove those portlets from the user profile and to add them again, they do not work anymore; - analyzing user PSML files, I discovered that the default portlets entries for WML profiles (MyWeather and StockQuote) have a <control name="ClearPortletControl"/> element inside, while the portlet entries created through the WML customizer do not have that element; - after experimenting several WML portlets (with and without the <control> element) I've found that portlet entries without that element do not work. My questions are: 1. Why can't Jetspeed show portlets that do not have the control element in the PSML portlet entry? 2. How can I fix Jetspeed WML customizer in order to insert the control element to the user PSML when adding a new WML portlet? Thank you for your help, Helder --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
