You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by David Sean Taylor <da...@bluesunrise.com> on 2001/12/10 07:40:45 UTC
Jetspeed release 1.3a2 candidate
There is a 1.3a2 release candidate at
http://jakarta.apache.org/builds/jakarta-jetspeed/release/v1.3a2/
If you get a chance, please give it a try and let us know how it works for
you.
The documentation is updated at http://jakarta.apache.org/jetspeed
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by Michael Sallman <ms...@pro-ns.net>.
David & all,
Downloaded 1.3a2rc zip file. Unzipped file.
Deleted existing /jetspeed directory & jetspeed.war in $TOMCAT_HOME/webapps/
Copied new jetspeed.war (from zip file) to $TOMCAT_HOME/webapps
Started Tomcat. Went to http://localhost:8080/jetspeed/. Added new user. Logged in
as new user. Customized user layout & portlet selection. Logged out.
Everything seems to work just fine so far. Great work guys!
1 minor item:
The API link in left.vm takes you to http://jakarta.apache.org/jetspeed/api/ if
the javadocs are not installed.
Someone might want to take a look at updating the javadocs there or change the
API link to http://www.bluesunrise.com/jetspeed-docs/javadocs/ (Javadocs link on
jakarta site).
Again, great work.
Mike
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by PVBB Listreader <pv...@hotmail.com>.
Did u delete $TOMCAT_HOME/work ? Sometimes tomcat will reload from the
work dir, instead or reloading from the war.
>>Brendan
----- Original Message -----
From: "John Wooten" <jw...@ntplx.net>
To: "Jetspeed Users List" <je...@jakarta.apache.org>
Sent: Monday, December 10, 2001 11:57 AM
Subject: RE: Jetspeed release 1.3a2 candidate
> I did all that. I still get that error.
>
> -----Original Message-----
> From: Paul Spencer [mailto:paulsp@apache.org]
> Sent: Monday, December 10, 2001 11:44 AM
> To: Jetspeed Users List
> Subject: Re: Jetspeed release 1.3a2 candidate
>
>
> John,
>
> The installation instruction assume a new install. In the you case,
> i.e. an updated war file, search the mailing list,
> http://www.mail-archive.com. for instruction on applying an updated war
> file.
>
> In general the process is to:
> 1) stop tomcat
> 2) backup the existing webapps/jetspeed directory
> 3) delete the existing webapps/jetspeed directory
> 4) delete webapps/jetspeed.war
> 5) copy the new jetspeed.war to webapps/jetspeed.war
> 6) startup tomcat
>
> Paul Spencer
>
> John Wooten wrote:
>
> > Why does this keep getting released with a set of instructions that say,
> > drop the jetspeed war file into the tomcat webapps and then start the
> server
> > and it will work?
> >
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by Paul Spencer <pa...@apache.org>.
John,
It appears you are running JBoss, in which Tomcat 3.2.3 is embedded. I
believe their are some message in the mailing list involving configuring
JBoss to run Jetspeed.
Paul Spencer
John Wooten wrote:
> Now getting null pointer and page build error when I delete jetspeed
> folder and let it rebuild from the jetspeed.war.
> Horrible Exception: java.lang.NullPointerException
> at org.apache.jetspeed.util.AutoProfile.loadProfile(AutoProfile.java:37)
> at
> org.apache.jetspeed.modules.actions.controls.Customize.doPerform(Customize.j
> ava:115)
> at org.apache.turbine.modules.Action.perform(Action.java:87)
> 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:565)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> 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(Unknown Source)
>
>
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, December 10, 2001 4:27 PM
> To: Jetspeed Users List; jwooten@shoulderscorp.com
> Subject: Re: Jetspeed release 1.3a2 candidate
>
>
> Could you please send us a summary of:
>
> - operating system
>
>>>Windows 2000
>>>
> - jdk
>
>>>jdk1.3.0_02
>>>
> - app server
>
>>>JBoss(2.4.1) with Tomcat = version (3.2.3)
>>>
> - jetspeed version, size and date of war file
>
>>>version 1.3A2-release
>>>size 5670 KB
>>>date 12/9/2001, 9.58PM
>>>
> - jetspeed log
>
> - directory listing of webapps (taken with bash)
> total 3642
> drwxr-xr-x 6 0 everyone 0 Oct 17 14:59 ROOT
> -rw-r--r-- 1 0 everyone 1069309 Sep 14 12:10 ROOT.war
> drwxr-xr-x 5 0 everyone 0 Oct 17 14:59 admin
> -rw-r--r-- 1 0 everyone 7044 Sep 14 12:10 admin.war
> -rw-r--r-- 1 0 everyone 0 Dec 10 16:55 dir.lst
> drwxr-xr-x 7 0 everyone 0 Oct 17 14:59 examples
> -rw-r--r-- 1 0 everyone 122213 Sep 14 12:10 examples.war
> drwxr-xr-x 2 0 everyone 0 Dec 9 21:58
> jetspeed-1.3a2-release
> -rw-r--r-- 1 0 everyone 5805973 Dec 9 21:58 jetspeed.war
> drwxr-xr-x 5 0 everyone 0 Nov 9 09:50 soap
> -rw-r--r-- 1 0 everyone 359462 May 29 2001 soap.war
> drwxr-xr-x 8 0 everyone 0 Oct 17 14:59 test
> -rw-r--r-- 1 0 everyone 89570 Sep 14 12:10 test.war
>
> We can then better try to reproduce it.
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> ------------------------------------------------------------------------
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by John Wooten <jw...@ntplx.net>.
When I run jspeed, it expands the war file and creates a folder jetspeed.
I've removed the extra folder and retried. Same result.
The log file comes from the jetspeed folder under web-inf/logs
-----Original Message-----
From: David Sean Taylor [mailto:david@bluesunrise.com]
Sent: Monday, December 10, 2001 5:18 PM
To: Jetspeed Users List; jwooten@shoulderscorp.com
Subject: Re: Jetspeed release 1.3a2 candidate
>From looking at the directory, I didn't see where jetspeed.war was getting
expanded to a directory.
There should be a directory called 'jetspeed'
This directory should not be there:
drwxr-xr-x 2 0 everyone 0 Dec 9 21:58
jetspeed-1.3a2-release
Jetspeed will not run in an app.server that does not expand the war file to
the file system.
There are actually some app servers that do not expand war files, so you
cannot write to any resources in the war. From what I can tell, this is a
valid interpretation of the servlet spec.
Tomcat does not have this 'problem'. It expands the war file into a
directory automatically.
But I've never ran Tomcat+JBoss.
I will dl jboss tonight and see if we have any issues running on jboss
Just for a sanity check, you may try running Tomcat standalone without
JBoss, and see if that works
David
----- Original Message -----
From: "John Wooten" <jw...@ntplx.net>
To: "Jetspeed Users List" <je...@jakarta.apache.org>
Sent: Monday, December 10, 2001 2:02 PM
Subject: RE: Jetspeed release 1.3a2 candidate
> Now getting null pointer and page build error when I delete jetspeed
> folder and let it rebuild from the jetspeed.war.
> Horrible Exception: java.lang.NullPointerException
> at org.apache.jetspeed.util.AutoProfile.loadProfile(AutoProfile.java:37)
> at
>
org.apache.jetspeed.modules.actions.controls.Customize.doPerform(Customize.j
> ava:115)
> at org.apache.turbine.modules.Action.perform(Action.java:87)
> 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:565)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> 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(Unknown Source)
>
>
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, December 10, 2001 4:27 PM
> To: Jetspeed Users List; jwooten@shoulderscorp.com
> Subject: Re: Jetspeed release 1.3a2 candidate
>
>
> Could you please send us a summary of:
>
> - operating system
> >> Windows 2000
> - jdk
> >> jdk1.3.0_02
> - app server
> >> JBoss(2.4.1) with Tomcat = version (3.2.3)
> - jetspeed version, size and date of war file
> >> version 1.3A2-release
> >> size 5670 KB
> >> date 12/9/2001, 9.58PM
> - jetspeed log
>
> - directory listing of webapps (taken with bash)
> total 3642
> drwxr-xr-x 6 0 everyone 0 Oct 17 14:59 ROOT
> -rw-r--r-- 1 0 everyone 1069309 Sep 14 12:10 ROOT.war
> drwxr-xr-x 5 0 everyone 0 Oct 17 14:59 admin
> -rw-r--r-- 1 0 everyone 7044 Sep 14 12:10 admin.war
> -rw-r--r-- 1 0 everyone 0 Dec 10 16:55 dir.lst
> drwxr-xr-x 7 0 everyone 0 Oct 17 14:59 examples
> -rw-r--r-- 1 0 everyone 122213 Sep 14 12:10 examples.war
> drwxr-xr-x 2 0 everyone 0 Dec 9 21:58
> jetspeed-1.3a2-release
> -rw-r--r-- 1 0 everyone 5805973 Dec 9 21:58 jetspeed.war
> drwxr-xr-x 5 0 everyone 0 Nov 9 09:50 soap
> -rw-r--r-- 1 0 everyone 359462 May 29 2001 soap.war
> drwxr-xr-x 8 0 everyone 0 Oct 17 14:59 test
> -rw-r--r-- 1 0 everyone 89570 Sep 14 12:10 test.war
>
> We can then better try to reproduce it.
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by David Sean Taylor <da...@bluesunrise.com>.
>From looking at the directory, I didn't see where jetspeed.war was getting
expanded to a directory.
There should be a directory called 'jetspeed'
This directory should not be there:
drwxr-xr-x 2 0 everyone 0 Dec 9 21:58
jetspeed-1.3a2-release
Jetspeed will not run in an app.server that does not expand the war file to
the file system.
There are actually some app servers that do not expand war files, so you
cannot write to any resources in the war. From what I can tell, this is a
valid interpretation of the servlet spec.
Tomcat does not have this 'problem'. It expands the war file into a
directory automatically.
But I've never ran Tomcat+JBoss.
I will dl jboss tonight and see if we have any issues running on jboss
Just for a sanity check, you may try running Tomcat standalone without
JBoss, and see if that works
David
----- Original Message -----
From: "John Wooten" <jw...@ntplx.net>
To: "Jetspeed Users List" <je...@jakarta.apache.org>
Sent: Monday, December 10, 2001 2:02 PM
Subject: RE: Jetspeed release 1.3a2 candidate
> Now getting null pointer and page build error when I delete jetspeed
> folder and let it rebuild from the jetspeed.war.
> Horrible Exception: java.lang.NullPointerException
> at org.apache.jetspeed.util.AutoProfile.loadProfile(AutoProfile.java:37)
> at
>
org.apache.jetspeed.modules.actions.controls.Customize.doPerform(Customize.j
> ava:115)
> at org.apache.turbine.modules.Action.perform(Action.java:87)
> 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:565)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> 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(Unknown Source)
>
>
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, December 10, 2001 4:27 PM
> To: Jetspeed Users List; jwooten@shoulderscorp.com
> Subject: Re: Jetspeed release 1.3a2 candidate
>
>
> Could you please send us a summary of:
>
> - operating system
> >> Windows 2000
> - jdk
> >> jdk1.3.0_02
> - app server
> >> JBoss(2.4.1) with Tomcat = version (3.2.3)
> - jetspeed version, size and date of war file
> >> version 1.3A2-release
> >> size 5670 KB
> >> date 12/9/2001, 9.58PM
> - jetspeed log
>
> - directory listing of webapps (taken with bash)
> total 3642
> drwxr-xr-x 6 0 everyone 0 Oct 17 14:59 ROOT
> -rw-r--r-- 1 0 everyone 1069309 Sep 14 12:10 ROOT.war
> drwxr-xr-x 5 0 everyone 0 Oct 17 14:59 admin
> -rw-r--r-- 1 0 everyone 7044 Sep 14 12:10 admin.war
> -rw-r--r-- 1 0 everyone 0 Dec 10 16:55 dir.lst
> drwxr-xr-x 7 0 everyone 0 Oct 17 14:59 examples
> -rw-r--r-- 1 0 everyone 122213 Sep 14 12:10 examples.war
> drwxr-xr-x 2 0 everyone 0 Dec 9 21:58
> jetspeed-1.3a2-release
> -rw-r--r-- 1 0 everyone 5805973 Dec 9 21:58 jetspeed.war
> drwxr-xr-x 5 0 everyone 0 Nov 9 09:50 soap
> -rw-r--r-- 1 0 everyone 359462 May 29 2001 soap.war
> drwxr-xr-x 8 0 everyone 0 Oct 17 14:59 test
> -rw-r--r-- 1 0 everyone 89570 Sep 14 12:10 test.war
>
> We can then better try to reproduce it.
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by John Wooten <jw...@ntplx.net>.
Now getting null pointer and page build error when I delete jetspeed
folder and let it rebuild from the jetspeed.war.
Horrible Exception: java.lang.NullPointerException
at org.apache.jetspeed.util.AutoProfile.loadProfile(AutoProfile.java:37)
at
org.apache.jetspeed.modules.actions.controls.Customize.doPerform(Customize.j
ava:115)
at org.apache.turbine.modules.Action.perform(Action.java:87)
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:565)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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(Unknown Source)
-----Original Message-----
From: David Sean Taylor [mailto:david@bluesunrise.com]
Sent: Monday, December 10, 2001 4:27 PM
To: Jetspeed Users List; jwooten@shoulderscorp.com
Subject: Re: Jetspeed release 1.3a2 candidate
Could you please send us a summary of:
- operating system
>> Windows 2000
- jdk
>> jdk1.3.0_02
- app server
>> JBoss(2.4.1) with Tomcat = version (3.2.3)
- jetspeed version, size and date of war file
>> version 1.3A2-release
>> size 5670 KB
>> date 12/9/2001, 9.58PM
- jetspeed log
- directory listing of webapps (taken with bash)
total 3642
drwxr-xr-x 6 0 everyone 0 Oct 17 14:59 ROOT
-rw-r--r-- 1 0 everyone 1069309 Sep 14 12:10 ROOT.war
drwxr-xr-x 5 0 everyone 0 Oct 17 14:59 admin
-rw-r--r-- 1 0 everyone 7044 Sep 14 12:10 admin.war
-rw-r--r-- 1 0 everyone 0 Dec 10 16:55 dir.lst
drwxr-xr-x 7 0 everyone 0 Oct 17 14:59 examples
-rw-r--r-- 1 0 everyone 122213 Sep 14 12:10 examples.war
drwxr-xr-x 2 0 everyone 0 Dec 9 21:58
jetspeed-1.3a2-release
-rw-r--r-- 1 0 everyone 5805973 Dec 9 21:58 jetspeed.war
drwxr-xr-x 5 0 everyone 0 Nov 9 09:50 soap
-rw-r--r-- 1 0 everyone 359462 May 29 2001 soap.war
drwxr-xr-x 8 0 everyone 0 Oct 17 14:59 test
-rw-r--r-- 1 0 everyone 89570 Sep 14 12:10 test.war
We can then better try to reproduce it.
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by David Sean Taylor <da...@bluesunrise.com>.
Could you please send us a summary of:
- operating system
- jdk
- app server
- jetspeed version, size and date of war file
- jetspeed log
- directory listing of webapps
We can then better try to reproduce it.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by John Wooten <jw...@ntplx.net>.
I did all that. I still get that error.
-----Original Message-----
From: Paul Spencer [mailto:paulsp@apache.org]
Sent: Monday, December 10, 2001 11:44 AM
To: Jetspeed Users List
Subject: Re: Jetspeed release 1.3a2 candidate
John,
The installation instruction assume a new install. In the you case,
i.e. an updated war file, search the mailing list,
http://www.mail-archive.com. for instruction on applying an updated war
file.
In general the process is to:
1) stop tomcat
2) backup the existing webapps/jetspeed directory
3) delete the existing webapps/jetspeed directory
4) delete webapps/jetspeed.war
5) copy the new jetspeed.war to webapps/jetspeed.war
6) startup tomcat
Paul Spencer
John Wooten wrote:
> Why does this keep getting released with a set of instructions that say,
> drop the jetspeed war file into the tomcat webapps and then start the
server
> and it will work?
>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by Paul Spencer <pa...@apache.org>.
John,
The installation instruction assume a new install. In the you case,
i.e. an updated war file, search the mailing list,
http://www.mail-archive.com. for instruction on applying an updated war
file.
In general the process is to:
1) stop tomcat
2) backup the existing webapps/jetspeed directory
3) delete the existing webapps/jetspeed directory
4) delete webapps/jetspeed.war
5) copy the new jetspeed.war to webapps/jetspeed.war
6) startup tomcat
Paul Spencer
John Wooten wrote:
> Why does this keep getting released with a set of instructions that say,
> drop the jetspeed war file into the tomcat webapps and then start the server
> and it will work?
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by Frank Villarreal <fv...@directhitdata.com>.
John Wooten said:
>I need to run JBoss for ejbs, can't just run Tomcat alone.
>
>Anyone found a way to get Jetspeed to run with JBoss?
>
I'm not sure if this is an option for you ... but you could run Tomcat &
JBoss each in separate VMs (they can even be on the same physical machine)
... works for me ... I thought I read on a JBoss list that the integrated
stack still has issues with Tomcat 4 ... I could be completely off (too much
reading) :)
- Frank
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by John Wooten <jw...@ntplx.net>.
I checked in the tomcat and I have the latest xerces version and no crimson
or parser.jar. I also checked under JBoss and found that the run.bat
implicitly sets the parser factory to be a crimson factory rather than
xerces. I changed that to xerces and replaced crimson.jar with xerces.jar
and JBoss fails. There are several differences in tags that apparently
xerces handles differently than crimson.
I have the latest version of xerces anywhere that it might even be
referenced. Still same error. Apparently the conflict is in the way JBoss
sets up its parser factory and some dependencies on crimson.jar.
I need to run JBoss for ejbs, can't just run Tomcat alone.
Anyone found a way to get Jetspeed to run with JBoss?
-----Original Message-----
From: Santiago Gala [mailto:sgala@hisitech.com]
Sent: Wednesday, December 12, 2001 8:00 AM
To: Jetspeed Users List
Subject: Re: Jetspeed release 1.3a2 candidate
John Wooten wrote:
>Why does this keep getting released with a set of instructions that say,
>drop the jetspeed war file into the tomcat webapps and then start the
server
>and it will work?
>
>Once again, I did that.
>I then connected to Jetspeed via the browser, logged in as turbine,
turbine.
>Got logged in. Then chose Customize and got the same page as after logging
>in. NO CUSTOMIZATION.
>
You have an older jaxp parser (probably an older xerces version, or
crimson.jar or parser.jar) in your classpath, and it is used instead of
the JAXP version included in Jetspeed. Please clean your classpath of
older versions.
For tomcat 3.2.X the simplest way is to remove parser.jar from the
tomcat/lib directory, and put there a copy of the xerces.jar that comes
with jetspeed.
Until people migrates to tomcat 4, where classpath isolation effectively
works, this will be a nightmare. Not sure about 3.3
>
>LOG STILL READS:
>jetspeed.portalfactory - /WEB-INF/psml/default.psml
>[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Initializing the
PortletFactory
>[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Returning local cached URL
>[Mon Dec 10 09:50:12 EST 2001] -- ERROR --
> Exception: java.lang.AbstractMethodError
> Stack Trace follows:
> java.lang.AbstractMethodError
> at
>org.exolab.castor.xml.UnmarshalHandler.startElement(UnmarshalHandler.java:6
6
>3)
> at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1335)
> at
>org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValida
t
>or.java:840)
> at
>org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScann
e
>r.java:1852)
> at
>org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(X
M
>LDocumentScanner.java:1233)
> at
>org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner
.
>java:380)
> at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908)
> at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:335)
> at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:267)
> at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:388)
> at
>org.apache.jetspeed.xml.api.portletmarkup.Portlets.unmarshal(Portlets.java:
4
>52)
> at
>org.apache.jetspeed.portal.factory.PortletSetFactory.init(PortletSetFactory
.
>java:230)
>
>--------PLEASE NOTE. This was reported as a problem over a week ago. NO
>ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND. NEW RELEASE
STILL
>DOES EXACTLY THE SAME THING AS BEFORE>
>
>OBVIOUSLY THERE IS A SETUP PROBLEM. WHAT ELSE IS NECESSARY TO GET THIS TO
>WORK? IS THERE A PIECE OF INFORMATION MISSING? DOES SOMETHING ELSE NEED
TO
>BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE WEBAPPS AND IT WILL
>WORK?
>
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by Santiago Gala <sg...@hisitech.com>.
John Wooten wrote:
>Why does this keep getting released with a set of instructions that say,
>drop the jetspeed war file into the tomcat webapps and then start the server
>and it will work?
>
>Once again, I did that.
>I then connected to Jetspeed via the browser, logged in as turbine, turbine.
>Got logged in. Then chose Customize and got the same page as after logging
>in. NO CUSTOMIZATION.
>
You have an older jaxp parser (probably an older xerces version, or
crimson.jar or parser.jar) in your classpath, and it is used instead of
the JAXP version included in Jetspeed. Please clean your classpath of
older versions.
For tomcat 3.2.X the simplest way is to remove parser.jar from the
tomcat/lib directory, and put there a copy of the xerces.jar that comes
with jetspeed.
Until people migrates to tomcat 4, where classpath isolation effectively
works, this will be a nightmare. Not sure about 3.3
>
>LOG STILL READS:
>jetspeed.portalfactory - /WEB-INF/psml/default.psml
>[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Initializing the PortletFactory
>[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Returning local cached URL
>[Mon Dec 10 09:50:12 EST 2001] -- ERROR --
> Exception: java.lang.AbstractMethodError
> Stack Trace follows:
> java.lang.AbstractMethodError
> at
>org.exolab.castor.xml.UnmarshalHandler.startElement(UnmarshalHandler.java:66
>3)
> at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1335)
> at
>org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidat
>or.java:840)
> at
>org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
>r.java:1852)
> at
>org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
>LDocumentScanner.java:1233)
> at
>org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
>java:380)
> at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908)
> at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:335)
> at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:267)
> at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:388)
> at
>org.apache.jetspeed.xml.api.portletmarkup.Portlets.unmarshal(Portlets.java:4
>52)
> at
>org.apache.jetspeed.portal.factory.PortletSetFactory.init(PortletSetFactory.
>java:230)
>
>--------PLEASE NOTE. This was reported as a problem over a week ago. NO
>ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND. NEW RELEASE STILL
>DOES EXACTLY THE SAME THING AS BEFORE>
>
>OBVIOUSLY THERE IS A SETUP PROBLEM. WHAT ELSE IS NECESSARY TO GET THIS TO
>WORK? IS THERE A PIECE OF INFORMATION MISSING? DOES SOMETHING ELSE NEED TO
>BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE WEBAPPS AND IT WILL
>WORK?
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jetspeed release 1.3a2 candidate
Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/10/01 9:57 AM, "John Wooten" <jw...@ntplx.net> wrote:
> Why does this keep getting released with a set of instructions that say,
> drop the jetspeed war file into the tomcat webapps and then start the server
> and it will work?
>
> Once again, I did that.
> I then connected to Jetspeed via the browser, logged in as turbine, turbine.
> Got logged in. Then chose Customize and got the same page as after logging
> in. NO CUSTOMIZATION.
>
>
>
> --------PLEASE NOTE. This was reported as a problem over a week ago. NO
> ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND. NEW RELEASE STILL
> DOES EXACTLY THE SAME THING AS BEFORE>
Also note that you have the source as every other __volunteer__ who works on
the jetspeed project. Maybe you might actually consider lending a hand in
helping to find a solution instead of complaining in BOLD. David, Raphael,
Paul, Nacho and the rest of Jetspeed developers all volunteer their time to
help you and everyone else who uses Jetspeed. The releases may not be as
frequent or as well documented as you would like, but it is in your power to
fix this by helping.
> OBVIOUSLY THERE IS A SETUP PROBLEM. WHAT ELSE IS NECESSARY TO GET THIS TO
> WORK? IS THERE A PIECE OF INFORMATION MISSING? DOES SOMETHING ELSE NEED TO
> BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE WEBAPPS AND IT WILL
> WORK?
Maybe there is a disconnect between the users and developers but you as a
user who cannot get this to work are in an ideal situation to find out what
the problem is and document a solution. As often is the case the core
developers have setups that are tried and tested and can sometimes miss
things that are not at all obvious to inexperienced users. You can fix the
problem once and for all with a little digging, documenting and testing. If
you're not will to fix it why do you expect anyone else to? The core
developers of Jetspeed do what they can and need help when problems like
this arise.
> Inquiring minds really would like to join the in-crowd and get their setup
> so it will work like everyone else who apparently can run these releases.
Like I said it's in your power to fix the problem. Just because you report
the problem doesn't mean a solution is imminent. And it's not likely that
too many developers are going to go out of their way to help someone who
sends a somewhat accusatory messages to the list, even if borne out of
frustration. Trust me it won't get you very far and it certainly won't help
you garner any help from the people who actually work on the project.
>
>
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, December 10, 2001 1:41 AM
> To: 'Jetspeed Users List'
> Subject: Jetspeed release 1.3a2 candidate
>
>
> There is a 1.3a2 release candidate at
>
> http://jakarta.apache.org/builds/jakarta-jetspeed/release/v1.3a2/
>
> If you get a chance, please give it a try and let us know how it works for
> you.
>
> The documentation is updated at http://jakarta.apache.org/jetspeed
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by David Sean Taylor <da...@bluesunrise.com>.
This is what the javadocs say for a java.lang.AbstractMethodError:
<javadoc>
public class AbstractMethodError
extends IncompatibleClassChangeError
Thrown when an application tries to call an abstract method. Normally, this
error is caught by the compiler; this error can only occur at run time if
the definition of some class has incompatibly changed since the currently
executing method was last compiled.
</javadoc>
Sounds to me like you have an old version of Jetspeed or Turbine somewhere
in your classpath.
Looking at your previous message "Re: Who changed this?":
"I just did a search through all the files I received as a part of the
distribution including the configuration files for the alpha version. I
cannot find a newuser.confirm.enable=false ( or true )."
The newuser.confirm.enable feature has been a part of the cvs head for a
very long time, but I believe it wasn't in 1.3a1.
And then:
"3) I get an error when logging our or updating an account about a class
cast exception for BigNum."
Which I specifically remember as being a bug in 1.3a1..
Could it be possible that version 1.3a1 is somewhere in your classpath?
When you drop the jetspeed.war into your webapps directory, are you deleting
the old jetspeed directory from webapps?
> -----Original Message-----
> From: John Wooten [mailto:jwooten@ntplx.net]
> Sent: Monday, December 10, 2001 6:57 AM
> To: Jetspeed Users List
> Subject: RE: Jetspeed release 1.3a2 candidate
>
>
> Why does this keep getting released with a set of
> instructions that say,
> drop the jetspeed war file into the tomcat webapps and then
> start the server
> and it will work?
>
> Once again, I did that.
> I then connected to Jetspeed via the browser, logged in as
> turbine, turbine.
> Got logged in. Then chose Customize and got the same page as
> after logging
> in. NO CUSTOMIZATION.
>
> LOG STILL READS:
> jetspeed.portalfactory - /WEB-INF/psml/default.psml
> [Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Initializing the
> PortletFactory
> [Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Returning local
> cached URL
> [Mon Dec 10 09:50:12 EST 2001] -- ERROR --
> Exception: java.lang.AbstractMethodError
> Stack Trace follows:
> java.lang.AbstractMethodError
> at
> org.exolab.castor.xml.UnmarshalHandler.startElement(UnmarshalH
> andler.java:66
> 3)
> at
> org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1335)
> at
> org.apache.xerces.validators.common.XMLValidator.callStartElem
> ent(XMLValidat
> or.java:840)
> at
> org.apache.xerces.framework.XMLDocumentScanner.scanElement(XML
> DocumentScanne
> r.java:1852)
> at
> org.apache.xerces.framework.XMLDocumentScanner$ContentDispatch
> er.dispatch(XM
> LDocumentScanner.java:1233)
> at
> org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDo
> cumentScanner.
> java:380)
> at
> org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908)
> at
> org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:335)
> at
> org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:267)
> at
> org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:388)
> at
> org.apache.jetspeed.xml.api.portletmarkup.Portlets.unmarshal(P
> ortlets.java:4
> 52)
> at
> org.apache.jetspeed.portal.factory.PortletSetFactory.init(Port
> letSetFactory.
> java:230)
>
> --------PLEASE NOTE. This was reported as a problem over a
> week ago. NO
> ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND.
> NEW RELEASE STILL
> DOES EXACTLY THE SAME THING AS BEFORE>
>
> OBVIOUSLY THERE IS A SETUP PROBLEM. WHAT ELSE IS NECESSARY
> TO GET THIS TO
> WORK? IS THERE A PIECE OF INFORMATION MISSING? DOES
> SOMETHING ELSE NEED TO
> BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE
> WEBAPPS AND IT WILL
> WORK?
>
> Inquiring minds really would like to join the in-crowd and
> get their setup
> so it will work like everyone else who apparently can run
> these releases.
>
>
>
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, December 10, 2001 1:41 AM
> To: 'Jetspeed Users List'
> Subject: Jetspeed release 1.3a2 candidate
>
>
> There is a 1.3a2 release candidate at
>
> http://jakarta.apache.org/builds/jakarta-jetspeed/release/v1.3a2/
>
> If you get a chance, please give it a try and let us know how
> it works for
> you.
>
> The documentation is updated at http://jakarta.apache.org/jetspeed
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by John Wooten <jw...@ntplx.net>.
Why does this keep getting released with a set of instructions that say,
drop the jetspeed war file into the tomcat webapps and then start the server
and it will work?
Once again, I did that.
I then connected to Jetspeed via the browser, logged in as turbine, turbine.
Got logged in. Then chose Customize and got the same page as after logging
in. NO CUSTOMIZATION.
LOG STILL READS:
jetspeed.portalfactory - /WEB-INF/psml/default.psml
[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Initializing the PortletFactory
[Mon Dec 10 09:50:12 EST 2001] -- NOTICE -- Returning local cached URL
[Mon Dec 10 09:50:12 EST 2001] -- ERROR --
Exception: java.lang.AbstractMethodError
Stack Trace follows:
java.lang.AbstractMethodError
at
org.exolab.castor.xml.UnmarshalHandler.startElement(UnmarshalHandler.java:66
3)
at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1335)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidat
or.java:840)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
r.java:1852)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1233)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:380)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:908)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:335)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:267)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:388)
at
org.apache.jetspeed.xml.api.portletmarkup.Portlets.unmarshal(Portlets.java:4
52)
at
org.apache.jetspeed.portal.factory.PortletSetFactory.init(PortletSetFactory.
java:230)
--------PLEASE NOTE. This was reported as a problem over a week ago. NO
ANSWER AS TO HOW TO FIX, WHERE TO LOOK, OR A WORK AROUND. NEW RELEASE STILL
DOES EXACTLY THE SAME THING AS BEFORE>
OBVIOUSLY THERE IS A SETUP PROBLEM. WHAT ELSE IS NECESSARY TO GET THIS TO
WORK? IS THERE A PIECE OF INFORMATION MISSING? DOES SOMETHING ELSE NEED TO
BE INSTALLED OTHER THAN JUST DROP THE WARFILE INTO THE WEBAPPS AND IT WILL
WORK?
Inquiring minds really would like to join the in-crowd and get their setup
so it will work like everyone else who apparently can run these releases.
-----Original Message-----
From: David Sean Taylor [mailto:david@bluesunrise.com]
Sent: Monday, December 10, 2001 1:41 AM
To: 'Jetspeed Users List'
Subject: Jetspeed release 1.3a2 candidate
There is a 1.3a2 release candidate at
http://jakarta.apache.org/builds/jakarta-jetspeed/release/v1.3a2/
If you get a chance, please give it a try and let us know how it works for
you.
The documentation is updated at http://jakarta.apache.org/jetspeed
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Jetspeed release 1.3a2 candidate
Posted by Ed Knutson <ed...@barkingcat.org>.
Hi everyone,
I worked with Jetspeed for a while a year or two ago, and let me say
first that I am very impressed with the progress the project has made.
However, there seems to be a problem with some of the configuration
files. On installing a fresh copy of the new version, I got the
following error (environment is Linux, Sun JDK 1.3.1, Tomcat 3.2.2):
Horrible Exception: java.lang.NullPointerException
at
org.apache.velocity.runtime.log.AvalonLogSystem.logVelocityMessage(Avalo
nLogSystem.java)
at org.apache.velocity.runtime.Runtime.log(Runtime.java)
at org.apache.velocity.runtime.Runtime.error(Runtime.java)
at
org.apache.velocity.runtime.resource.ResourceManager.getResource(Resourc
eManager.java)
at org.apache.velocity.runtime.Runtime.getTemplate(Runtime.java)
at org.apache.velocity.app.Velocity.mergeTemplate(Velocity.java)
at org.apache.velocity.app.Velocity.mergeTemplate(Velocity.java)
rethrown as org.apache.turbine.util.TurbineException: Error rendering
Velocity template: layouts/html/default.vm
....
NOTE:
I was able to remedy the error by changing all instances of "=/WEB-INF"
to "=WEB-INF" in WEB-INF/conf/TurbineResources.* and
WEB-INF/conf/JetspeedResources.properties. That may have been more than
necessary. I was hoping just editing the velocity file would be enough,
and I actually saved the *.url properties in
JetspeedResources.properties for last, and it did not work until I
changed those, too. Does this sound like a Jetspeed problem? Apologies
if this was discussed before I joined the list.
Ed Knutson
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>