Hi there,
we just started playing around with jetspeed 1.3.1a, having a closer look on
1.3.a2. But we are getting confused now. Version 1.3.1a seems to run fine,
but we have some problems using 1.3.a2.
1) Our main interest is in the customizer, that looks better in 1.3.2a, but
does not really work for us (but for everybody else it seems):
- Move / Changing the portlet position does not work (with no nightly cvs
download since the last week where we started examing)
- Sometimes a portlet is shown twice after customizing. Recustomizing and
removing this double entry leads to an horrible error:
Horrible Exception: java.lang.reflect.InvocationTargetException:
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:382)
at java.lang.Integer.parseInt(Integer.java:463)
at
org.apache.jetspeed.modules.actions.controllers.RowColumnControllerAction.do
Delete(RowColumnControllerAction.java:321)
at java.lang.reflect.Method.invoke(Native Method)
at
org.apache.turbine.util.velocity.VelocityActionEvent.executeEvents(VelocityA
ctionEvent.java:166)
at
org.apache.jetspeed.modules.actions.controllers.VelocityControllerAction.per
form(VelocityControllerAction.java:110)
at org.apache.turbine.modules.ActionLoader.exec(ActionLoader.java:122)
at
org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:143)
at org.apache.turbine.modules.Page.build(Page.java:90)
at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123)
at org.apache.turbine.Turbine.doGet(Turbine.java:462)
at org.apache.turbine.Turbine.doPost(Turbine.java:552)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:81
2)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:758)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:213)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Thread.java:484)
- Layout seems not do what we told the customizer (selecting a two column
layout can lead to a three column layout for some portlets after leaving
with Save&Apply)
- Everytime a user visits the customize/add portlet dialog - not one portlet
is checked. Never ! (Or is this meant that way ?)
2) Besides guessing that support questions concerning 1.3.1a will lead to a
"use 1.3.a2" answer, what parts of 1.3.a2 you would consider as instable for
now ?
3) Why is that new RSS portlet from 1.3.2a not working at all ?
org.apache.turbine.util.TurbineException: Error rendering Velocity template:
/controls/html/jetspeed.vm: Invocation of method 'getContent' in class
org.apache.jetspeed.portal.portlets.NewRSSPortlet threw exception class
java.lang.NoSuchMethodError : null
4) We recognized some changes concerning config files for portlets. But did
you change the api for portlets as well ? Is it possible to create portlets
with 1.3.1a and using them later for 1.3.a2 without changing the java code ?
Best regards and keep on with this good work,
Ron
PS: We are currently using nightly build from today/tonight and tomcat
version 3.2.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
