Hi, Tapestry over time added additional checks to detect whether the classes in the Tapestry specific packages are really only relevant to Tapestry. Not doing so can cause unexpected exceptions due to classloading issues.
in other words: only page, component and mixin classes go into the respective packages. everything else should be moved outside (eg. base or services) not a big deal, just a precaution. g, Kris On Tue, Jul 2, 2013 at 10:38 AM, Dmitriy Vsekhvalnov <dvsekhval...@gmail.com > wrote: > Hi everyone, > > doing app migration from 5.1 to 5.3, currently face with weird exception: > > > Caused by: org.apache.tapestry5.ioc.internal.OperationException: Base class > java.lang.Enum (super class of xxx.xx.xx) is not in a controlled package > and is therefore not valid. You should try moving the class to package > xxx.base. > > > What does it mean? >
