struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34714] - [Shale] Clay PropUtil.setProperty should not fail silently if the property could not be set.
Date Tue, 03 May 2005 17:51:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34714>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34714





------- Additional Comments From manklu@web.de  2005-05-03 19:51 -------
(In reply to comment #4)
> Good point.  Maybe this parameter name should be configurable through an 
> initialization  parameter in the web deployment descriptor where the default 
> is "allowBody".
> 
> The change would effect several of the Builders. The ConfigBeanFactory might 
> be a good place to make it available.  It could be set by the 
> ClayConfigureListener.
> 
> What do you think?

I think this would still be not optimal. Suppose the following scenario:

A developer receives Clay component definitions from different sources and
wants to assemble dialogues. But there is a big problem. Developer A has used
'allowBody', developer B 'myAllowBody' and so on.

I see currently only two solutions to avoid that problem:

1. Define the special attribute names per file.
2. Remove the special attribute names and use independent tags.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message