I think this is the case when me might choose follow the spec
Most likely we will not break existing applications if we weaken
requirements for method arguments. But advanced users would be able
to use our benefits.
Thanks,
Mikhail
2006/3/30, Paulex Yang [EMAIL PROTECTED]:
Hi,
About the
On 3/30/06, Mikhail Loenko [EMAIL PROTECTED] wrote:
I think this is the case when me might choose follow the spec
Most likely we will not break existing applications if we weaken
requirements for method arguments. But advanced users would be able
to use our benefits.
+1
--
Anton Avtamonov,
Mikhail Loenko wrote:
I think this is the case when me might choose follow the spec
+1. I think it's a bug of RI.
Most likely we will not break existing applications if we weaken
requirements for method arguments. But advanced users would be able
to use our benefits.
Thanks,
Mikhail
+1
Mikhail Loenko wrote:
I think this is the case when me might choose follow the spec
Most likely we will not break existing applications if we weaken
requirements for method arguments. But advanced users would be able
to use our benefits.
Thanks,
Mikhail
2006/3/30, Paulex Yang
+1
Mikhail Loenko wrote:
I think this is the case when me might choose follow the spec
Most likely we will not break existing applications if we weaken
requirements for method arguments. But advanced users would be able
to use our benefits.
Thanks,
Mikhail
2006/3/30, Paulex Yang [EMAIL
Hi,
About the Internet proxy properties, the Java 5 document says '*' can be
used as wild card character for matching, as below
http.nonProxyHosts indicates the hosts which should be connected too
directly and not through the proxy server. The value can be a list of
hosts, each seperated by
