Ate,What is your timeline for 2.0.1? I think I'd like to look at creating a 2.1.0 branch to do some refactoring as far as what goes where in the pluto modules as well as some new features and changes. If I start that branch this week will it interfere with the 2.0.1 work?
I think the first place I'll be focusing is the portlet registration process. As far as I can tell the current implementation breaks if the portal webapp is ever redeployed. Portlets appear to start a Timer when they init to register themselves with a portal injected implementation class. If the portal is restarted that class is no longer valid but there is no way for the redeployed portal to still access the previously registered portlets. I have a few ideas on how to address this but I'll post more detail once I've actually dug in a little further.
-Eric
smime.p7s
Description: S/MIME Cryptographic Signature
