hi eduardo,
if so: please file the corresponding jira-ticket/s.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2013/10/30 Contrib gcont...@cibinetonline.com
There
Hey guys, I understand some of the frustration, but MyFaces 2.1 and Trinidad
2.0 is an invalid configuration. Why would a release of Trinidad 2.1 (which is
designed for JSF 2.1) not solve this issue.
--
Scott O'Bryan
Sent with Airmail
On October 30, 2013 at 1:28:20 AM, Gerhard Petracek
hi scott,
yes - that isn't a big issue (even though the reason for it is quite
questionable, if you consider the changes in jsf 2.1).
however, i'm more concerned about the implication of the topics i mentioned
earlier.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE
Gerhard and Devs,
The problem is there was some 2.1 stuff added to the ExternalContext I believe.
At any rate, I agree with you and I've managed to free up some free time to
get a release. So here is what I suggest:
1) I'm going to begin the release of the Trinidad plugins. With voting this
@ExternalContext:
there shouldn't be an issue due to ExternalContextWrapper.
in any case +1 for the rest.
regards,
gerhard
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2013/10/30
That's only if you are wrapping another ExternalContext. If you need to create
an ExternalContext out of thin air, then any new abstract methods are a
problem. Essentially, the JSF specification made an incompatible api change
between JSF 2.0 and 2.1.
-- Blake Sullivan
On Oct 30, 2013, at
hi blake,
many other libs don't have an issue with using the std. wrapper approach
(+ ExternalContextWrapper).
- without concrete details we can't follow, since ExternalContextWrapper
was introduced for keeping libs as stable/compatible as possible (across
spec. revisions).
regards,
gerhard
Gerhard, what he's saying is that we have several cases that require a base
implementation. Mostly they are for cases that are outside of the JSF
lifecycle. It MAY be possible to retrofit these cases with the
ExternalContextFactory and the wrapper, but this work hasn't been done yet.
--
I assume that the specific issue is when Trinidad is using the ExternalContext
as an api to hide Servlet vs. Portlet differences BEFORE the FacesContext is
created. In these cases, Trinidad needs to create concrete ExternalContext
implementations for Servlets and Portlets. An example of this
i guess it's quite specific to trinidad and other libs with similar
requirements just use a different approach (and/or abstraction) to do the
same.
now it's clear what was done (and the reason for it), however, as we see
there are clear limitations once you are doing it that way.
regards,
gerhard
There are some bugfixes on MyFaces 2.1, and projects having Trinidad 2.0
as part of the stack, cannot update it due this.
Regards,
Eduardo
El 28/10/13 10:09, Gerhard Petracek escribió:
it isn't only about one release.
e.g. 2.1.0 was just skipped and at least a part is broken since months
it isn't only about one release.
e.g. 2.1.0 was just skipped and at least a part is broken since months (see
[1] and [2]).
therefore i called this thread trinidad.next instead of trinidad 2.1.1.
imo:
the current situation isn't acceptable for users.
committers who work on trinidad on a regular
Am 17.10.13 22:47, schrieb Gerhard Petracek:
hi @ all,
we haven't seen a trinidad release for almost 20 months.
it's known that other projects are based on trinidad and therefore it's
obvious that they have to use snapshot versions.
imo:
since there are commits on a regular basis, there should
+1 for a release too.
On Fri, Oct 18, 2013 at 2:12 PM, Werner Punz werner.p...@gmail.com wrote:
Am 17.10.13 22:47, schrieb Gerhard Petracek:
hi @ all,
we haven't seen a trinidad release for almost 20 months.
it's known that other projects are based on trinidad and therefore it's
obvious
hi @ all,
we haven't seen a trinidad release for almost 20 months.
it's known that other projects are based on trinidad and therefore it's
obvious that they have to use snapshot versions.
imo:
since there are commits on a regular basis, there should be also releases
on a regular basis.
regards,
15 matches
Mail list logo
