I have had no troubles with the a CVS May 17 download of Jetspeed1.4b5dev with SUN's JDK1.4.1_03 and Tomcat4.1.24. However, there was a Jetspeed bug fix for an extra xercesImpl in the WEB-INF/lib. See if it is in your version and remove the redundant xercesImpl.
We are running tomcat4.1.24 LE. Are you running the full tomcat4.1.24? Also, make sure you are using the tomcat4.1.24 for JDK1.4.
That is about I can say to help you out. It is worth the effort to find the problem and start running JDK1.4.
Good luck, Glen
Mike Davis wrote:
Hi Glen,
Yes, I did follow the instructions. However, I
was using (JDK) 1.4.1. I just switched back to 1.3.1
and everything seems to be working. The instructions
are slightly out of date (no castor.jar in
$JBOSS_HOME/server/default/lib for instance), but no
matter...
Do you know if Jetspeed 1.4B5dev is supported "out of the box" under JDK 1.4.1 and Tomcat 4.1.24?
It appears to me that it is not. I figured out that it was a Tomcat/Jetspeed problem, not a JBoss problem. I was running Tomcat 4.1.18 under JDK 1.4.1 with no problems. Then just as a test, I installed Tomcat 4.1.24 and poof, the same exact problem popped-up, no JBoss involved. I then back-dated to JDK 1.3.1 and the problem disappeared. I took a quick scan in the mail list archives, but I couldn't find anything directly applicable. Anyways, I guess I will stick with JDK 1.3.1 until further notice.
Thanks, Mike
--- Glen Carl <[EMAIL PROTECTED]> wrote:
Yesterday, I set up our Jetspeed-based portal on/layouts/html/default.jsporg.apache.jasper.JasperException
JBoss3.2 w/Tomcat and followed the instructions at
<http://www.shiftat.com/blog/page/werner/20021027>
I did have a JasperException before following the
instructions. Did you try the werner instructions?
I think there are some of us that would like to see
some formalized instructions for JBoss set up. Right now, all I know is from the
werner site. We are also using the Apache HTTP Client
commons-httpclient-2.0-beta1.jar vs the default commons-httpclient.jar that comes with JBoss and
Jetspeed. To get this to work, I needed to remove the default httpclients from
Jboss/lib and of course the jetspeed/WEB-INF/lib.
Glen
Mike Davis wrote:
Hi, I tried using the latest JBoss/Tomcat
integration
(jboss-3.2.1_tomcat-4.1.24.zip). I followed the instructions as best I could, but they are clearly
out
of date for this latest version of Jboss/Tomcat.
I am
using a latest code of Jetspeed extracted from CVS about 1 week ago. I can see from the JBoss STDOUT that the jetspeed servlet seems to load
successfully.
When I access it, it loads the top and left
area's,
but the "main" part of the page pukes with a
Jasper
exception:
Error encountered processing a template:
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)at
=== message truncated ===at ...... (and so on) .....
Any idea of which jar that Jasper lives in under JBoss? Maybe the list of jar's to be removed from
Jboss/lib
simply needs to be updated. I will share any
useful
results...
Thanks!
--- Mark Orciuch <[EMAIL PROTECTED]> wrote:
Check out README from CVS - it has a section on JBoss integration.
Best regards,
Mark Orciuch - [EMAIL PROTECTED] Jakarta Jetspeed - Enterprise Portal in Java http://jakarta.apache.org/jetspeed/
-----Original Message----- From: Andy Benjamin
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 8:39 PM To: [EMAIL PROTECTED] Subject: Re: Jetspeed Best Practices
Can anyone go into more detail about exactly how
ejbs are being accessed
from inside the jetspeed environment? Is there a
design pattern that has
proven to work/not work well with Jetspeed? I
understand how to
access them directly from a jsp but wanted to see if there
was
a cleaner
design approach as this seems to bypass the separation of
presentation/business
logic/data, etc.
Also, did anyone get jetspeed to run on the
Jboss/Tomcat bundle?
I posted a couple days ago and haven't heard any response on
how we can get
Jetspeed to run in that environment.
Any good advice on proper DB access in a clean
design pattern
would be most helpful. Thanks!!
Andy
I can give a little bit of feedback because our
situation is similar.
1- basic portlet that get data from a database. We do mostly what you propose; often used db
objects or objects shared
between multiple "applications" are kept in the session,
but smaller,
simpler apps usually just go to the db for each call. We use EJBs for
all db access.
2- Multiple Application portal. We use role based security and role based psml;
the presence of
a role or permission grants you access to a particular application or
part of one. Our
applications are organized into tabs. Basic tabs are level 1; For
Visitors, For Staff,
etc... Under each of those tabs is another application
specific
tab. For
example under staff we might have the Intranet tab that has a portlet or
two, the Paging
tab which has the paging application portlet, and whatever other
apps the Staff role has
access to.
3- Extending Jetspeed users. We extended the base jetspeed user quite a bit
and
restrict
access to what
__________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
--------------------------------------------------------------------- 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]
