http://permalink.gmane.org/gmane.comp.java.jsr311.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.java.jsr311.user/89 <pre>JSR311 itself does not implement any encryption. Martin On 1.4.2011 19:57, Stephan Koops wrote: </pre> Martin Matula 2011-04-03T19:45:41 http://permalink.gmane.org/gmane.comp.java.jsr311.user/88 <pre>Hi Marco, I don't know what you exactly mean, but if you use https, than you have encryption. best regards Stephan </pre> Stephan Koops 2011-04-01T17:57:14 http://permalink.gmane.org/gmane.comp.java.jsr311.user/87 <pre>Hi On Wed, Mar 30, 2011 at 1:09 PM, &lt;marko.miettinen-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: Cheers, Sergey </pre> Sergey Beryozkin 2011-03-30T12:53:45 http://permalink.gmane.org/gmane.comp.java.jsr311.user/86 <pre>Hi, After unsuccessfully searching the forum and mailing lists, I decided to post my questions here: 1) Does JRS311 contain/make use of any encryption? 2) If yes, is anyone aware if an ECCN code has been assigned? From source code, I would think that answer to question #1 would be no. Thanks in advance for any answers. -Marko </pre> marko.miettinen-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org 2011-03-30T12:09:49 http://permalink.gmane.org/gmane.comp.java.jsr311.user/85 <pre> Begin forwarded message: </pre> Paul Sandoz 2011-01-26T10:36:10 http://permalink.gmane.org/gmane.comp.java.jsr311.user/84 <pre> Begin forwarded message: </pre> Paul Sandoz 2011-01-12T08:22:37 http://permalink.gmane.org/gmane.comp.java.jsr311.user/83 <pre>Hi Sergey, On Jan 7, 2011, at 6:14 PM, Sergey Beryozkin wrote: I think you are conflating two things: 1) the contextual encoding of literal characters; and 2) the encoding of parameter values. Calls to queryParam/replaceQuery are associated with 1 and calls to build/buildFromEncoded are associated with 2. Thus the following must produce equivalent URI values: 1. UriBuilder.fromUri("http://localhost:8080").queryParam("name", "%20").build(); 2. UriBuilder.fromUri("http://localhost:8080").queryParam("name", "%20").buildFromEncoded(); 3. UriBuilder.fromUri("http://localhost:8080").replaceQuery("name= %20").build(); 4. UriBuilder.fromUri("http://localhost:8080").replaceQuery("name= %20").buildFromEncoded(); (i.e. like what Jersey does :-) ) The difference occurs when parameter names in queryParam/replaceQuery and corresponding parameter values in build/buildFromEncoded are declared. The following: 1. UriBuilder.fromUri("http://localhost:8080").queryParam("name", "{va</pre> Paul Sandoz 2011-01-10T08:30:31 http://permalink.gmane.org/gmane.comp.java.jsr311.user/82 <pre> The reason why we decided that "build" does not contextually encode parameter values is parameter values might originate from other sources e.g. a DB or HTML forms etc. where the intention is that these things cannot be contextually encoded. If you are being "literal" then we considered it sufficient to do contextual encoded. It is not encouraged to do string concatenation to stuff values into a URI. Paul.</pre> Paul Sandoz 2011-01-10T15:57:04 http://permalink.gmane.org/gmane.comp.java.jsr311.user/81 <pre>Hi Paul It does help, thanks. Please see the comments inline On Mon, Jan 10, 2011 at 8:30 AM, Paul Sandoz &lt;Paul.Sandoz-QHcLZuEGTsvQT0dZR+AlfA&lt; at &gt;public.gmane.org&gt; wrote: It does clarify everything. And I think I finally can see what actually I'm confused about. Sorry I don't quire recall why I thought the handling of queryParam was done differently to replaceQuery, I think I hit some issue while working with the TCK - I'll update as soon as I recall what was it... Please look at these two examples, using path calls, just for some difference : 1. UriBuilder.fromUri("http://localhost:8080 ").path("name/{value}").path("%20").build("%20"); will output http://localhost:8080/name/%2520/%20 &lt;http://localhost:8080/?name=%2520&gt; 2. UriBuilder.fromUri("http://localhost:8080 ").path("name/%20").path("%20").build(); will output http://localhost:8080/name/%20/%20 &lt;http://localhost:8080/?name=%2520&gt; 3. UriBuilder.fromUri("http://localhost:8080 ").path("name/{value}").path("%20").buildFromEncoded("%20"); will</pre> Sergey Beryozkin 2011-01-10T15:19:10 http://permalink.gmane.org/gmane.comp.java.jsr311.user/80 <pre>Hi Paul Many thanks for finding the time to reply and apologies for the the very late reply... I do believe what you're saying below makes sense to me :-), but I'm still not following why a '%' specified as part of queryParam() calls is not double-encoded; however when it is passed as part of replaceQuery() calls the it is double encoded. What I'm trying to say that irrespectively of how the query part of a given URI has been built, whether using say 5 queryParam calls or using a single replaceQuery() call, the end result should be the same Cheers, Sergey On Wed, Oct 20, 2010 at 9:17 AM, Paul Sandoz &lt;Paul.Sandoz-QHcLZuEGTsvQT0dZR+AlfA&lt; at &gt;public.gmane.org&gt; wrote: </pre> Sergey Beryozkin 2011-01-07T17:14:56 http://permalink.gmane.org/gmane.comp.java.jsr311.user/79 <pre></pre> Edward Bratt 2010-12-10T20:39:21 http://permalink.gmane.org/gmane.comp.java.jsr311.user/78 <pre>This project will be migrated to Kenai in the wave-2 migration effort. This project will be locked, starting at 10 PM Pacific Standard Time, Sunday November. 21. We will work to unlock this project as soon as possible however, we cannot predict the exact schedule for importing projects into Kenai. The whole effort is expected to take about two weeks, possibly three. Projects will be activated at [project].java.net as soon as all data are imported into Kenai. Please watch http://kenai.com/projects/glassfish-migration/pages/Home for updates regarding progress. If you have any questions about the projects which are going to be migrated, please review the complete list, here &lt;http://kenai.com/projects/glassfish-migration/pages/Wave2Projects&gt;. Actions you should take *User Credentials* If you have not activated your new java.net user credentials, please do that now. (beta.java.net, select login. If you did not receive your welcome e-mail, click "lost password.") *Sync your local source copy* You</pre> Ed Bratt 2010-11-19T19:38:55 http://permalink.gmane.org/gmane.comp.java.jsr311.user/77 <pre>Hello, Assume there is a root resource with &lt; at &gt;Path("/") with a resource method for &lt; at &gt;Path("{path:.*}") and a root resource for &lt; at &gt;Path("/foo") with no method matching the subpath "bar". Is it ok for an implementation to forward the request for /foo/bar to the method of the first root resource or is it necessary to answer with 404? Cheers, Reto </pre> Reto Bachmann-Gmuer 2010-11-07T13:03:08 http://permalink.gmane.org/gmane.comp.java.jsr311.user/76 <pre> Correct. Yes, still here :-) Yes, i replied to the email you sent me personally. Paul.</pre> Paul Sandoz 2010-10-20T08:25:17 http://permalink.gmane.org/gmane.comp.java.jsr311.user/75 <pre>Hi Sergey, The methods "build" and "buildFromEncoded" only apply to the parameter values passed to the method that replace parameter names declared in the strings the builder methods. The JavaDoc of the build method states: Build a URI, using the supplied values in order to replace any URI template parameters. Values are converted to String using their toString method and are then encoded to match the rules of the URI component to which they pertain. All '%' characters in the stringified values will be encoded. The JavaDoc of the buildFromEncoded method states: Build a URI. Any URI templates parameters will be replaced with the supplied values in order. Values are converted to String using their toString method and are then encoded to match the rules of the URI component to which they pertain. All % characters in the stringified values that are not followed by two hexadecimal numbers will be encoded. Note also the JavaDoc of the UriBuilder class: Builder methods perform contextua</pre> Paul Sandoz 2010-10-20T08:17:38 http://permalink.gmane.org/gmane.comp.java.jsr311.user/74 <pre>Hi Sergey, First, please accept my sincere apologies for not replying, it was an email management SNAFU on my part. Next time please, metaphorically, poke me in the ribs, with a direct email if i do not reply in a timely fashion! The encoding rules for query parameter name and values are different to the encoding rules for the query component. There is a "convention" (well it is defined by the HTTP spec in the form section) that for query parameter name and values a ' ' character is encoded as a '+'. That convention should not apply to the encoding rules of the query component. Does that help? Paul. On Aug 23, 2010, at 11:55 PM, Sergey Beryozkin wrote: </pre> Paul Sandoz 2010-10-20T08:07:49 http://permalink.gmane.org/gmane.comp.java.jsr311.user/73 <pre>It looks like Marc Hadley has left Oracle. Is Paul Sandoz still there? We would like to have someone do a large scale presentation for Credit Suisse NY, such as the presentations that Marc and Paul used to do at JavaOne. Is there any potential for that? Thanks, Victor Grazi CreditSuisse VP - Application Development Tel: 212-538-5703 Please follow the attached hyperlink to an important disclosure: http://www.credit-suisse.com/legal/marketcommentary =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html =============================================================================== </pre> Grazi, Victor 2010-10-20T03:52:26 http://permalink.gmane.org/gmane.comp.java.jsr311.user/76 <pre> Correct. Yes, still here :-) Yes, i replied to the email you sent me personally. Paul.</pre> Paul Sandoz 2010-10-20T08:25:17 http://permalink.gmane.org/gmane.comp.java.jsr311.user/75 <pre>Hi Sergey, The methods "build" and "buildFromEncoded" only apply to the parameter values passed to the method that replace parameter names declared in the strings the builder methods. The JavaDoc of the build method states: Build a URI, using the supplied values in order to replace any URI template parameters. Values are converted to String using their toString method and are then encoded to match the rules of the URI component to which they pertain. All '%' characters in the stringified values will be encoded. The JavaDoc of the buildFromEncoded method states: Build a URI. Any URI templates parameters will be replaced with the supplied values in order. Values are converted to String using their toString method and are then encoded to match the rules of the URI component to which they pertain. All % characters in the stringified values that are not followed by two hexadecimal numbers will be encoded. Note also the JavaDoc of the UriBuilder class: Builder methods perform contextua</pre> Paul Sandoz 2010-10-20T08:17:38 http://permalink.gmane.org/gmane.comp.java.jsr311.user/74 <pre>Hi Sergey, First, please accept my sincere apologies for not replying, it was an email management SNAFU on my part. Next time please, metaphorically, poke me in the ribs, with a direct email if i do not reply in a timely fashion! The encoding rules for query parameter name and values are different to the encoding rules for the query component. There is a "convention" (well it is defined by the HTTP spec in the form section) that for query parameter name and values a ' ' character is encoded as a '+'. That convention should not apply to the encoding rules of the query component. Does that help? Paul. On Aug 23, 2010, at 11:55 PM, Sergey Beryozkin wrote: </pre> Paul Sandoz 2010-10-20T08:07:49 http://permalink.gmane.org/gmane.comp.java.jsr311.user/73 <pre>It looks like Marc Hadley has left Oracle. Is Paul Sandoz still there? We would like to have someone do a large scale presentation for Credit Suisse NY, such as the presentations that Marc and Paul used to do at JavaOne. Is there any potential for that? Thanks, Victor Grazi CreditSuisse VP - Application Development Tel: 212-538-5703 Please follow the attached hyperlink to an important disclosure: http://www.credit-suisse.com/legal/marketcommentary =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html =============================================================================== </pre> Grazi, Victor 2010-10-20T03:52:26 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.jsr311.user