commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37713] - [resources] Mesage API additions
Date Tue, 06 Dec 2005 16:31:42 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=37713>.
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=37713





------- Additional Comments From niallp@apache.org  2005-12-06 17:31 -------
(In reply to comment #1)
> The second example always felt strange to me. We are misusing the "key" member
> and setting resource to false, puzzling. 
> If we want to support such a use case I'd prefer to either rename the member 
to
> some name which is applicable to both use cases or add another member (e.g.
> "content") and ensure that only one of both members is set. 

Thanks for the feedback - I agree with you and Craig's original comments that 
this is strange - plus I've thought of another way this could be achieved - 
having a Resources implementation that just returns the key in its content 
retrieval methods.

For now I'll just add the "resourcesName" to the Message API.

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message