Hello, users. Is there a way to separate activation contexts for page and its components?
I wrote a component that uses AJAX to interact from client side. Render part of the component creates links for callbacks using ComponentResources. And callbacks are method with fixed number of arguments (2 for ex.). When the page that contains that component tries to introduce its own activation context, callback url will have page's context embedded. So now AJAX calls to component with 3 context elements - 1 from page and 2 from component. And as the component knows nothing about this, it must be treated in a special way (for now I retained only onActivate part of the page so it's not a fully pages context that is saved). Is there a way to clearly separate contexts of the page and component events so that component could be unaware of any page it is embedded to? -- Best regards, Yury --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
