Olivier Ledru

Congratulations,

And I agree, the K&B book is the one to study !

Both reduce Network traffic, but not the same way.
Transfert Object reduce it by sending a bundle of data in one remote call, instead of having several small remote call.
Service Locator reduce it by "caching" high-cost resource (like JNDI resource).

The answer is definitely Service Locator to me.
[ June 06, 2008: Message edited by: Olivier Ledru ]

Hello,

I pass SCJP5.0 yesterday, with 81%.
I study about 1 month with the Sierra/Bates book and the free examulator and inquisition test.
And now, see SCWCD...

Thanks for your support ;-)
[ June 06, 2008: Message edited by: Olivier Ledru ]

In the real life, your beans have getter and setter, and your class is thightly encapsulated, but using the setter of your bean, you can change its internal state, so your bean has not to be immutable. Actually, it generally isn't immutable.

Well, after reading http://java.sun.com/j2se/1.5.0/docs/api/java/util/Arrays.html#asList(T...) ,
Why int[] is not read as 'int...' but Integer[] is read as 'Integer...' ?
Nothing in the API point any difference on this.
Did I miss something ?

Hi,
Just wonder why Arrays.asList() has this behavior when passing an int[] !?
Why asList take it as a single Object, and not as a regular array ?!
import java.util.Arrays; import java.util.List; import junit.framework.TestCase; public class TestArrays extends TestCase { public void testAsList() { System.out.println("testAsList()"); List<Integer> listAnonymInteger = Arrays.asList( 1, 2, 3, 4 ); assertTrue(4 == listAnonymInteger.size()); List listAnonym = Arrays.asList( 1, 2, 3, 4 ); assertTrue(4 == listAnonym.size()); int[] arrayInt = new int[] {1,2,3,4}; assertTrue(1 == Arrays.asList(arrayInt).size()); Integer[] arrayInteger = new Integer[] {1,2,3,4}; assertTrue(4 == Arrays.asList(arrayInteger).size()); } }