Are there any inherent disadvantages to directly presetting a property's
default value on an ActionBean instead of using the @Before interceptor?
For example:
public class MyActionBean extends ActionBean {
private String prop = "preset";
public Resolution view() { ... }
public String getProp() { ... }
public void setProp(String prop) { ... }
}
...versus...
public class MyOtherActionBean extends ActionBean {
private String prop;
@Before(stages = {LifecycleStage.BindingAndValidation})
public void init() {
setProp("preset");
}
public Resolution view() { ... }
public String getProp() { ... }
public void setProp(String prop) { ... }
}
--
View this message in context:
http://www.nabble.com/Any-advantage-to-%40Before-over-straight-property-%3D-value--tp25017706p25017706.html
Sent from the stripes-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
