History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: WW-1331
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Nils-Helge Garli
Reporter: Nils-Helge Garli
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
WebWork

The Jsr168Dispatcher does not initialize the DispatcherUtils

Created: 30/Jul/06 05:37 AM   Updated: 14/Aug/06 03:41 PM
Component/s: Portlet Integration
Affects Version/s: 2.2.2
Fix Version/s: 2.2.3

Flags: Important


 Description  « Hide
The consequence is that the filter dispatcher needs to be added to the web.xml to detect that portlet support is active. I don't think it's necessary that the initialization of DispatcherUtils checks to see if it can find the portlet classes. It can be a field that is set by the Jsr168Dispatcher, since it only makes sense that portlet support is active if you use the portlet dispatcher.

 All   Comments   Change History      Sort Order:
Rainer Hermanns - [14/Aug/06 10:06 AM ]
Turns out to be a blocker, since the portlet support is currently broken.
See http://forums.opensymphony.com/thread.jspa?messageID=79930&#79930 for details

Rainer Hermanns - [14/Aug/06 03:41 PM ]
Fixed by Nils with latest commit, thanks a lot!