Correct. Taga's 3rd option fulfills what I need but I didn't catch the
difference. Thank you all.
On Fri, Aug 31, 2012 at 12:45 PM, Bob Harner <bobhar...@gmail.com> wrote:
> Taha's 3rd option is refactor-safe, too. On the other hand, since Tapestry
> will complain loudly about links to non-existent pages, using strings for
> page names is less risky in this case.
> On Aug 31, 2012 5:26 AM, "Lance Java" <lance.j...@googlemail.com> wrote:
>
> > @Inject
> > private ComponentClassResolver componentClassResolver;
> >
> > public String getProbesHealthPageName() {
> > return
> >
> >
> componentClassResolver.resolvePageClassNameToPageName(ProbesHealth.class.getName());
> > }
> >
> >
> >
> > --
> > View this message in context:
> >
> http://tapestry.1045711.n5.nabble.com/t5-3-4-Plugin-blocks-tp5715810p5715936.html
> > Sent from the Tapestry - User mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
--
*Regards,*
*Muhammad Gelbana
Java Developer*
