I tried to look at those listeners. If I understand correctly you always
need to be a component to be a listener.
Each listener interface must have 1 method with 0 parameters. So it means
all state must be kept in the component.
You cannot pass any parameters to it? So in the case of a PageLink you must
know which page to render, before
the link has been clicked?
I'm just trying to sort things out in my head.
I would like to know more about how Wicket knows which ILinkListener to call
when a link is clicked. I found the apidocs
to be rather abstract about listeners. It felt like you already had to know
how they work before you can understand the docs.
Please don't take any off this as criticism against Wicket. I'm sure it is a
great project. And I will be using it in the future.
I'm just not sure if I should convert this project from Tapestry to Wicket.
I am beginning to think that it's not a good idea.
On 3/15/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
yes. that and the ability to create new listeners. there is nothing
special about the listeners that wicket pre-registers to handle various
kinds of requests such as resource requests or link clicks (although you
should definitely prefer the already existing event listeners!). in fact,
below is the code in init that registers all the "service" listeners in
wicket
revealing that you can create your own if you're doing something special
that wicket does not (yet) support.
/**
* @see wicket.IInitializer#init(wicket.Application)
*/
public void init(Application application)
{
// Register listener interfaces explicitly (even though
they implicitly
// register when loaded) because deserialization of an
object that
// implements an interface does not load the interfaces it
implements!
IBehaviorListener.INTERFACE.register();
IUnversionedBehaviorListener.INTERFACE.register();
IFormSubmitListener.INTERFACE.register();
ILinkListener.INTERFACE.register();
IOnChangeListener.INTERFACE.register();
IRedirectListener.INTERFACE.register();
IResourceListener.INTERFACE.register();
}
public interface ILinkListener extends IRequestListener
{
/** Listener interface */
public static final RequestListenerInterface INTERFACE = new
RequestListenerInterface(
ILinkListener.class);
/**
* Called when a link is clicked.
*/
void onLinkClicked();
}
igor.vaynberg wrote:
>
> wicket's equivalent of a service is a shared resource. you can register
> your
> own shared resources through your webapplication subclass.
>
> as far as selecting pages via javascript:
>
> wicket doesnt really have a page service. urls for pages are resolved
> internally. if you want a stable entry point into the page then you
should
> mount it, also via the webapplication subclass, and then the javascript
> can
> redirect to the mounted url.
>
> -igor
>
>
> On 3/15/07, Robert . <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I have been examining how I can convert a web application product from
>> Tapestry 3 to Wicket, and trying to adapt
>> myself to the Wicket way of thinking about web flow.
>>
>> One part that I just can't seem to figure out from reading Pro Wicket
and
>> browsing through the apidocs is how to
>> make something like Tapestry "services".
>>
>> For example I have an action service in Tapestry that let's me send an
>> action command, including additonal parameters,
>> to the service by using javascript. I have such a service for both
normal
>> requests and XMLHTTP requests. But thinking
>> about this further makes me realize I don't even know how to make
>> something like a PageService where the page is determined by
javascript.
>>
>> I feel like I am missing something.
>>
>> Robert
>>
>>
>>
>>
-------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your
>> opinions on IT & business topics through brief surveys-and earn cash
>>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Wicket-user mailing list
>> Wicket-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wicket-user
>>
>>
>
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
--
View this message in context:
http://www.nabble.com/Tapestry--%3E-Wicket-%7C-Action-Service-tf3408177.html#a9504695
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
