After about a weeks worth of work today I was able to get a running tapestry JSR-168 portlet to work in WebSphere Portal. I had initially gone down the path of trying to integrate Tapestry 4 with Portal Server 5. This didn't work because Portal Server 5 runs jdk 1.3.1 and Tapestry was trying to load a 1.4 class, specifically java.util.IdentityHashMap (Created bug Tapestry-452 on JIRA). Then I went down the path of installing WebSphere Portal 5.1 which uses jdk 1.4.2 (most of my time being spent here). This got me further, but not quite there. I got an exception involving tapestry annotations. This ended up being an easy fix. Remove tapestry-annotations-4.0.jar from the classpath. I should have known this since I'm using jdk 1.4.2 but it may be beneficial to add to the documentation to only include this jar if you are using jdk 1.5 (for people like me that blindly include all framework jars when trying to get a sample app running).
Otherwise, everything was good. Looking forward to experimenting with tapestry in the portlet world. Ryan
