geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: pluto portal for geronimo 2.0
Date Wed, 13 Jun 2007 00:23:28 GMT

On Jun 12, 2007, at 2:54 PM, Jeff Genender wrote:

> Paul,
> Nice work. As for cross-context, why not use a standard geronimo- 
> web.xml
> that allows yu to place container-specific configurations for both  
> Jetty
> and Tomcat.  IIRC, each container will only pick up its own
> configuration.  I recall we did this for the exact reason you  
> cited ;-)

Sure, but if you are planning to use this for the admin console  
you'll probably need separate modules for jetty and tomcat anyway, so  
2 plans is more or less required even if they  are identical.

Is pluto 1.2 actually functional as a real portal, or is it just way  
easier to deploy portlets to than 1.0 was?  My impression was that it  
was not really intended to be a jetspeed or liferay replacement.   
I've been hoping that now that jetspeed has m2-ized their build we  
might be able to pursue jetspeed integration again.

david jencks

> Jeff
> Paul McMahan wrote:
>> We have talked about upgrading the admin console to use a more recent
>> version of pluto.  Now that geronimo 2.0 has taken shape I took a  
>> look
>> at pluto 1.2 and found that it has a lot of new features that we  
>> should
>> take advantage of, including the ability to make our admin console  
>> more
>> dynamic and customizable.  It is not backwards compatible with the
>> version that we currently use so we can't just swap in the jars.  But
>> that's OK since I think our goal to make the admin console more  
>> dynamic
>> probably warrants a bit of redesign anyway.   I just committed some
>> stuff to sandbox that demonstrates one technique for integrating  
>> pluto
>> into geronimo, and I think it can serve as the basis for a more  
>> dynamic
>> admin console as well.   You can try it out by following these steps:
>> svn co
>> cd portals
>> mvn
>> geronimo/bin/ install-plugin
>> pluto-container/target/
>> geronimo/bin/ deploy
>> pluto-portal/target/pluto-portal-1.0-SNAPSHOT.war
>> geronimo/bin/ deploy pluto-testsuite/target/pluto- 
>> testsuite.war
>> point your browser at http://localhost:8080/pluto/portal
>> This works in the minimal or jee5 assemblies, but right now it only
>> supports tomcat because the <cross-context> setting is required in
>> geronimo-web.xml.  I was hoping to avoid a separate jetty module just
>> for that setting, but maybe that's unavoidable.   The maven related
>> stuff could probably use some tuning as well.
>> While working on this it occurred to me that we could consider  
>> providing
>> a native general purpose portal in geronimo, and the admin console  
>> as we
>> know it today could just be a collection of portlets deployed into it
>> that are only visible to users with sufficient admin privileges.    
>> The
>> stuff in sandbox could also help us move things in that direction  
>> if we
>> like that idea.   Thoughts?
>> Best wishes,
>> Paul

View raw message