You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/11/26 20:26:43 UTC
[jira] Created: (TAPESTRY-1934) Tapestry should enforce that
component classes only extend from other (transformed) component classes,
or java.lang.Object
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Created: (TAPESTRY-1934) Tapestry should enforce that component classes only extend from other (transformed) component classes, or java.lang.Object
Posted by Howard Lewis Ship <hl...@gmail.com>.
Those would be allowed as long as they are in a .base. package.
On Nov 26, 2007 11:32 AM, Robert Zeigler <ro...@scazdl.org> 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: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] Created: (TAPESTRY-1934) Tapestry should enforce that component classes only extend from other (transformed) component classes, or java.lang.Object
Posted by Robert Zeigler <ro...@scazdl.org>.
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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-1934) Tapestry should enforce that
component classes only extend from other (transformed) component classes,
or java.lang.Object
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1934.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.7
> 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
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Assigned: (TAPESTRY-1934) Tapestry should enforce that
component classes only extend from other (transformed) component classes,
or java.lang.Object
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAPESTRY-1934:
----------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
> Assignee: 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org