Just a quick update: I solved my problem, which was more about my specific using of zones than the zone functionality itself being broken. It was rather changed. I have a few nested components that need zone, which means that I have a few zone="inherit:zone" properties. Now, in one of the components, I didn't created an explicit zone property, so it seems that the "chain" was broken at that point. In the prior versions of T5.1 it worked, and it seems that the newer version became more restrictive about that.
Dragan Djuric wrote: > > > > Howard Lewis Ship wrote: >> >> Yes, a lot of code has changed there. Can you create a JIRA issue, >> preferably with a sample app to demonstrate the problem? >> > > I thought about opening an issue, but I decided to wait a few days to see > if there will be some simple solution. I am not sure how easy it will be > to create a simple demonstration, because the code that has the problem > depends on other projects and have a lot of simple nested components. I am > not sure whether I can make it dead simple and still show the problem, but > I'll try (I won't be near a computer until 22. Feb, so the I'll probably > create the demo and raise the issue after that). > I still hope that someone will come up with a few simple canges that shuld > be done in the app code to solve the problem :) > > -- View this message in context: http://www.nabble.com/Zone-broken-in-15-February-2009-5.1.0.0-SNAPSHOT-changes-tp22039148p22252825.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
