I have installed jetspeed-2 M1 on Tomcat 5.0.30 and finally got it
working (after buggering around with Java SDK's and Tomcat 5.5) but have
a question.
When the welcome page appears, the login portlet and locale selector
portlet are both empty. In particular the login portlet being empty
Hi Craig,
Start up J2. Try going into the ${j2-webapp}/WEB-INF/deploy directory and
cut the security.war file out of there. Wait for a few seconds, and watch
the logging statements as jetspeed undeploys the application. After
successful undeployment, paste the security.war file back into the
The portlet application corresponding at the Login portlet is security.war
Have you an error trace when you try to access to the login portlet ?
best regards
Jabouille Jean Charles
- Original Message -
From: Craig McDonald [EMAIL PROTECTED]
To: Jetspeed Users List
FYI J2 Developers:
I wanted to deploy a new portlet in Jetspeed2 and took the following steps:
1) deployed the portlet war (worked)
2) made changes to my PSML in order to place my new portlet in an existing
page by overwriting a previous fragment
My portlet displays fine except for the title
On Thu, 24 Feb 2005 23:10:48 -0500, Craig Doremus [EMAIL PROTECTED] wrote:
Hi,
This is somewhat off topic, but of interest to us in 'portal-land': Are
you working on making Tapestry JSR-168 compatible? If not, do you have
plans to move in this direction?
That's exactly what I'm working on
Thank you, Hema!
Yes, that was it - the default name had to be set to
'mysql'.
Once I did that, the build script finished all DB
setup work fine but it failed at a later point:
java:compile:
[echo] Compiling to
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\portlet-api/target/classes
Christophe,
Here's my html:
%@ page session=false %
%@ page import=javax.portlet.*%
%@ page import=java.util.*%
%@ taglib uri='/WEB-INF/tld/portlet.tld' prefix='portlet'%
portlet:defineObjects/
form action=portlet:actionURL/ enctype=multipart/form-data
method=post
input type=file name=foo/br
Frank,
Try using a new fragment id. JS2 does cache certain portlet info per
fragment ids... a long standing issue for sure. Many of us are simply in
the habit of generating new ids for edited pages and fragments when
manually editing PSML.
Randy
FYI J2 Developers:
I wanted to deploy a new
Craig,
I have seen this problem with the login portlet when the security.xml
context descriptor is not deployed correctly. Please make sure that it is
located in conf/Catalina/localhost. If everything is in place, you might
need to try restarting tomcat several times and waiting for the
Marina,
These settings have always worked for me, (note that I do not set the
ojb.platform property):
org.apache.jetspeed.test.jdbc.drivers.path=${org.apache.jetspeed.server.shared}/mysql-connector-java-3.0.16.jar
org.apache.jetspeed.test.database.default.name=mysql
10 matches
Mail list logo