[ http://issues.apache.org/struts/browse/WW-1424?page=comments#action_38088 ] Don Brown commented on WW-1424: -------------------------------
Ted Husted wrote: > In my experience, the easiest way to flatten the learning curve is > consistency. > > Right now, our approach to default result types is inconsistent. Most > results work out of the box, but some require people to add optional > JARs to the distribution. For the "optional" results, we've started to > add apologetic logging statements, saying "Oops, I'm here, but my JAR > isn't, but you probably don't care anyway." > > If we are going to have optional result types, then let's have > optional result types. Let's add an "optional" attribute, so that we > can render more meaningful logging statements. > > 1 When optional=true, and the support class is absent, then nothing is logged. > > 2 When optional=true, and the support class is present, then a DEBUG > logging statement saying the result is enabled is logged > > 3 When optional=false (the default), and the support class is absent, > a runtime exception is logged and thrown (fail fast). > > 4 When optional=false, and the support class is present, then nothing > is logged (the nominal case). > > Even if we mark a result type optional in the configuration, we can > still override the setting in a package, so if we need to do a problem > determination, we can add the result again as "optional=false" in a > package, so that we can be sure the system sees the result, but not > the JAR. > > -Ted. > Missing or unneccessary configuration objects shouldn't throw warning messages > ------------------------------------------------------------------------------ > > Key: WW-1424 > URL: http://issues.apache.org/struts/browse/WW-1424 > Project: Struts 2 > Issue Type: Bug > Components: Configuration > Reporter: Don Brown > Assigned To: Don Brown > Priority: Minor > Fix For: 2.0.1 > > > In the struts-default.xml file, we define interceptors and results that > aren't needed by most applications. Currently, they result in warn messages > when they can't be loaded. We should, at a minimum, reduce these to infos, > but perhaps in the long term, provide better support for extra configuration > elements that aren't "required". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
