This is a known issue (well at least to Mike and myself). WOLips was
previously ignoring any generified classes completely and not
validating them at all. I recently changed this to replace
unresolvable types (S in this case) with "Object" which isn't ideal
but it's the best I could do at the time. The plan is to go back and
improve this when I have a chance. The erased type "should" evaluate
to "Project" instead of "Object" in this case, but currently it
doesn't. Ideally it should resolve to the unerased type
(SpecialProject) but that will require some heavy handed refactoring
of how validation type resolution and caching works.
On 28/09/2008, at 6:39 PM, Alan Zebchuk (JIRA) wrote:
> Problem validating components with generics
> -------------------------------------------
>
> Key: WOL-899
> URL: http://issues.objectstyle.org/jira/browse/WOL-899
> Project: WOProject/WOLips
> Issue Type: Bug
> Components: wolips
> Environment: 3.4.5484
> Reporter: Alan Zebchuk
>
>
> For Example, if my component is like this:
>
> public class SpecialProjectsListing extends
> ProjectListingComponent<SpecialProject>
>
> And Project Listing Component has the following:
>
> public abstract class BaseResearchProjectsListingComponent<S extends
> Project> extends WOComponent {
>
> and has the following field:
>
> public S project;
>
> Then, the Component editor won't validate any of the keypaths on
> project, such as project.title
>
>
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10) Ph: +61 419 729 806
This archive was generated by hypermail 2.0.0 : Mon Sep 29 2008 - 19:18:10 EDT