Hi, my tapestry/portlets project is advancing quite a bit. I'm currently stuck at a page that contains 3 portlets, each being generate from one tapestry page. One of the portlets contains a form that does some default tapestry javascript form validation (checking whether an integer form really contains an integer value). This validation fails if tapestry includes its javascript default libraries in one of the other portlets. If the other portlets do not contain javascript it works fine. I can also work around this if I move my form portlet to some other location in the page. I think that it always works if the form-containing portlet is the last in the html code of the rendered portal page.
Now my question is: can anybody image what is causing these cross-portlet issues? Can I automatically get this fixed my "separating" the javascript scope on the page? Can I manually disable the tapestry-javascript inclusion in my pages with an annotation? (Then of course I would have to make sure that one of the portlets on the page actually does the inclusion). Thanks for any help Moritz --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
