AW: Re: unexpected exception - closed

2006-01-31 Thread Gerald Schöffel
Ok, finally I got it. Uh, very embarrassing, because I already use this method of injecting the PageService on another page in my app. So @InjectObject("engine-service:page") public abstract IEngineService getPageService(); did it - hopefully for all cases that could appear. So thank

AW: Re: unexpected exception

2006-01-31 Thread Gerald Schöffel
:-)=) Hi Howard, thank you for pointing this out ;) I did not expect this exception because I expect getService() to return a PageService - not a DirectService. In my understanding (which seems to be wrong :) ) the DirectService was 'consumed' on the Login-page to do the submit. After this,

Re: unexpected exception

2006-01-30 Thread Howard Lewis Ship
"Parameter parameter is of type java.lang.String which is not compatible with org.apache.tapestry.engine.DirectServiceParameter." The third parameter to the getLink() method (for the direct service) must be a DirectServiceParameter, not a string. I'm not sure how Tapestry could phrase it any clea

unexpected exception

2006-01-30 Thread Gerald Schöffel
Hi ! While doing some research to solve this nasty https/http-switching problem I have, I got to a point where a 'strange' exception is thrown. MyBasePage implements PageValidateListener: public void pageValidate(PageEvent event) { String url = event.getRequestCycle().getService().getLink