JS2 login portlet empty
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 isn't very helpful because then I can't login to Jetspeed and play around with it's customisation and personalisation tools. For info, in the WEB-INF/deploy directory there doesn't seem to be any war specifically for login or locale - the directory listing is: demo.war; jetspeed-layouts.war; jsf-demo.war; pam.war; perl.war; php.war; rss.war; security.war; struts-demo.war; All other portlets display fine - any help would be appreciated. Cheers, Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JS2 login portlet 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
deploy directory ... once again, watch the logging statements as jetspeed
(re)deploys the application. Refresh your portal page and you should see
the previously missing portlet. I found I had to perform this routine with
several different portlets that kept disappearing. It seems occasionally
J2's application database gets corrupted and this procedure is required. I
have yet to identify how this corruption takes place ... heck, I might be
the cause ;-)
- Frank
-Original Message-
From: Craig McDonald [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 24, 2005 05:17 PM
To: Jetspeed Users List
Subject: JS2 login portlet empty
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
isn't very helpful because then I can't login to Jetspeed and play
around with it's customisation and personalisation tools.
For info, in the WEB-INF/deploy directory there doesn't seem to be any
war specifically for login or locale - the directory listing is:
demo.war;
jetspeed-layouts.war;
jsf-demo.war;
pam.war;
perl.war;
php.war;
rss.war;
security.war;
struts-demo.war;
All other portlets display fine - any help would be appreciated.
Cheers,
Craig
-
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]
Re: JS2 login portlet empty
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 jetspeed-user@jakarta.apache.org Sent: Friday, February 25, 2005 12:16 AM Subject: JS2 login portlet empty 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 isn't very helpful because then I can't login to Jetspeed and play around with it's customisation and personalisation tools. For info, in the WEB-INF/deploy directory there doesn't seem to be any war specifically for login or locale - the directory listing is: demo.war; jetspeed-layouts.war; jsf-demo.war; pam.war; perl.war; php.war; rss.war; security.war; struts-demo.war; All other portlets display fine - any help would be appreciated. Cheers, Craig - 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]
Corrupt Fragment Info
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 ... I'm seeing some strange behavior, the following line of velocity code (taken from a portlet decorator) returns the overwritten fragment's previous portlet title instead of the title from my new fragment(portlet) ... $!jetspeed.getTitle($myPE, $myF) All my new portlet's deployment info is correct, J2 appears to be caching the previous fragment's title somewhere. Anyone know where I can clear this? I can't seem to find it in the database. Where do fragments/portlet entities get cached? Is it outside the database? - Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Force restart/reload
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 right now. Tapestry 3.1 will have an add-on library that turns Tapestry into a natively portlet compliant framework. I'm introducing a number of abstractions to deal with the differences -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: using MySQL with J2 - setup problem
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
[echo]
==
NOTE: Targetting JVM 1.4, classes
will not run on earlier JVMs
==
[javac] Compiling 27 source files to
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\portlet-api\target\classes
BUILD FAILED
File..
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\maven.xml
Element... maven:reactor
Line.. 133
Column 40
Unable to obtain goal [java:compile] --
C:\Marina\MyWork\Maven\cache\maven-java-plugin-1.5\plugin.jelly:63:48:
ant:javac Error running javac.exe compiler
Total time: 37 seconds
Finished at: Fri Feb 25 19:23:20 EST 2005
Any idea what is wrong now?
Thank you!
Marina
--- Hema Menon [EMAIL PROTECTED] wrote:
Marina,
What I meant to say is that, I believe the default
name should be the
type of database name, so in your build script it
should be mysql
instead of j2 and j2test. If you look at the sample
build properties,
it contains hsql for both test and production
default database name.
org.apache.jetspeed.test.database.default.name=hsql
org.apache.jetspeed.test.database.ojb.platform=Hsqldb
Hema
On Thu, 24 Feb 2005 18:37:18 -0800 (PST), Marina
[EMAIL PROTECTED] wrote:
Hi,
I finally got around to switch from HSQLDB to
MySQL
and ran into a build problem.
I setup MySQL DB schema and users per J2
instructions
(created 'j2test' and 'j2' schemas and the
'jetspeed2'
user that has all writes for those schemas). I
have
also modified J2's build.properties to use MySQL
(I'm
including a snippet below).
After that, I do the following:
1. start MySQL DB
2. cd [EMAIL PROTECTED]
maven allClean - OK
maven allBuild - Error:
Attempting to download
maven-torque-plugin-3.2.jar.
2/6K
6/6K
6K downloaded
build:start:
allBuild:
check.required.properties:
torque:init:
db.scripts.gen:
[echo] Generating SQL schema creation
scripts for
HSQLDB
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\hsql\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
MySQL
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\mysql\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
Oracle
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\oracle\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
MS SQL
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\mssql\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
Postgres
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\postgres\report.portal.sql.generation
BUILD FAILED
File..
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\maven.xml
Element... sql
Line.. 355
Column 39
Source file does not exist!
Total time: 12 seconds
Finished at: Thu Feb 24 21:27:54 EST 2005
Here is my build.properties (relevant parts):
# Override the database connection and
driverproperties in your
${USER_HOME}/build.properties
appropriately
# See:
#
http://portals.apache.org/jetspeed-2/database.html
org.apache.jetspeed.test.database.url =
jdbc:mysql://localhost/j2test
org.apache.jetspeed.test.database.driver =
com.mysql.jdbc.Driver
org.apache.jetspeed.test.database.user =
jetspeed2
org.apache.jetspeed.test.database.password =
jetspeed2
org.apache.jetspeed.test.jdbc.drivers.path=C:/Marina/MySQL/mysql-connector-java-3.0.16-ga/mysql-connector-java-3.0.16-ga-bin.jar
org.apache.jetspeed.test.database.default.name=j2test
org.apache.jetspeed.test.database.ojb.platform=mysql
org.apache.jetspeed.production.database.url =
jdbc:mysql://localhost/j2
org.apache.jetspeed.production.database.driver =
com.mysql.jdbc.Driver
org.apache.jetspeed.production.database.user =
jetspeed2
org.apache.jetspeed.production.database.password
=
jetspeed2
org.apache.jetspeed.production.jdbc.drivers.path=C:/Marina/MySQL/mysql-connector-java-3.0.16-ga/mysql-connector-java-3.0.16-ga-bin.jar
RE: File upload using commons fileuploader not working
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
input name=method type=submit value=Submit/
/formbr
Thanks,
Nik
-Original Message-
From: Christophe Lombart
[mailto:[EMAIL PROTECTED]
Sent: Friday, February 25, 2005 6:32 AM
To: Jetspeed Users List
Subject: Re: File upload using commons fileuploader not working
I'm using the same component in Graffito and it works with Jetspeed 2.
Your code seems correct. Maybe an issue in the html form.
Christophe
nik gonzalez wrote:
By the way, its a JSR 168 portlet that i deployed in Fusion.
Thanks,
Nik
-Original Message-
From: nik gonzalez [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 5:05 PM
To: jetspeed-user@jakarta.apache.org
Subject: File upload using commons fileuploader not working
Hello,
I ran the following code in my portlet.
PortletFileUpload dfu = new PortletFileUpload();
//get the FileItems
List fileItems = dfu.parseRequest(request);
Iterator iter = fileItems.iterator();
while (iter.hasNext())
{
FileItem item = (FileItem) iter.next();
if (item.isFormField())
{
//pass along to render request
String fieldName = item.getFieldName();
String value = item.getString();
response.setRenderParameter(fieldName, value);
}
else
{
//write the uploaded file to a new location
String fieldName = item.getFieldName();
String fileName = item.getName();
String contentType = item.getContentType();
long size = item.getSize();
response.setRenderParameter(size,
Long.toString(size));
response.setRenderParameter(contentType, contentType);
String tempDir =
System.getProperty(java.io.tmpdir);
System.out.println(tempDir: +tempDir);
String serverFileName = fieldName +
-portlet.tmp;
File serverFile = new File(tempDir,
serverFileName);
item.write(serverFile);
response.setRenderParameter(serverFileName,
serverFileName);
getPortletContext().log(
serverFileName : + tempDir + / +
serverFileName);
}
}
Once i submit the multipart form, it does not enter the while
loop meaning
that the iterator is empty. Is this a bug?
I attached the rest of the source code. got this from one of
the messages in
this mailing list.
Thanks,
Nik
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 2/22/2005
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Corrupt Fragment Info
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 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 ... I'm seeing some strange behavior, the following line of velocity code (taken from a portlet decorator) returns the overwritten fragment's previous portlet title instead of the title from my new fragment(portlet) ... $!jetspeed.getTitle($myPE, $myF) All my new portlet's deployment info is correct, J2 appears to be caching the previous fragment's title somewhere. Anyone know where I can clear this? I can't seem to find it in the database. Where do fragments/portlet entities get cached? Is it outside the database? - Frank - 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]
Re: JS2 login portlet empty
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 initialization to complete. M1 had many deployment issues. Ate is working on a much better deployment solution, so you might want to consider trying again with the CVS/M2 release when he commits. Randy 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 jetspeed-user@jakarta.apache.org Sent: Friday, February 25, 2005 12:16 AM Subject: JS2 login portlet empty 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 isn't very helpful because then I can't login to Jetspeed and play around with it's customisation and personalisation tools. For info, in the WEB-INF/deploy directory there doesn't seem to be any war specifically for login or locale - the directory listing is: demo.war; jetspeed-layouts.war; jsf-demo.war; pam.war; perl.war; php.war; rss.war; security.war; struts-demo.war; All other portlets display fine - any help would be appreciated. Cheers, Craig - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: using MySQL with J2 - setup problem
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
org.apache.jetspeed.test.database.url=jdbc:mysql://localhost/j2test
org.apache.jetspeed.test.database.driver=org.gjt.mm.mysql.Driver
org.apache.jetspeed.test.database.user=admin
org.apache.jetspeed.test.database.password=admin
org.apache.jetspeed.production.jdbc.drivers.path=${org.apache.jetspeed.server.shared}/mysql-connector-java-3.0.16.jar
org.apache.jetspeed.production.database.default.name=mysql
org.apache.jetspeed.production.database.url=jdbc:mysql://localhost/j2
org.apache.jetspeed.production.database.driver=org.gjt.mm.mysql.Driver
org.apache.jetspeed.production.database.user=admin
org.apache.jetspeed.production.database.password=admin
Randy
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
[echo]
==
NOTE: Targetting JVM 1.4, classes
will not run on earlier JVMs
==
[javac] Compiling 27 source files to
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\portlet-api\target\classes
BUILD FAILED
File..
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\maven.xml
Element... maven:reactor
Line.. 133
Column 40
Unable to obtain goal [java:compile] --
C:\Marina\MyWork\Maven\cache\maven-java-plugin-1.5\plugin.jelly:63:48:
ant:javac Error running javac.exe compiler
Total time: 37 seconds
Finished at: Fri Feb 25 19:23:20 EST 2005
Any idea what is wrong now?
Thank you!
Marina
--- Hema Menon [EMAIL PROTECTED] wrote:
Marina,
What I meant to say is that, I believe the default
name should be the
type of database name, so in your build script it
should be mysql
instead of j2 and j2test. If you look at the sample
build properties,
it contains hsql for both test and production
default database name.
org.apache.jetspeed.test.database.default.name=hsql
org.apache.jetspeed.test.database.ojb.platform=Hsqldb
Hema
On Thu, 24 Feb 2005 18:37:18 -0800 (PST), Marina
[EMAIL PROTECTED] wrote:
Hi,
I finally got around to switch from HSQLDB to
MySQL
and ran into a build problem.
I setup MySQL DB schema and users per J2
instructions
(created 'j2test' and 'j2' schemas and the
'jetspeed2'
user that has all writes for those schemas). I
have
also modified J2's build.properties to use MySQL
(I'm
including a snippet below).
After that, I do the following:
1. start MySQL DB
2. cd [EMAIL PROTECTED]
maven allClean - OK
maven allBuild - Error:
Attempting to download
maven-torque-plugin-3.2.jar.
2/6K
6/6K
6K downloaded
build:start:
allBuild:
check.required.properties:
torque:init:
db.scripts.gen:
[echo] Generating SQL schema creation
scripts for
HSQLDB
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\hsql\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
MySQL
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\mysql\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
Oracle
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\oracle\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
MS SQL
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\mssql\report.portal.sql.generation
[echo] Generating SQL schema creation
scripts for
Postgres
[torque-sql] Using classpath
[torque-sql] Generating to file
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\target\src\sql\postgres\report.portal.sql.generation
BUILD FAILED
File..
C:\Marina\Harvard\Projects\jakarta-jetspeed-2-MYSQL\maven.xml
Element... sql
Line.. 355
Column 39
Source file does not exist!
Total time: 12 seconds
Finished at: Thu Feb 24 21:27:54 EST 2005
Here is my build.properties (relevant parts):
# Override the database connection and
driverproperties in your
${USER_HOME}/build.properties
appropriately
# See:
#
http://portals.apache.org/jetspeed-2/database.html
