In answer to your questions,
1) The first time you visit jetspeed, the index.jsp needs to be compiled. Also, there might be some initial startup costs, but in my experience, it only took seconds.
2) All the index.jsp file does is forward you to the url http://localhost:8080/jetspeed/portal. If you look at the web.xml, you will see that portal is the url mapping that jetspeed uses.
3) I think I've seen this error in relation to JDK 1.4.2. Try a different JDK perhaps. Also, you might try replacing the xalan jar that is shipped with JDK1.4.2.
Jeremy Ford
From: Zufeng Huang <[EMAIL PROTECTED]> Reply-To: "Jetspeed Users List" <[EMAIL PROTECTED]> To: Jetspeed Users List <[EMAIL PROTECTED]> Subject: Re: God, jetspeed from cvs is too slow. Date: Fri, 25 Jul 2003 10:53:47 -0400
Mike,
I am a newbie to jetspeed and portlet, I just restore jetspeed to standard WAR(1.4-b4), not the one I compiled(1.4-b5-dev).
but it seems that it has some problems.
As I remember, except the first time to visit http://localhost:8080/jetspeed/ will cost some time -- about 3~5 minutes -- then it
becomes fast to access other pages or re-access http://localhost:8080/jetspeed/. But now, each time I access the page(http://localhost:8080/jetspeed/),
it will cost several minutes.
And my questions are:
1. How much time cost to get response from http://localhost:8080/jetspeed/ at the first?
how about refresh the page?
2. Can you explain <jsp:forward page="portal/"/> in the /jetspeed/index.jsp for me?
I want to find out what operations are performed when access the page, but I didn't find the directory or file named portal.
3. There is a error message on the page as below:
Jetspeed Documentation
problem in SAX transform: org.apache.xml.utils.WrappedRuntimeException: The output format must have a '{http://xml.apache.org/xalan}content-handler' property!
and sometimes there are some other alike error messages, how to solve such errors?
thanks,
Zufeng,
I'm not convinced that it has to be the Jetspeed code that is causing delays.
Are you using the Stock Quote portlet? It can be a performance killer. Perhaps some other portlet is taking a long time to render?
Mike
--------------------------------------------------------------------- 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]
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
