I am very much surprised after reading your mail. I don't have the
feeling that Trinidad is stagnating, at least we use it more and more
ourselves. And as I have no idea about the rich client I cannot
comment on that, but Trinidad development should not depend on such a
project, on the contrary.
Red schrieb:
Hello.
I decided to upgrade to MyFaces 1.2.4 (from 1.1.something) today, and I
noticed something odd - some of my converters stopped working. I traced
the problem to ApplicationImpl.internalCreateConverter, which appears to
have a bug.
My converter is bound in faces-config.xml to
Hi!
This used to work in MyFaces 1.1, but in 1.2 it looks like the fact that
my type is an enum takes precedence over the fact that it implements
EnumCoded interface, so I end up with the built-in EnumConverter instead
of my GenericEnumTypeConverter.
Of course this issue was not relevant in
Hi Andrew, Bruno,
the mail was pretty long, and raised some interesting points, but I
honestly don't think adding another component library to MyFaces will
help. What we should really do is consolidation - if we can work into
this direction, we will have more success as a group.
On Sun, Sep 28, 2008 at 7:35 PM, Simon Lessard
[EMAIL PROTECTED] wrote:
Hi all,
As of JSF 2.0, it's possible to have a ResourceBundle associated to an
UIComponent. This is reflected in the API with the method:
public MapString, String getResourceBundleMap()
However, this method, as you can
Update:
Somehow I royally messed up the Jira query and re-ran it this morning.
There are 285 issues that were either improvement, wish or new feature
requests that have been made to Trinidad.
After thinking more about this email, I should have taken a different
approach. After mulling it over
I had no a good chance to complete read you past email, since I am sick today.
Some comments inline
On Mon, Sep 29, 2008 at 4:57 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
Update:
Somehow I royally messed up the Jira query and re-ran it this morning.
There are 285 issues that were either
It's been about a month since I posted the previous message, any
thoughts on the questions?
Is there a workaround for Trinidad-73? Currently, it doesn't take too
many users to crash Tomcat when we hit the maximum open files per
process limit in z-Linux.
Thank you,
Ed
On 8/25/08, Edward
I think this is really want I want to get at. For me to see no
progress for over 6 months on many issues, not see people's patches
applied, etc., is disheartening. I am part to blame and should also be
helping close some of these issues.
it is all a matter of time... so why not sending more
Hi Ed,
there will be a release by end of October, that contains the fix.
Is it possible for you to test against a pretty recent snapshot of 1.2.10 ?
(or against 1.1.10 if you are on the JSF 1.1 side):
Hi Paul,
Thanks for the link, it makes the whole thing clearer. However, is that
point still debatable? I quite disagree about the conclusion about forcing
the upgrade of the core if you upgrade Tomahawk. Upgrading Tomahawk might
force the upgrade of shared, but not necessarily if the former
On Mon, Sep 29, 2008 at 5:56 PM, Edward Dowgiallo [EMAIL PROTECTED] wrote:
I can't get any of the releases imported to our development system
until they go 'production' on the Apache site. I will try out the
I understand that.
snapshot at home.
that was what I tried to say ;-) Try them at the
BTW, for anyone that hasn't read this ridiculously long and dumb
thread, feel free to hit delete.
I think the best thing is for me to shut up and just start committing
fixes to the bugs that have been open for a long time instead of
making any criticism against the community.
Sorry for all the
On Mon, Sep 29, 2008 at 6:00 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
BTW, for anyone that hasn't read this ridiculously long and dumb
thread, feel free to hit delete.
I think the best thing is for me to shut up and just start committing
fixes to the bugs that have been open for a long
sheet paging should adjust scroll position
--
Key: TOBAGO-703
URL: https://issues.apache.org/jira/browse/TOBAGO-703
Project: MyFaces Tobago
Issue Type: Bug
Components: Themes
Affects
Hi,
The UIX issue is a very valid one indeed and so few link to it remains, it's
a shame that we didn't get rid of it already and I'm to blame a lot for that
because I started it a long time ago but was never able to finish it.
However, as Matthias pointed out, JSF 2.0 standardize Trinidad's
Forgot to mention that conversation scope is getting standardized by
JSR-299, Web Beans so most of Trinidad's features are getting standardized
and personally it drains a part of my motivation to improve the existing
code for those modules knowing it might have to be re-refactored so soon.
~
However, as Matthias pointed out, JSF 2.0 standardize Trinidad's principal
core features namely PPR and Resource handling and hopefully skinning too.
Under such circumstances, I feel that we should wait for 2.0 to be cemented
before going through a massive refactoring of some of the old and
Hi Andrew,
Yes I think Adam made a wiki for UIXNode conversion during the time of
incubation, I'll have to look for the link.
As for JSF 2.0 adoption, I would say 2 years after the specification release
which is... not so soon. Implementation will start before that though and I
think it's what
I'd rather fully agree than gully agree though. :)
On Mon, Sep 29, 2008 at 1:46 PM, Simon Lessard [EMAIL PROTECTED]wrote:
Hi Andrew,
Yes I think Adam made a wiki for UIXNode conversion during the time of
incubation, I'll have to look for the link.
As for JSF 2.0 adoption, I would say 2
On Mon, Sep 29, 2008 at 7:46 PM, Simon Lessard
[EMAIL PROTECTED] wrote:
Hi Andrew,
Yes I think Adam made a wiki for UIXNode conversion during the time of
incubation, I'll have to look for the link.
As for JSF 2.0 adoption, I would say 2 years after the specification release
which is... not
also, the sandbox renderer approach sounds good so far.
However, you should ensure we don't break a lot of things
-Matthias
On Mon, Sep 29, 2008 at 7:53 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On Mon, Sep 29, 2008 at 7:46 PM, Simon Lessard
[EMAIL PROTECTED] wrote:
Hi Andrew,
Yes I
returnListener not called from manually launched dialog.
Key: TRINIDAD-1244
URL: https://issues.apache.org/jira/browse/TRINIDAD-1244
Project: MyFaces Trinidad
Issue Type: Bug
In GuiceResolver managed-bean-scope is ignored, scope defaults to none
--
Key: MYFACES-1999
URL: https://issues.apache.org/jira/browse/MYFACES-1999
Project: MyFaces Core
24 matches
Mail list logo