[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Freedman resolved PORTLETBRIDGE-211. -------------------------------------------- Resolution: Fixed Fix Version/s: 3.0.0 With the release Trinidad 2.0.0 these problems have gone away -- so marking bug as resolved. > Trinidad doesn't work with the 3.0.0 Portlet Bridge > --------------------------------------------------- > > Key: PORTLETBRIDGE-211 > URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-211 > Project: MyFaces Portlet Bridge > Issue Type: Bug > Components: TCK > Affects Versions: 3.0.0-alpha > Reporter: Michael Freedman > Assignee: Scott O'Bryan > Fix For: 3.0.0 > > > I got 2.0.0-alpha2 working with a patch but once I upgraded to 2.0.0-beta-2 > (which fixed the problem I needed to patch) the bridge completely breaks as > long as the app includes the trinidad libs. There seems to be some > incompatibilities between the Trinidad extensions and the bridge's. Did get > a chance to track down the specific details but wanted to get the issue > logged as its likely to be identified much faster by someone in the Trinidad > team. > To reproduce -- get the bridge-3.0.0-alpha and set up a project pointing to > the 3.0.0 TCK. Follow the instructions in the TCK User Manual for building > it, configuring it on Apache, and then running it. With the Trinidad jars in > the deployment you will find that almost all the test fail (>170) -- the few > that pass don't actually execute Faces. If you remove the jars (and I think > drop the other Trinidad refs in the web.xml) things run fine except for those > few tests that depend on Trindiad (failed tests shoudl be something like 37). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira