jsr372-experts@javaserverfaces-spec-public.java.net

[jsr372-experts] Re: Expert Group Meeting _at_ JavaOne

From: Michael Müller <michael.mueller_at_mueller-bruehl.de>
Date: Mon, 13 Oct 2014 17:01:19 +0200

And what about a more rest-alike mapping
x?id=yyy -> x/yyy
 
-- 
Herzliche Grüße, best regards
Michael Müller
Am 13. Oktober 2014 16:38:33 MESZ, schrieb Josh Juneau <juneau001_at_gmail.com>:
>Glad to see that others agree that we need one or more big ticket items
>for
>JSF 2.3.
>
>I think a native push component using WebSockets is a good idea and
>would
>be well-received by the community.  I also agree that the URL mapping
>idea
>would be quite useful.  That would help in terms of providing
>extension-less URLs...and it seems to fall in line with Arjan's ideas
>around REST-like URLs.  I think we can all agree that any features that
>help to align JSF with HTML5 and REST will be welcomed.
>
>I'm sure Facelets could use some "freshening up"...not sure of any
>ideas
>that come to mind immediately there, but as mentioned it would be good
>to
>do a cross-check of the other templating languages.  I also like
>Arjan's
>post regarding component creation and customization.  Components are
>really
>the bread and butter of JSF, and I think the community would be pleased
>if
>there were increased ease of development and simplification via more
>annotation support, etc. in that area.
>
>Neil, thanks for your update on the "decorate response" idea.
>
>Thanks for your time.
>
>Josh Juneau
>juneau001_at_gmail.com
>http://jj-blogger.blogspot.com
>https://www.apress.com/index.php/author/author/view/id/1866
>
>
>On Mon, Oct 13, 2014 at 8:58 AM, Neil Griffin
><neil.griffin_at_portletfaces.org
>> wrote:
>
>> I did some prototyping with Nashorn and jQuery and the "decorate
>response"
>> idea is probably a no-go for the following reasons:
>>
>> 1) It requires a DOMResponseWriter and the org.w3c.dom Java classes
>are
>> not good enough for JS libraries like jQuery to operate against.
>>
>> 2) DOM manipulation is only one feature offered by JS libraries.
>Features
>> like DOM event handling are not covered in the server-side use-case.
>>
>> 3) Fully decorated HTML can already be achieved by having renderers
>encode
>> more detailed markup.
>>
>> On Oct 13, 2014, at 9:37 AM, Cagatay Civici
><cagatay.civici_at_gmail.com>
>> wrote:
>>
>> Hi,
>>
>> We need 2 or 3 big ticket features in JSF 2.3.
>>
>> My big ticket offer would be related to url mapping.
>>
>> For example app/user/ maps to WEBAPP/pages/userpages/user.xhtml
>>
>> I don't think it is very hard to do in terms of implementation as
>well.
>>
>> Would be good to have a configuration by exception just like the rest
>of
>> Java EE by following a certain convention of mapping.
>>
>> Regards,
>>
>> Cagatay Civici
>> PrimeFaces Lead
>> PrimeTek Informatics
>> www.primefaces.org
>>
>> On Monday 13 October 2014 at 16:22, Bauke Scholtz wrote:
>>
>> Hi,
>>
>> How about a native push component using websockets which is new since
>Java
>> EE 7?
>>
>> Cheers, Bauke
>> On Oct 13, 2014 3:00 PM, "Josh Juneau" <juneau001_at_gmail.com> wrote:
>>
>> I listened to the audio from the expert group meeting at JavaOne.  I
>> apologize again that I could not make it due to one of my talks being
>> scheduled at the same time.  That said, it seemed as though the
>meeting
>> went very well, and I was happy to hear that there are others (Neil
>in
>> particular) that also would like to see at least one big ticket item
>for
>> JSF 2.3.
>>
>> I feel that it is important to have at least one feature that will
>catch
>> the attention of the community...mainly because such features help to
>> maintain the visibility of technologies.  If there are no big ticket
>items
>> in 2.3, then it may be overlooked by some, making it look like JSF is
>> becoming a waning technology...falling to the single-page frameworks,
>or
>> being pushed aside for the MVC initiative.  We all know that JSF is
>still
>> widely used and excellent at what it does, but I think JSF needs to
>remain
>> highly visible with the 2.3 release as the leading server-side web
>> framework for Java EE, especially given that there are a couple of
>years
>> between each release.
>>
>> Maybe the big feature could be the "decorate response" phase that was
>> mentioned in the meeting, or even "increased support for HTTP 2.0",
>> covering the dispatch priority concerns.  Perhaps better integration
>with
>> single-page frameworks, as addressed in Ian's presentation?
>>
>> Thanks for your time, I appreciate it.
>>
>> Josh Juneau
>> juneau001_at_gmail.com
>> http://jj-blogger.blogspot.com
>> https://www.apress.com/index.php/author/author/view/id/1866
>>
>>
>>
>>