Then i guess you do not need the PageRenderLinkSource. Use simple java.net.URL, also you may generate your URLs via a Service that will allow you to configure different part of URL (host, port...) via Symbol.
2010/2/3 Everton Agner <everton_ag...@yahoo.com.br> > Oh... sorry, I forgot the most important thing. > > The other app isn't a Tapestry application... > > > > > ________________________________ > De: cordenier christophe <christophe.corden...@gmail.com> > Para: Tapestry users <users@tapestry.apache.org> > Enviadas: Quarta-feira, 3 de Fevereiro de 2010 11:32:14 > Assunto: Re: Link to a Page from another context > > Hi > > (If application are deployed in the same container) I guess using > crossContext feature will allow you to have access to Tapestry Registries > of > other application contexts. Then you can call PageRenderLinkSource service > instance of other context. > > It depends on the security level you want for your architecture, some > prefer > to disable crossContext feature. > > Regards, > Christophe. > > Developer of wooki @wookicentral.com > > > 2010/2/3 Everton Agner <everton_ag...@yahoo.com.br> > > > Hi, > > > > I have a PopupPageLink Component that receives a Page path and redirect > to > > the page via : PageRenderLinkSource.createPageRenderLink(). > > > > The problem is when i have to redirect to a page from another context, > > because it tries to find the page within the app context. How can I avoid > > doing that? I need to pass it through the PopupPageLink. > > > > > > > > > > > > ____________________________________________________________________________________ > > Veja quais são os assuntos do momento no Yahoo! +Buscados > > http://br.maisbuscados.yahoo.com > > > > > > > > ____________________________________________________________________________________ > Veja quais são os assuntos do momento no Yahoo! +Buscados > http://br.maisbuscados.yahoo.com >
