Re: Strange component parameter issues with annotations

2006-09-07 Thread andyhot
I like using the reset service, instead of disabling cache. This way i can control when the templates+xml are reloaded. I simply have a tab opened at http://127.0.0.1:9090/app?service=reset&page=Home and refresh it whenever i want changes to be reloaded. See http://tapestry.apache.org/tapestry4/U

Re: Strange component parameter issues with annotations

2006-09-07 Thread Jan Normann Nielsen
Jan Normann Nielsen skrev: Hi I'm currently writing a Tapestry web application using Tapestry 4.0.2 under Tomcat 5.5.18 and JDK 1.5.0_08. [bla-bla - snip] I this is not a lot of information to go by, but my application is quite big and this is what I have narrowed the problem down to. I hav

Re: Strange component parameter issues with annotations

2006-09-07 Thread andyhot
Do you have org.apache.tapestry.disable-caching set to true ? Jan Normann Nielsen wrote: > Hi > > I'm currently writing a Tapestry web application using Tapestry 4.0.2 > under Tomcat 5.5.18 and JDK 1.5.0_08. > > The situation is: > > Page 1: Contains "Iframe page 1" and "Iframe page 2" as iframe

Strange component parameter issues with annotations

2006-09-07 Thread Jan Normann Nielsen
Hi I'm currently writing a Tapestry web application using Tapestry 4.0.2 under Tomcat 5.5.18 and JDK 1.5.0_08. The situation is: Page 1: Contains "Iframe page 1" and "Iframe page 2" as iframes. Iframe page 1: Contains "Component 1" Iframe page 2: Contains "Component 2" All these pages, ifram