Bill/all,
When you say "our management console", is that the one of WildFly since the
relaunch under the new name?
JSF per se doesn't make the whole MVC framework, you always have to take
implementations or component libraries into consideration.
One or two versions before WildFly we had EAP 5.x and the server that's
part of this bundle in our DevOps infrastructure at the client back then,
and one of the internal projects ("tenants" if you want) required to use
another JSF implementation in parallel for JRules or something similar. I
can tell you isolating the two from each other wasn't fun, but I'd say it
is a bit more on the middle tier or container side to solve these kinds of
problems. Java EE 8 and possible ingredients like the Config API might
help;-)
As for "Ajax" of HTML5/JavaScript support, the Portlet 3 standard (JSR 362)
has even a bit more JavaScript there now, too, but it won't aim to create
another "MVC Framework" or competition to JSF either. Many portals use JSF
but it's not a precondition to use JSF for a Portlet container.
So a sensitive level of support for these "Ajax" needs looks good for other
JSRs like JAXRS, too.
And yes, I'm also among those who used JavaScript and J2EE as it was first
called for ~15 years now, but not all of it has changed so drastically just
because they found new fancy names for it like "Ajax", "Spring" or "Play";-D
Regards,
Werner
On Thu, Aug 7, 2014 at 11:15 AM, <users-request_at_jax-rs-spec.java.net> wrote:
> Table of contents:
>
> 1. [jax-rs-spec users] Re: HTMLEasy - Marek Potociar <
> marek.potociar_at_oracle.com>
> 2. [jax-rs-spec users] Re: HTMLEasy - Bill Burke <bburke_at_redhat.com>
>
>
>
> ---------- Forwarded message ----------
> From: Marek Potociar <marek.potociar_at_oracle.com>
> To: Bill Burke <bburke_at_redhat.com>
> Cc: Santiago Pericas-Geertsen <santiago.pericasgeertsen_at_oracle.com>,
> users_at_jax-rs-spec.java.net
> Date: Wed, 6 Aug 2014 17:38:49 +0200
> Subject: [jax-rs-spec users] Re: HTMLEasy
> Hi Bill,
>
> Since you seem to have a very strong opinion on the subject, perhaps you
> want to provide the RedHat point of view here? :)
>
> Thanks,
> Marek
>
> On 22 Jul 2014, at 19:14, Frans Thamura <frans_at_meruvian.org> wrote:
>
> > several time ago there are discussion regarding JAXRS like MVC
> >
> > and there is htmleasy for resteasy
> >
> > https://code.google.com/p/htmleasy/
> >
> > will this feature part of JAXRS future?
> >
> > F
>
>
>
> ---------- Forwarded message ----------
> From: Bill Burke <bburke_at_redhat.com>
> To: Marek Potociar <marek.potociar_at_oracle.com>
> Cc: Santiago Pericas-Geertsen <santiago.pericasgeertsen_at_oracle.com>,
> users_at_jax-rs-spec.java.net
> Date: Wed, 06 Aug 2014 12:14:24 -0400
> Subject: [jax-rs-spec users] Re: HTMLEasy
> I didn't write this HTMLEasy framework.
>
> As I've already stated, I'm strongly against any new MVC framework in
> JAX-RS, or in Java EE. We have enough popular ones already:
>
> * JSF
> * Struts
> * Tapestry
> * Spring MVC
> * Play
> * Seam
>
> JAX-RS was designed for stateless REST APIs. Once you start getting into
> MVC you have to worry about HTTP session state and propagating this
> information.
>
> Plus as I said before, apps are moving to Pure Javascript/HTML5 with
> frameworks like Angular JS and GWT that are making simple REST calls to the
> backend. This is the approach we took for our management console in the
> latest project I've been working on and it was marvelous.
>
> IMO, the only thing JAX-RS should do would be to add features to help
> support external MVC frameworks, i.e.:
>
> * propagating properties from jaxrs resource mehtods to
> interceptors/filters
> * propagating atributes from jax-rs methods to and from HttpServletRequest
> and ServletContext
> * Forwarding requests.
>
> Anything beyond that would be a big mistake. These types of things tend
> to grow and bloat over time. Once an MVC framework is introduced to
> JAX-RS, I predict it will eventually evolve to compete against JSF. This is
> bad for Java EE. Also, MVC is a very personal preference. New ones pop up
> all the time, are popular for awhile then fade away. I just don't want to
> have yet another API that nobody uses and that I have to implement and
> support for years to come.
>
> You have to remember I've been doing this Java EE thing for a long long
> time. 12 years now. Maybe I'm a miserable old fart/dinosaur or maybe I've
> gained a little wisdom. :)
>
> On 8/6/2014 11:38 AM, Marek Potociar wrote:
>
>> Hi Bill,
>>
>> Since you seem to have a very strong opinion on the subject, perhaps you
>> want to provide the RedHat point of view here? :)
>>
>> Thanks,
>> Marek
>>
>> On 22 Jul 2014, at 19:14, Frans Thamura <frans_at_meruvian.org> wrote:
>>
>> several time ago there are discussion regarding JAXRS like MVC
>>>
>>> and there is htmleasy for resteasy
>>>
>>> https://code.google.com/p/htmleasy/
>>>
>>> will this feature part of JAXRS future?
>>>
>>> F
>>>
>>
>>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
>
> End of digest for list users_at_jax-rs-spec.java.net - Thu, 07 Aug 2014
>
>