Message:
The following issue has been closed.
Resolver: David Le Strat
Date: Sat, 29 May 2004 2:52 PM
This feature has been implemented. The implementation follows 2 steps:
1. Parse the portlet.xml to grab the user attributes declared for a portlet. This is
done in org.apache.je
Message:
The following issue has been closed.
Resolver: David Le Strat
Date: Sat, 29 May 2004 2:45 PM
This issue is also addressed in:
http://nagoya.apache.org/jira/browse/JS2-56
This issue has been resolved by patching OJB. The fix impacts
org.apache.ojb.broker.util.ClassHelper
dlestrat2004/05/29 12:46:00
Modified:applications/demo/src/webapp/WEB-INF/demo/userinfo
userinfo.jsp
Log:
User info is now working! Need some nicer front end but that will do for now.
Revision ChangesPath
1.5 +2 -2
jakarta-jetspeed-2/a
taylor 2004/05/29 12:01:49
Modified:portal/src/java/org/apache/jetspeed/engine
JetspeedEngine.java
Log:
patch to OJB to allow it to use jetspeed context class loader to find classes
requires a patched version of OJB, found at
http://www.bluesunrise.com
Le 27 mai 04, à 19:31, David Pankros a écrit :
To deploy portlets to j2 do you just drop the war into the tomcat
deploy dir
(i.e. ${deploy.war.dir})? Obviously, the war contains the portlet.xml
and
all that other good stuff...
No that's not enough, J2 needs to be aware of teh webapp to actual
Use the following instructions:
http://jakarta.apache.org/site/cvsindex.html
Le 23 mai 04, à 14:59, Vikas Gupta a écrit :
Paul
I am using default port 2401 to connect,
is it correct or do i have to use some other port
Regards
Vikas
-Original Message-
From: Paul Spencer [mailto:[EMAIL PROTEC
