@AT
> For the record, I just started to work on a transcription of the
> recording. It's a bit more difficult and time consuming than I
> anticipated, but I hope to finish it soon and will post it here then.
Much appreciated ;)
@EB
> For my money, I think Kito's
> "JSON Rendering" one is a great one to start with.
This is next to native push support also one of most commonly requested
features from the community side. Particularly if it's possible to obtain
and process it via native XHR and libs like jQuery. Lot of starters are
clueless stabbing around in jsf.ajax.request() in order to figure how to
get exactly the XML response they need.
Further it would be great to have the possibility to reduce .taglib.xml
boilerplate to a minimum as described in Arjan's blog
http://arjan-tijms.omnifaces.org/2014/07/jsf-23-wish-list-part-i-components.html.
The community seems to underestimate the power and usefulness of taglibs.
Starters are driven away to composite components because of their
zero-configuration nature. Composites are too often abused for tasks which
clearly needs to be done with includes or tagfiles, which ultimately ends
up in relatively inefficient code. Starters do not seem to see/understand
that a composite is really only useful whenever you want to bind a single
model property to a bunch of closely related components (this might perhaps
also be better clarified in docs and tutorials). If we can reduce the
required .taglib.xml boilerplate to a minimum, preferably zero, then the
community may rediscover the power of taglibs and end up developing more
efficient templates/tags.
Cheers, Bauke
On Mon, Oct 13, 2014 at 5:59 PM, Edward Burns <edward.burns_at_oracle.com>
wrote:
> >>>>> On Mon, 13 Oct 2014 08:00:05 -0500, Josh Juneau <juneau001_at_gmail.com>
> said:
>
> JJ> I listened to the audio from the expert group meeting at
> JJ> JavaOne. [...] I was happy to hear that there are others (Neil in
> JJ> particular) that also would like to see at least one big ticket item
> JJ> for JSF 2.3.
>
> JJ> I feel that it is important to have at least one feature that will
> catch
> JJ> the attention of the community [...]
>
> JJ> Maybe the big feature could be the "decorate response" phase that was
> JJ> mentioned in the meeting, or even "increased support for HTTP 2.0",
> JJ> covering the dispatch priority concerns. Perhaps better integration
> with
> JJ> single-page frameworks, as addressed in Ian's presentation?
>
> Hello Josh,
>
> Thanks for taking the time to listen to the audio. Were you at the BOF
> Monday night? If not, you may want to take a look at my slides for our
> JSF 2.3 BOF, which I have linked from a blog entry [1]. Ian Hlavats's
> informative slides are linked from there. Your email gives me a good
> opportunity to recap the administrative content from the BOF here on the
> list.
>
> The most important goal for the BOF was to state that there are two
> feature engines for JSF 2.3, each with different agendas and
> capabilities (some of which overlap).
>
> * Oracle Driven Features
>
> These features will be characterized by having stability, performance,
> and platform integration as their goal. Examples of this category of
> feature include
>
> 1316-_at_InjectOnJSFArtifacts
>
> 1321-LeverageHTTP2ServerPush
>
> 1-MultiComponentValidation (with Bean Validation)
>
> * Community Driven Features
>
> Kito's "JSON Rendering" feature
>
> Ian's "Twitter Bootstrap support" feature
>
> Ian's "RenderKits that target AngularJS directives"
>
> Josh, you're right about the need to draw people in with new features.
> While it's hard to argue that any of the individual features in the
> "Oracle Driven" category are compelling, taken together, they
> do have a very big impact in increasing the appeal of JSF for
> developers. We've been getting comments about the need to take time to
> tighten up the loose ends for many releases now. It's time to sit down
> and take action on those comments.
>
> I would like Arjan to lead a discussion here to find the single highest
> impact/least effort new feature in the "Community Driven"
> category. Let's take these one at a time. For my money, I think Kito's
> "JSON Rendering" one is a great one to start with.
>
> Even if we have no success with the Community Driven Features, we still
> have 1321-LeverageHTTP2ServerPush as a fallback.
>
> Ed
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | 19 work days til Devoxx 2014
>
>