rather large.
Or is this too much change now?
Stephen
--
John Yu Scioworks Technologies
e: [EMAIL PROTECTED] w: +(65) 873 5989
w: http://www.scioworks.com m: +(65) 9782 9610
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail
would not fulfill it, even if the
functionality were the same.
My vague view being that things can be syntactically the same but
semantically different.
You lost me.
Could you elaborate? What semantics you're referring to in Pair?
--
John Yu
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED
Steve,
At 04:48 am 13-10-2002, you wrote:
On Friday 11 October 2002 07:49 pm, Henri Yandell wrote:
On Fri, 11 Oct 2002, Steve Downey wrote:
2) Mutable primitive classes. Pondered this at the hospital today. Do
we want such things? new MutableInteger(); mi.setValue(42); etc. Same
At 12:21 am 12-10-2002, you wrote:
Has anyone thought of implementing Digester type functionality using the
DOM API?
Just curious: why does one need that?
--
John Yu
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
+1 on adding a new subproject.
-0 on calling it reflection.
Calling it reflection will be a bit misleading as it implies
java.lang.reflect. But what has been discussed so far is more than simply
providing a thin utils on the top of java.lang.reflect.
I'd suggest something like Meta-Prog,
(MyClass.class, name, fName,
setNameWithValidation);
BeanInfoUtils.expose(MyClass.class, age, fAge, fAge);
}
private void setNameWithValidation(String name) {..}
}
Then, the properties can be accessed by PropertyUtils:
PropertyUtils.setProperty(myObj, name, John Yu
) {..}
}
Then, the properties can be accessed by PropertyUtils:
PropertyUtils.setProperty(myObj, name, John Yu);
PropertyUtils.setProperty(myObj, age, new Integer(42));
Comment?
--
John
At 03:02 am 04-10-2002, you wrote:
Steve Downey wrote:
From
http://msdn.microsoft.com/library/en-us/dndevqa/html
has addressed (partly?) the last issue that
CallMethodRule didn't work correctly in nested situation.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
John Yu
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional
an explict
bijection class (extends Map) that supports this functionality than a
MapUtils method that is only meaningful for a subset of Maps.
What do you think?
--
John Yu Scioworks Technologies
e: [EMAIL PROTECTED] w: +(65) 873 5989
w: http://www.scioworks.com m
swaps meaningful (e.g., duplicate keys the
destination map point to a *set* of values), or that happens to change the
behavior in the non-bijection case.
--
John Yu
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
}
}
}
Besides, I have a modified SoftRefHashMap version which does more efficient
purging by using the java.lang.ref.ReferenceQueue, similar to what
java.util.WeakHashMap does. Should I post the modification to the mailing list?
--
John Yu Scioworks Technologies
e: [EMAIL
.
In principle, (1) and (2) are orthogonal. In practice, however,
implementation of (2) usually uses (1) to manage the schema/metadata.
--
John Yu Scioworks Technologies
e: [EMAIL PROTECTED] w: +(65) 873 5989
w: http://www.scioworks.com m: +(65) 9782 9610
Scioworks
12 matches
Mail list logo
