Webwork Configuration mechanism induces unnecessary SQL statements and hence hurts performance

The webwork configuration registry code looks up the view of any action. This is really an unbounded ste of data.

However the JIRA applications properties configurator has a go at looking up this value anways even though it can handle it

2011-06-23 12:15:08,033 http-8090-5 admin 735x929x1 1irnuir /secure/CreateIssue.jspa 1ms "SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype FROM PUBLIC.propertyentry WHERE ENTITY_NAME='jira.properties' AND ENTITY_ID='1' AND PROPERTY_KEY='CreateIssue.success'"

2011-06-23 12:15:08,033 http-8090-5 admin 735x929x1 1irnuir /secure/CreateIssue.jspa 1ms "SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype FROM PUBLIC.propertyentry WHERE ENTITY_NAME='jira.properties' AND ENTITY_ID='1' AND PROPERTY_KEY='CreateIssue.none'"

This results in an SQL statement and a a PropertySet cache entry. That cached entry repesents a value whcih is "I dont know" so JIRA is using memory to remember that it doesnt know somehting and then returning a "I dont know exception".

We need to do this smarter.

We should NOT respond to these keys. We can either look at the key and decide that its jira. or webwork. and only respond then OR we can prefix the webwork view look ups to be some like view.CreateIssue.none and then chomp the view. bit later so that the other configurators can skip them!