Those would be allowed as long as they are in a .base. package. On Nov 26, 2007 11:32 AM, Robert Zeigler <[EMAIL PROTECTED]> wrote: > What about abstract "base" pages? > > Robert > > > On Nov 26, 2007, at 11/261:26 PM , Howard M. Lewis Ship (JIRA) wrote: > > > Tapestry should enforce that component classes only extend from > > other (transformed) component classes, or java.lang.Object > > -------------------------------------------------------------------------------------------------------------------------- > > > > Key: TAPESTRY-1934 > > URL: https://issues.apache.org/jira/browse/TAPESTRY-1934 > > Project: Tapestry > > Issue Type: Bug > > Components: tapestry-core > > Affects Versions: 5.0.6 > > Reporter: Howard M. Lewis Ship > > > > > > Currently, you can have a component extend from any base class. > > That causes issues when there's a class (that, perhaps, has state) > > between java.lang.Object and a component class (i.e., a class in a > > managed component class package). Tapestry should explicitly forbid > > this. > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
-- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
