[ http://issues.apache.org/jira/browse/JS2-444?page=all ]
David Jencks updated JS2-444:
-----------------------------
Attachment: patch4.diff
With the enclosed patch I have jetspeed running on geronimo. In order to deal
with some classloading problems I moved all the jars out of jetspeed.war lib
and added dependencies in the ear file. I also had to modify
PortletApplicationManager to determine "local" based on whether the war name
starts with "jetspeed-", since in my setup all wars are deployed the same, as
wars in the ear.
I actually think this will lead to a better solution for environments with
reasonably sophisticated classloading, such as geronimo. I plan to have 2
basic configurations (i.e. classloaders) for jetspeed in geronimo: a base
configuration that includes basically the jars put into "shared" in tomcat, and
a child configuration that includes as dependencies all the jars normally put
into jetspeed.war lib. "regular" portlet applications can then be deployed as
children of the base configuration, whereas "local" portlet applications can be
deployed as children of the child config. In this way the local portlet apps
won't need to use special directories in the unpacked jetspeed war and the
jetspeed war probably won't need to be unpacked.
However, what I have in this patch is rather crude.
This patch is generated with svk: if anyone has trouble applying it please let
me know. To get to my local state you should unpack the zip file i provided,
then apply patch1.diff and patch4.diff.
This file includes a modification to JetspeedDeploy from Jian Liao.
> Run Jetspeed 2.0 on Geronimo V1.0
> ---------------------------------
>
> Key: JS2-444
> URL: http://issues.apache.org/jira/browse/JS2-444
> Project: Jetspeed 2
> Type: New Feature
> Versions: 2.1-dev
> Environment: WinXP SP2, JDK1.4.2_10
> Reporter: James Liao
> Attachments: GeronimoSecurityValveImpl.java,
> geronimo-application.xml.20051219, geronimo-j2.zip, geronimo-jetspeed.zip,
> patch1.diff, patch4.diff
>
> Run Jetspeed V2.0 on Geronimo V1.0.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
