Some observations on jetspeed-2

2004-09-24 Thread [EMAIL PROTECTED]
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: 
org.apache.jetspeed.components.portletentity.PortletEntityNotGeneratedException: 
Failed to retrieve Portlet Definition for testsuite::TestPortlet1
at 
org.apache.jetspeed.aggregator.impl.PortletRendererImpl.renderNow(PortletRendererImpl.java:172)
at 
org.apache.jetspeed.aggregator.impl.ContentDispatcherImpl.include(ContentDispatcherImpl.java:286)
at 
org.apache.jetspeed.velocity.JetspeedPowerTool.include(JetspeedPowerTool.java:552)

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.

I'm now going to repeat the process using Tomcat 4.28 and see what happens.
Thanks
wh


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


psml reference using portlet

2004-09-24 Thread Dimitris Avramidis
Hello everybody!
Due to some limitations in our application we would like to have an 
alternative way to have psml references in a pane.

Is it feasible to create a reference-portlet, such that it takes as 
init parameter the psml to be referenced, and place it in the desired pane?

Any ideas/help is welcome!
Thanks,
  Dimitris Avramidis.-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Some observations on jetspeed-2 (cont)

2004-09-24 Thread [EMAIL PROTECTED]
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)

2004-09-24 Thread Randy Watler
 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

2004-09-24 Thread Scott T. Weaver
[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.
Please define mess.  There are six jars (two of which are optional) 
that are copied to the shared/lib directory.  Not a single one of these 
should conflict with any other jars since they are all part of the 
Jetspeed project.  The only other modification is copying the 
jetspeed.xml to con/Catalina/local host, which defines the DS we use for 
our registry.  The only other thing I can think of is in Tomcat 5.x 
there was a modification to JAAS that breaks any other app trying to use 
their own JAAS implementation, so in this case we copy so patched 
classes to  server/classes to fix this.

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.  
The base build of Jetspeed 2 installs example portlets.  If you do not 
want a portlet, delete its application war from WEB-INF/deploy and it 
will be undeployed from Jetspeed 2 AND Tomcat.

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.
All portlet applications MUST also be available as web applications, 
this is a requirement of the JSR-168 hence the reason for each portlet 
application also being a deployed as web application.  I think you 
should read the spec, especially PLT 3.1 and more specifically PLT 3.2 
which says a portlet container environment must fully support the 
Servlet 2.3 spec.  You should really do more research before you start 
criticizing a project.  Building an application server that lives inside 
another is no easy task, multiply that by our goal of being able to run 
Jetspeed 2 inside any servlet container.  This is why J2 is relatively 
more complicated when compared to J1.

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)
This is probably due the failure to deploy the multicolumn portlet.  I 
will need to install tomcat 5.0.28 to see if it is a version conflict or 
just an issue with your specific environment.


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)

2004-09-24 Thread [EMAIL PROTECTED]
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)

2004-09-24 Thread Michael Bowman
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)

2004-09-24 Thread David Sean Taylor
[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)

2004-09-24 Thread Scott T. Weaver
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) 

Re: I surrender!

2004-09-24 Thread Scott T. Weaver
looks like something was being built that should not have been.  
null:null-.pom is a valid linux filename but must not be a valid windows 
one because I was not encountering the same error.

The apache cvs seems to be down right now, so I have inlcuded the change 
you need to make in /maven.xml.  Locate the jetspeed2:jar:install goal 
and replace it with what I have included below.

goal name =jetspeed2:jar:install
   maven:reactor
  basedir=${basedir}
  
includes=commons/project.xml,cps/project.xml,content-server/project.xml,jetspeed-api/project.xml,portal-bridges/project.xml,portal/project.xml,components/**/project.xml
  
excludes=/project.xml,maven-plugin/**,cornerstone-jmx/**,cornerstone-jmx-demo/**,layout-portlets/**,applications/**,applications/**/**,site/project.xml,design-docs/project.xml,
  goals=jar:install
  banner=Build and Install all Jetspeed 2 jars
  postProcessing=false
  ignoreFailures=false/
 /goal

