Just in case someone is wondering why I did not use a FilteredActivityMapper: the activity manager would work perfectly, the problem is the ActivityController: it does not see the "place redirect". This way the place controller does not really know where the application is.
Here is my problem: I have a "haveToGoHereFirst" place. placecontroller.goto(somewhere); ==> now placecontroller thinks we are somewhere filter changes to haveToGoHereFirst(whereDidIComeFrom) activity mapper returns activity for haveToGoHereFirst haveToGoHereFirst does some work, and finally takes the user where it wanted to go to in first place by calling placecontroller goto( somewhere ) ==> now nothing happens. the place controller sees you going to somewhere again and does not trigger the place request. To fix this, we shold add the place filter to the placecontroller, and have a activity filter on the activity mapper. the way it is, it is imho broken. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
