Inject page doesn't inject the page into the page you are looking at from a view standpoint, rather it makes an instance of that page a member of the page.
In the form submission of page 1, get the instance of page 2 via the accessor and set the appropriate attributes. The layout of page 2 (including borders/other components) is page 2's responsibility. If you have a border on page 1 but not on page 2, injecting page 2 into page 1 won't change that. Page 2 needs it's own border. I might be reading your email wrong, but if I'm not, you need to set up page 2 to work and display independently of page 1. If all it needs is the form data from page 1, that's all that should be needed for page 2 to be considered 'whole'. -Mike On 4/17/06, Mário Lopes <[EMAIL PROTECTED]> wrote: > Hello everyone! > > First off, I'm new to Tapestry so cheers everyone! :-) > > Well, I'm building an application and I need to share information > accross different pages. For instance, page1 has a form which gets > several values and fetches others from the database, while page2 > should be receiving those values and others, redirecting from page1. > > It seems there's two ways of doing this: Application State Objects, > like Visit or Global, and the new @InjectPage from Tapestry 4. > > InjectPage worked but it only shows the attributes belonging to the > class that's associated with, ignoring Border and other stuff like > hivemind SiteMap component. Now, am I not properly using InjectPage, > since it should only be used as a scaffold for viewing forms (?) or am > I missing something ? > > Some insight on the subject would be great! > > Thanks in advance. > > Kind regards, > > Mário Lopes > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
