Creator 2 EA and Apache's Pluto Portlet Container: Part 2
By David Botterill on Sep 23, 2005
In my last "blog":http://blogs.sun.com/roller/comments/david/Weblog/creator_2_ea_and_apache about Creator and Pluto, I briefly mentioned how erasing the “plutocontainer” directory in your user directory will reset Pluto.
Let me explain a little bit more about that. If for some reason, your portlet environment, Pluto, seems to be trashed and not working correctly when you deploy from Creator, you can delete the “plutocontainer” directory in your user directory to cause a refresh. The next time you deploy a portlet, the “plutocontainer” directory will be created again for you.
The “plutocontainer” directory is basically Pluto deployed. Now I know some of you will be tempted to experiment with changing things in this directory.
\*CAUTION\*: Please understand that when you do so, you're on your own. Also, I won't guarantee that this implementation will continue in the next release.
The great part is if you mess it up too bad, you simply have to rename it or delete it to get a fresh copy. When the “plutocontainer” directory is created, Creator basically extracts a jar from a jar then unjars it. That's why the “Initializing portlet container. Please wait...” period of a deploy can take so long.