--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> On 6/14/07, Peter Reilly
> <[EMAIL PROTECTED]> wrote:
> > interface SetPropertyResolver {
> > boolean setProperty(Project a, String
> property, String value)
> > returns true if property consumed
> > return false if not
> > }
>
> I don't understand the SetPropertyResolver aspect. I
> like the GetPR,
> although I'd call it PropertyEvaluator maybe, or
> PropertyExpander, but
> I don't get the Set part. How would that be used?
> The GetPR comes into
> play in a ${scheme:...} expansion, but how would the
> SetPR work? --DD
>
On further reflection, the Set* interface does make
sense, but only as an extension to the Get* interface.
This would be the correct way to set anything that
couldn't be stuffed into the basic String-to-Object
property map (whatever that might be) and would imply
that the entity in question could get anything it
could set. This also implies that the existing
namespace concept that exists but is unused in
PropertyHelper needs to go away. The
setter-that-can-get would parse its own
pseudo-namespace if applicable. Since this would
extend the Get version, I would think it could wait
until the main two interfaces were handled.
-Matt
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
