Re: JEP 110 - Violating Naming Convention ?

2016-08-17 Thread Rahman USTA
There is a JaxRS-Client API sample here; String entity = client.target("http://example.com/rest";) .register(FilterForExampleCom.class) .path("resource/helloworld") .queryParam("greeting", "Hi World!") .request(MediaType.TEXT_PLAIN_TYPE)

Re: JEP 110 - Violating Naming Convention ?

2016-08-17 Thread Bernd Eckenfels
Hello I think .get() or .put() would look even strange. With all uppercase it is rather clear its an HTTP/2 method keyword. Gruss Bernd Am Wed, 17 Aug 2016 16:51:18 +0300 schrieb Rahman USTA : > Thank you Pavel, this uncommon usage looks to me very weird. > > I hope it could be re-evaluated ag

Re: JEP 110 - Violating Naming Convention ?

2016-08-17 Thread Simone Bordet
Hi, On Wed, Aug 17, 2016 at 3:51 PM, Rahman USTA wrote: > Thank you Pavel, this uncommon usage looks to me very weird. The GET() method is a shortcut to send the request with the HTTP "GET" method, hence the upper case. Equivalent to request.method("GET"). It's not a classic getter method, and

Re: JEP 110 - Violating Naming Convention ?

2016-08-17 Thread Rahman USTA
Thank you Pavel, this uncommon usage looks to me very weird. I hope it could be re-evaluated again. Thanks 2016-08-17 16:29 GMT+03:00 Pavel Rappo : > The correct mailing list for issues in java.net area would be > net-dev@openjdk.java.net > > IMO, these conventions are just guidelines. One can

Re: JEP 110 - Violating Naming Convention ?

2016-08-17 Thread Pavel Rappo
The correct mailing list for issues in java.net area would be net-dev@openjdk.java.net IMO, these conventions are just guidelines. One can override them in some circumstances where it makes a lot of sense. Yes, the barrier for violations should be high. I believe this is one of the cases. > On 17

Re: RFR 8146602: jdk/test/sun/misc/URLClassPath/ClassnameCharTest.java test fails with NullPointerException

2016-08-17 Thread Daniel Fuchs
+1 -- daniel On 16/08/16 16:35, Svetlana Nikandrova wrote: Hello, please review this test update. Test do not consider that exception could happen while variable "server" is not initialized yet. As a result log shows NPE instead of the real exception which is irrecoverably lost. I added check