click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <j...@apache.org>
Subject [jira] Closed: (CLK-562) AbstractControl and default constructor
Date Mon, 29 Jun 2009 16:06:47 GMT

     [ https://issues.apache.org/jira/browse/CLK-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bob Schellink closed CLK-562.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0
         Assignee: Bob Schellink

fixed in trunk

> AbstractControl and default constructor
> ---------------------------------------
>
>                 Key: CLK-562
>                 URL: https://issues.apache.org/jira/browse/CLK-562
>             Project: Click
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.1.0
>            Reporter: WarnerJan Veldhuis
>            Assignee: Bob Schellink
>            Priority: Trivial
>             Fix For: 2.1.0
>
>
> The AbstractControl javadoc says: "Subclasses are expected to at least override getTag()
 to differentiate the control.". What it *also* should mention, is that it needs a default
constructor if you have created a custom constructor. 
> At deploy time, all the controls listed in click.xml will have their onDeploy() method
called. But the reflection part will fail if the default cstor does not exist.
> org.apache.click.service.XmlConfigService.deployControls(XmlConfigService.java:1077):
>        Class deployClass = ClickUtils.classForName(classname);
>        Control control = (Control) deployClass.newInstance();  //<--- fails at deploy
time
>        control.onDeploy(servletContext);

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message