Yes, but I get what he was saying. I'll take a look at the tap worker method tonight and see if I can't figure out how to get a custom one working. Dmitry, do you know what I'll need to do in my app module to get my custom annotation working?
On Wed, Sep 3, 2014 at 10:58 AM, Dmitry Gusev <dmitry.gu...@gmail.com> wrote: > Aren't you talking about different things: ActivationRequestParameter vs. > PageActivationContext ? > > > On Wed, Sep 3, 2014 at 5:31 PM, George Christman <gchrist...@cardaddy.com> > wrote: > > > I'd like to just create my own then since it handles the urls so well. > How > > would I go about doing that lance? > > > > > > On Wed, Sep 3, 2014 at 2:23 AM, Lance Java <lance.j...@googlemail.com> > > wrote: > > > > > @PageActivationContext is a convenience annotation that ultimately > > creates > > > onActivate(..) and onPassivate() methods on your page. I think you're > > > surpassing what it was designed for. > > > > > > You should just declare onActivate(..) and onPassivate() instead (or > > maybe > > > create your own @PageActivationContexts annotation / worker). > > > > > > > > > > > -- > > George Christman > > www.CarDaddy.com > > P.O. Box 735 > > Johnstown, New York > > > > > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com > -- George Christman www.CarDaddy.com P.O. Box 735 Johnstown, New York
