Re: Some observations on jetspeed-2 (cont)
Just to confirm, exact same problems with Tomcat 4.28. Tried running under Solaris, fails at the allBuild stage. Probably linked to the Apache site problems, but it's strange the Windows build doesn't fail then : java:prepare-filesystem: java:compile: [echo] Compiling to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] Compiling 35 source files to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspeed/portlet/ServletContextProviderImpl.java:28: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: package common [javac] import org.apache.portals.bridges.common.ServletContextProvider; [javac] ^ [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspeed/portlet/ServletContextProviderImpl.java:36: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: class org.apache.jetspeed.portlet.ServletContextProviderImpl [javac] public class ServletContextProviderImpl implements ServletContextProvider [javac]^ [javac] 2 errors BUILD FAILED File.. /local/user/Source/jakarta-jetspeed-2/maven.xml Element... maven:reactor Line.. 133 Column 40 Unable to obtain goal [java:compile] -- /local/user/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48: ant:javac Compile failed; see the compiler error output for details. Total time: 1 minutes 42 seconds Finished at: Fri Sep 24 14:59:10 CEST 2004 [EMAIL PROTECTED] wrote: Perhaps better suited for the developers list, but I didn't really want to subscribe there. Hopefully these comments will be of use to the developers in understanding from a user perspective some of the issues of the current development state of jetspeed-2. 1)Compared to jetspeed-1, the jetspeed-2 installation makes quite a mess of your application server, and pretty much renders it unusable for anything else you were planning to host in it. While jetspeed-1 had a lovely simple war file to drop in/out, jetspeed-2 installs roughly 10 seperate servlets, none of which can be uninstalled by any targets I found in the maven build file. I always understood portlets were supposed to be run hosted in a Portlet server, so I don't really understand the need to publish all these servlets - they should be Portlets, and thus not visible from the application server perspective. Hopefully this will be sorted out as we near a production version, and the install gets a bit more streamlined 2)Default install on clean jakarta-tomcat-5.0.28 give me the following errors right off the bat when accessing the index page:: CNF: java.lang.ClassNotFoundException: org.apache.jetspeed.portlets.layout.MultiColumnPortlet:org.apache.jetspeed.portle ts.layout.MultiColumnPortlet 3)The My First PSML Page accesible off the main guest screen gives me an immediate : Invocation of method 'getCurrentPortletEntity' in class org.apache.jetspeed.velocity.JetspeedPowerTool threw exception class java.lang.NullPointerException : null org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getCurrentPortletEntity' in class org.apache.jetspeed.velocity.JetspeedPowerTool threw exception class java.lang.NullPointerException : null at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:193) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.jetspeed.velocity.JetspeedVelocityViewServlet.mergeTemplate(JetspeedVelocityViewServlet.java:116) at org.apache.velocity.tools.view.servlet.VelocityViewServlet.doRequest(VelocityViewServlet.java:455) at org.apache.velocity.tools.view.servlet.VelocityViewServlet.doGet(VelocityViewServlet.java:411) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Strangley the My Second PSML page works with no problems. 4) The Test Suite Page tab has errors in each prtlet window, all complaining : org.apache.jetspeed.aggregator.FailedToRenderFragmentException: Unable to render fragment because: org.apache.jetspeed.container.window.FailedToRetrievePortletWindow: org.apache.jetspeed.container.window.FailedToCreateWindowException: Error generating new PortletEntity:
RE: Some observations on jetspeed-2 (cont)
wh, I have been working with J2 for about a month or so and have had minimal problems, especially considering the current alpha state of the release. The dev team is pressing hard for a release this fall and there is plenty going on! I think I can help with some of your isses: 1) to minimize the install, you can remove the unnecessary war files from the deploy directory before starting tomcat after the first install. 'quickStart' can also be tuned and there are other goals that one could probably employ... but I am not a maven expert yet! The multiple portlet-app install is by design. The goal is to be able to install jetspeed and your configuration separately. BTW, removing items out of the deploy directory was intended to uninstall them, but that is not working under all circumstances yet! 2) I canont duplicate this error. What URL are you using to lauch and where does this appear? 34) I do see these messages... they may be related to recent changes in the decorator and layout templates or fragment rendering. No doubt this will get fixed. I will look into this today if I get a chance and forward what I find to the dev team. 5) Profiling has just recently been enabled and the test configuration pages have not been changes to reflect this. You should expect this to be addressed as the profiling subsytem is brought up to speed. If you long in as user/user, you will see some profiling taking place. The jetspeed/jetspeed user is not customized at this point. 6) There should be a logout link in the login portlet after you have logged in. This worked for me. Finally, I think that you would be better served by the team if you posted this kind of thing to the dev list. J2 is in alpha state and things are going to break as other things are added and fixed. I suspect that you know that! Thanks for the input, Randy Watler -Original Message- From: [EMAIL PROTECTED] To: Jetspeed Users List Sent: 9/24/04 7:05 AM Subject: Re: Some observations on jetspeed-2 (cont) Just to confirm, exact same problems with Tomcat 4.28. Tried running under Solaris, fails at the allBuild stage. Probably linked to the Apache site problems, but it's strange the Windows build doesn't fail then : java:prepare-filesystem: java:compile: [echo] Compiling to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] Compiling 35 source files to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspe ed/portlet/ServletContextProviderImpl.java:28: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: package common [javac] import org.apache.portals.bridges.common.ServletContextProvider; [javac] ^ [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspe ed/portlet/ServletContextProviderImpl.java:36: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: class org.apache.jetspeed.portlet.ServletContextProviderImpl [javac] public class ServletContextProviderImpl implements ServletContextProvider [javac]^ [javac] 2 errors BUILD FAILED File.. /local/user/Source/jakarta-jetspeed-2/maven.xml Element... maven:reactor Line.. 133 Column 40 Unable to obtain goal [java:compile] -- /local/user/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48: ant:javac Compile failed; see the compiler error output for details. Total time: 1 minutes 42 seconds Finished at: Fri Sep 24 14:59:10 CEST 2004 [EMAIL PROTECTED] wrote: Perhaps better suited for the developers list, but I didn't really want to subscribe there. Hopefully these comments will be of use to the developers in understanding from a user perspective some of the issues of the current development state of jetspeed-2. 1)Compared to jetspeed-1, the jetspeed-2 installation makes quite a mess of your application server, and pretty much renders it unusable for anything else you were planning to host in it. While jetspeed-1 had a lovely simple war file to drop in/out, jetspeed-2 installs roughly 10 seperate servlets, none of which can be uninstalled by any targets I found in the maven build file. I always understood portlets were supposed to be run hosted in a Portlet server, so I don't really understand the need to publish all these servlets - they should be Portlets, and thus not visible from the application server perspective. Hopefully this will be sorted out as we near a production version, and the install gets a bit more streamlined 2)Default install on clean jakarta-tomcat-5.0.28 give me the following errors right off the bat when accessing the index page:: CNF: java.lang.ClassNotFoundException: org.apache.jetspeed.portlets.layout.MultiColumnPortlet:org.apache.jetspe ed.portle
Re: Some observations on jetspeed-2 (cont)
Thanks for the feedback. I appreciate all is in flux at the moment, that's why I tried to detail as much as possible all that I did. I'm sure it will get better. In response to your 2) that is the Tomcat trace I get when I go from the Tomcat manager list if applets and click on the jetspeed servlet, so essentially the URL is yourtomcatroot/jetspeed I find it strange none one else has these errors, I used a clean Tomcat, clean Jetspeed install, tried on both Solaris and Windows. I'll try again tomorrow by cleaning my maven cache in case it had some bad jars from the Apache site problems. cheers wh Randy Watler wrote: wh, I have been working with J2 for about a month or so and have had minimal problems, especially considering the current alpha state of the release. The dev team is pressing hard for a release this fall and there is plenty going on! I think I can help with some of your isses: 1) to minimize the install, you can remove the unnecessary war files from the deploy directory before starting tomcat after the first install. 'quickStart' can also be tuned and there are other goals that one could probably employ... but I am not a maven expert yet! The multiple portlet-app install is by design. The goal is to be able to install jetspeed and your configuration separately. BTW, removing items out of the deploy directory was intended to uninstall them, but that is not working under all circumstances yet! 2) I canont duplicate this error. What URL are you using to lauch and where does this appear? 34) I do see these messages... they may be related to recent changes in the decorator and layout templates or fragment rendering. No doubt this will get fixed. I will look into this today if I get a chance and forward what I find to the dev team. 5) Profiling has just recently been enabled and the test configuration pages have not been changes to reflect this. You should expect this to be addressed as the profiling subsytem is brought up to speed. If you long in as user/user, you will see some profiling taking place. The jetspeed/jetspeed user is not customized at this point. 6) There should be a logout link in the login portlet after you have logged in. This worked for me. Finally, I think that you would be better served by the team if you posted this kind of thing to the dev list. J2 is in alpha state and things are going to break as other things are added and fixed. I suspect that you know that! Thanks for the input, Randy Watler -Original Message- From: [EMAIL PROTECTED] To: Jetspeed Users List Sent: 9/24/04 7:05 AM Subject: Re: Some observations on jetspeed-2 (cont) Just to confirm, exact same problems with Tomcat 4.28. Tried running under Solaris, fails at the allBuild stage. Probably linked to the Apache site problems, but it's strange the Windows build doesn't fail then : java:prepare-filesystem: java:compile: [echo] Compiling to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] Compiling 35 source files to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspe ed/portlet/ServletContextProviderImpl.java:28: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: package common [javac] import org.apache.portals.bridges.common.ServletContextProvider; [javac] ^ [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspe ed/portlet/ServletContextProviderImpl.java:36: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: class org.apache.jetspeed.portlet.ServletContextProviderImpl [javac] public class ServletContextProviderImpl implements ServletContextProvider [javac]^ [javac] 2 errors BUILD FAILED File.. /local/user/Source/jakarta-jetspeed-2/maven.xml Element... maven:reactor Line.. 133 Column 40 Unable to obtain goal [java:compile] -- /local/user/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48: ant:javac Compile failed; see the compiler error output for details. Total time: 1 minutes 42 seconds Finished at: Fri Sep 24 14:59:10 CEST 2004 [EMAIL PROTECTED] wrote: Perhaps better suited for the developers list, but I didn't really want to subscribe there. Hopefully these comments will be of use to the developers in understanding from a user perspective some of the issues of the current development state of jetspeed-2. 1)Compared to jetspeed-1, the jetspeed-2 installation makes quite a mess of your application server, and pretty much renders it unusable for anything else you were planning to host in it. While jetspeed-1 had a lovely simple war file to drop in/out, jetspeed-2 installs roughly 10 seperate servlets, none of which can be uninstalled by any targets I found in the maven build file. I always understood portlets were
Re: Some observations on jetspeed-2 (cont)
Yup. I'm getting the same errors now (was working last week). Looks like there is a new (at least I haven't noticed it before) jar file Maven is trying to download... jetspeed-web-content-2.0-a1-dev.jar. Could this be the problem? Thanks, -Michael [EMAIL PROTECTED] wrote: Just to confirm, exact same problems with Tomcat 4.28. Tried running under Solaris, fails at the allBuild stage. Probably linked to the Apache site problems, but it's strange the Windows build doesn't fail then : java:prepare-filesystem: java:compile: [echo] Compiling to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] Compiling 35 source files to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspeed/portlet/ServletContextProviderImpl.java:28: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: package common [javac] import org.apache.portals.bridges.common.ServletContextProvider; [javac] ^ [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspeed/portlet/ServletContextProviderImpl.java:36: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: class org.apache.jetspeed.portlet.ServletContextProviderImpl [javac] public class ServletContextProviderImpl implements ServletContextProvider [javac]^ [javac] 2 errors BUILD FAILED File.. /local/user/Source/jakarta-jetspeed-2/maven.xml Element... maven:reactor Line.. 133 Column 40 Unable to obtain goal [java:compile] -- /local/user/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48: ant:javac Compile failed; see the compiler error output for details. Total time: 1 minutes 42 seconds Finished at: Fri Sep 24 14:59:10 CEST 2004 [EMAIL PROTECTED] wrote: Perhaps better suited for the developers list, but I didn't really want to subscribe there. Hopefully these comments will be of use to the developers in understanding from a user perspective some of the issues of the current development state of jetspeed-2. 1)Compared to jetspeed-1, the jetspeed-2 installation makes quite a mess of your application server, and pretty much renders it unusable for anything else you were planning to host in it. While jetspeed-1 had a lovely simple war file to drop in/out, jetspeed-2 installs roughly 10 seperate servlets, none of which can be uninstalled by any targets I found in the maven build file. I always understood portlets were supposed to be run hosted in a Portlet server, so I don't really understand the need to publish all these servlets - they should be Portlets, and thus not visible from the application server perspective. Hopefully this will be sorted out as we near a production version, and the install gets a bit more streamlined 2)Default install on clean jakarta-tomcat-5.0.28 give me the following errors right off the bat when accessing the index page:: CNF: java.lang.ClassNotFoundException: org.apache.jetspeed.portlets.layout.MultiColumnPortlet:org.apache.jetspeed.portle ts.layout.MultiColumnPortlet 3)The My First PSML Page accesible off the main guest screen gives me an immediate : Invocation of method 'getCurrentPortletEntity' in class org.apache.jetspeed.velocity.JetspeedPowerTool threw exception class java.lang.NullPointerException : null org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getCurrentPortletEntity' in class org.apache.jetspeed.velocity.JetspeedPowerTool threw exception class java.lang.NullPointerException : null at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:193) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.jetspeed.velocity.JetspeedVelocityViewServlet.mergeTemplate(JetspeedVelocityViewServlet.java:116) at org.apache.velocity.tools.view.servlet.VelocityViewServlet.doRequest(VelocityViewServlet.java:455) at org.apache.velocity.tools.view.servlet.VelocityViewServlet.doGet(VelocityViewServlet.java:411) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Strangley the My Second PSML page works with no problems. 4) The Test Suite Page tab has errors in each prtlet window, all complaining :
Re: Some observations on jetspeed-2 (cont)
[EMAIL PROTECTED] wrote: 5)Logging in as user jetspeed with password jetspeed seems to work, but I am presented with a Manager Role Page titled window in which none of the tabs work. Although they appear to link correctly (for example to jetspeed/portal/p002.psml), the link itself always returns the default index page. 6)There is no way to log out of this non-functioning manager role page, since a)it probably won't work and b)no logout facility is provided. This is the CVS head that you are working with. Its ongoing development. This particular PSML page was checked in less than 24 hours ago. Why are you whining about works in progress as if they were bugs? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Some observations on jetspeed-2 (cont)
I fixed that this morning. Try updating from the CVS now and see if that resolves the issue for you. Michael Bowman wrote: Yup. I'm getting the same errors now (was working last week). Looks like there is a new (at least I haven't noticed it before) jar file Maven is trying to download... jetspeed-web-content-2.0-a1-dev.jar. Could this be the problem? Thanks, -Michael [EMAIL PROTECTED] wrote: Just to confirm, exact same problems with Tomcat 4.28. Tried running under Solaris, fails at the allBuild stage. Probably linked to the Apache site problems, but it's strange the Windows build doesn't fail then : java:prepare-filesystem: java:compile: [echo] Compiling to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] Compiling 35 source files to /local/user/Source/jakarta-jetspeed-2/commons/target/classes [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspeed/portlet/ServletContextProviderImpl.java:28: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: package common [javac] import org.apache.portals.bridges.common.ServletContextProvider; [javac] ^ [javac] /local/user/Source/jakarta-jetspeed-2/commons/src/java/org/apache/jetspeed/portlet/ServletContextProviderImpl.java:36: cannot resolve symbol [javac] symbol : class ServletContextProvider [javac] location: class org.apache.jetspeed.portlet.ServletContextProviderImpl [javac] public class ServletContextProviderImpl implements ServletContextProvider [javac]^ [javac] 2 errors BUILD FAILED File.. /local/user/Source/jakarta-jetspeed-2/maven.xml Element... maven:reactor Line.. 133 Column 40 Unable to obtain goal [java:compile] -- /local/user/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48: ant:javac Compile failed; see the compiler error output for details. Total time: 1 minutes 42 seconds Finished at: Fri Sep 24 14:59:10 CEST 2004 [EMAIL PROTECTED] wrote: Perhaps better suited for the developers list, but I didn't really want to subscribe there. Hopefully these comments will be of use to the developers in understanding from a user perspective some of the issues of the current development state of jetspeed-2. 1)Compared to jetspeed-1, the jetspeed-2 installation makes quite a mess of your application server, and pretty much renders it unusable for anything else you were planning to host in it. While jetspeed-1 had a lovely simple war file to drop in/out, jetspeed-2 installs roughly 10 seperate servlets, none of which can be uninstalled by any targets I found in the maven build file. I always understood portlets were supposed to be run hosted in a Portlet server, so I don't really understand the need to publish all these servlets - they should be Portlets, and thus not visible from the application server perspective. Hopefully this will be sorted out as we near a production version, and the install gets a bit more streamlined 2)Default install on clean jakarta-tomcat-5.0.28 give me the following errors right off the bat when accessing the index page:: CNF: java.lang.ClassNotFoundException: org.apache.jetspeed.portlets.layout.MultiColumnPortlet:org.apache.jetspeed.portle ts.layout.MultiColumnPortlet 3)The My First PSML Page accesible off the main guest screen gives me an immediate : Invocation of method 'getCurrentPortletEntity' in class org.apache.jetspeed.velocity.JetspeedPowerTool threw exception class java.lang.NullPointerException : null org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getCurrentPortletEntity' in class org.apache.jetspeed.velocity.JetspeedPowerTool threw exception class java.lang.NullPointerException : null at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:193) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.jetspeed.velocity.JetspeedVelocityViewServlet.mergeTemplate(JetspeedVelocityViewServlet.java:116) at org.apache.velocity.tools.view.servlet.VelocityViewServlet.doRequest(VelocityViewServlet.java:455) at org.apache.velocity.tools.view.servlet.VelocityViewServlet.doGet(VelocityViewServlet.java:411) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Strangley the My Second PSML page works with no problems. 4)