[EMAIL PROTECTED] wrote:
I updated again, but still seems to be missing some stuff :
BUILD FAILED
File.. C:\Source\jakarta-jetspeed-2\maven.xml
Element... maven:reactor
Line.. 133
Column 40
Unable to obtain goal [jar:install] -- C:\Documents and 
Settings\skruger\.maven\cache\maven-jar-plugin-1.6\plugin.jelly:255:7: 
artifact:install Cann
ot install file: 
'C:\Source\jakarta-jetspeed-2\site\xdocs\stylesheets\project.xml'. 
Reason: Failed to copy full contents from C:\Source\jakarta-jetspe
ed-2\site\xdocs\stylesheets\project.xml to C:\Documents and 
Settings\user\.maven\repository\null\poms\null:null-.pom
Total time: 2 minutes 14 seconds
Finished at: Thu Sep 23 16:53:10 CEST 2004


Scott T. Weaver wrote:
Fixed.  Just update the root level maven.xml as it is the only file I 
changed.

Scott T. Weaver wrote:
It is broken for me also.  Give me ten miniutes to see if Ican get 
it fixed.

[EMAIL PROTECTED] wrote:
Just got some more time to spend on this.
I'm trying a fresh install of everything - re-installed :
Java (1.4.2_05-b04)
Ant (1.6.2)
Maven (1.0)
Tomcat  (jakarta-tomcat-5.0.28)
Jetspeed (cvs head copy)
Currently the Jetspeed build fails trying to download some 
dependancies :

Jetspeed-2 Demo Portlet Application
+
| Build and Install the Demo application WAR Jetspeed-2 Demo 
Portlet Application
| Memory: 57M/70M
+
Attempting to download jetspeed-web-content-2.0-a1-dev.jar.
Response content length is not known
Response content length is not known
WARNING: Failed to download jetspeed-web-content-2.0-a1-dev.jar.

BUILD FAILED
File.. C:\Source\jakarta-jetspeed-2\maven.xml
Element... maven:reactor
Line.. 308
Column 40
The build cannot continue because of the following unsatisfied 
dependency:

jetspeed-web-content-2.0-a1-dev.jar
I assume this is a file Maven is trying to download off some 
backend server which is missing?
I know maven is correctly configured through our proxy, cos it 
managed o download quite a bit of other stuff, but when I run the 
allClean allBuild goal he complains all the plugins are not 
available. (e.g. Plugin 'maven-deploy-plugin' in project 
'Jetspeed-2 Page Manager' is not available) Perhaps some repository 
at Apache is down?

wh
maven -o -Dmaven.test.skip=true allClean allBuild quickStart 
should put it down to around a minute or two.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Great minds discuss ideas. Average minds discuss events. Small minds discuss people. 
 - Admiral Hyman Rickover
***
*   Scott T. Weaver   *
* [EMAIL PROTECTED] *
* http://www.einnovation.com*
* --  *
*   Apache Jetspeed Enterprise Portal *
* Apache Pluto Portlet Container  *
* *
* OpenEditPro, Website Content Management *
* http://www.openeditpro.com*
***
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Issues of value passing

2004-09-24 Thread #HO QUOC THUAN#
Hi,

I have two question about value passing.


(1) I have a dynamic array of checkboxes specified in jetspeed template.
How can their values be passed (checked or unchecked) to the server?

For example, 
#foreach ($file in $flist)
input type=checkbox name=$file.name value=$file.state
$file.state/
#end

At the server, a Vector of files is used. Each element is the vector is
a record of file attributes. This way, $file.name and $file.state are
displayed correctly. 

Is there any way to capture check box state (CHECKED or UNCHECKED)?

If I specify: 
input type=checkbox name=$file.name value=$file.state
!$file.state/

What should be done at the servlet (such as file.state =
rundata.getParameters().) ? 

(2) How can a variable's value in javascript be passed to one variable
specified in vm template? Following is my try but it failed, $list value
captured is a string of javascript:geta();. Do you have any
suggestion?

script ...
var a;
function geta()
{
return a;
}
/script

#set( $list =  javascript:geta();)




Thank you,

_thuan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]