On 2/17/08, Davor Hrg <[EMAIL PROTECTED]> wrote: > You can instead just accept string > and call TypeCoercer your self in the meanwhile
That's a very nice and clever way to do that, but that would not be very elegant in my structure. I defined an ActivationContextContext<T, A> interface to encapsulate all the activation context encoding and decoding of some class in a single place, so I can do two very nice things: to change the activation context without changing any other class and to build ActivationContextActionLink, a component similar to ActionLink, but it receives an object and uses its activation context value to build the link. ;) -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
