We could use a little help on this one, guys :)
tia
Phil
On Wed, Dec 29, 2010 at 1:59 PM, Simone Tripodi wrote:
> Hi all mates,
> since JMX is not a technology I'm expert, since MBean interfaces were
> recently added, I'd like to know how to test this kind of support.
> Many thanks in advance, a
That is correct. Some of the commons libraries have existed for a long time,
and they are written to work with older JRE versions for backward
compatibility. Newer releases are written for newer JREs.
-Adrian
--- On Wed, 12/29/10, Michael Giannakopoulos wrote:
> Hello Andrian,
>
> Thanks for
Hello Andrian,
Thanks for the quick and effective reply... Say we changed the files so as
to apply to the standard of JRE 1.6... Then Apache Commons Library would
became broken as far as the previous versions of JRE are concerned?
The project was written for a JRE earlier than 1.5. Change your Eclipse
project settings to use a compiler prior to 1.5.
-Adrian
On 12/29/2010 12:18 PM, Michael Giannakopoulos wrote:
Hello to all of you guys,
I would like to ask a trivial for most of you question... As i see the
source code in
Hello to all of you guys,
I would like to ask a trivial for most of you question... As i see the
source code in Eclipse is full of warnings because IDE is complaining that
references to generic types should be parameterized... Wouldn't it be more
correct if we add to all generic types after their
Hi all mates,
since JMX is not a technology I'm expert, since MBean interfaces were
recently added, I'd like to know how to test this kind of support.
Many thanks in advance, all the best,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
---
Hello everybody.
I did a microbenchmark comparing a hardcoded synchronization wrapper
with the proposed dynamic proxy-based one (which is very elegant IMHO
and it proves that Java has a surprising amount of meta-programming
facilities in it). The comparison was done on a Map instance using
C
