I found that I was wrong. I did not put the contribution right place. I did place it in servlet module, so in portlet the contribution is useless. I fixed by putting it to the portlet module, and now it runs properly. I've modified the source that I download from https://issues.apache.org/jira/browse/TAP5-78 and now I can run portlet with tapestry version 5.0.18 and 5.1.0.5.
On Tue, Sep 1, 2009 at 8:18 AM, Xuan Tran Le <lexuanttk...@gmail.com> wrote: > I did debug and found that AppModule is loaded and the contribution is > called. It runs properly in servlet mode, but when run in portlet mode it > doesn't. > > > On Tue, Sep 1, 2009 at 5:29 AM, Howard Lewis Ship <hls...@gmail.com>wrote: > >> The only explanation for this is that your AppModule is not being >> loaded; Tapestry sends debug output at startup to list modules that >> are loaded; that's the first step. For example, AppModule must be in >> the correct package for Tapestry to find it. The rules for all this >> are in the documentation. >> >>
