You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Luther Baker <lu...@gmail.com> on 2009/06/07 00:00:45 UTC

wicket:link -> wicket:context

I'd like to consider writing a component similar to wicket:link.

I don't think wicket:link actually does the dirty work. My cursory view at
the source suggests that wicket:link sets a flag and some other classes
update the actual path printed to the page. Is this an established or
documented pattern that I could follow for implementing something like
wicket:context? I have WIA but didn't recognize this type of component
discussed.

Igor mentioned:

> it may be helpful to create <wicket:context> analog of <wicket:link>, we
already have the framework for getting the path prefix to get to contextpath

Likely it is obvious - but would someone be able to briefly elaborate on the
'framework' Igor mentions here ... or anyone care to map out a high level
class or object blueprint of what I might look at or how to make this
happen?

Any suggestions would be appreciated.

Thanks,

-Luther

Re: wicket:link -> wicket:context

Posted by Jeremy Thomerson <je...@wickettraining.com>.
See org.apache.wicket.markup.resolver.AutoLinkResolver

--
Jeremy Thomerson
http://www.wickettraining.com




On Sat, Jun 6, 2009 at 5:00 PM, Luther Baker <lu...@gmail.com> wrote:
> I'd like to consider writing a component similar to wicket:link.
>
> I don't think wicket:link actually does the dirty work. My cursory view at
> the source suggests that wicket:link sets a flag and some other classes
> update the actual path printed to the page. Is this an established or
> documented pattern that I could follow for implementing something like
> wicket:context? I have WIA but didn't recognize this type of component
> discussed.
>
> Igor mentioned:
>
>> it may be helpful to create <wicket:context> analog of <wicket:link>, we
> already have the framework for getting the path prefix to get to contextpath
>
> Likely it is obvious - but would someone be able to briefly elaborate on the
> 'framework' Igor mentions here ... or anyone care to map out a high level
> class or object blueprint of what I might look at or how to make this
> happen?
>
> Any suggestions would be appreciated.
>
> Thanks,
>
> -Luther
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org