Alas no. All classes inside those packages (and sub packages) are transformed (re-loaded) by T5. I either stick it in the "services" package or create a separate package called "util" or "entity".
com.myapp.components com.myapp.pages com.myapp.services <-- here com.myapp.entities <-- or here com.myapp.util <-- or here Steve. On 30 June 2012 20:22, bhorvat <horvat.z.bo...@gmail.com> wrote: > I see, well that makes sense. Can I place that class then inside a components > page, or better yet components subpackage? > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Breaking-auto-realding-feature-with-embeded-classes-tp5714201p5714206.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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
