True!
...and also the name common is very common... :-)
And therefore not reserved for Apache Commons ...
-M
On 10/31/07, Volker Weber [EMAIL PROTECTED] wrote:
It is a apache commons like project, just not located in commons.apache.org.
If it is named myfaces-jsf-commons it should clear
It is a apache commons like project, just not located in commons.apache.org.
If it is named myfaces-jsf-commons it should clear enough this is a
myfaces project.
And imho it should contain tools, components, ... for jsf users like
apache-commons-beanutils contains java-collection stuff for java
tcs:tree can't get marked node
Key: TOBAGO-527
URL: https://issues.apache.org/jira/browse/TOBAGO-527
Project: MyFaces Tobago
Issue Type: Improvement
Affects Versions: 1.0.13
Reporter: Jens
[
https://issues.apache.org/jira/browse/TOMAHAWK-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539030
]
Navid Mitchell commented on TOMAHAWK-1115:
--
I agree with Andrew. I think it is bad form to make Tomahawk
What are the thoughts about providing a Joda DateTime converter in the
upcoming commons project ?
-M
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Although it'll create a dependency, Joda is great:) so +1.
Cagatay
On 10/31/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
What are the thoughts about providing a Joda DateTime converter in the
upcoming commons project ?
-M
--
Matthias Wessendorf
further stuff:
blog:
+1
Regarding dependencies:
We should be careful about dependencies in jsfcommons. Right.
The Joda converter would be a candidate for an *optional* compile
dependency.
--Manfred
On 10/31/07, Cagatay Civici [EMAIL PROTECTED] wrote:
Although it'll create a dependency, Joda is great:) so +1.
Grins
I give up :) as far as I am concerned call it that (booring!!! :) )
Ron
On 10/31/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
True!
...and also the name common is very common... :-)
And therefore not reserved for Apache Commons ...
-M
On 10/31/07, Volker Weber [EMAIL
Regarding dependencies:
We should be careful about dependencies in jsfcommons. Right.
The Joda converter would be a candidate for an *optional* compile
dependency.
+1
--Manfred
On 10/31/07, Cagatay Civici [EMAIL PROTECTED] wrote:
Although it'll create a dependency, Joda is great:)
I don't see any problem with introducing optional dependencies.
For example, commons-logging is a library that has about half-a-dozen optional
dependencies, one for each concrete logging library that it has built-in
support for. This causes no problems at all AFAIK.
The only thing to look out
Nice,
this converter can be easily moved over to the JSF2.0 API,
in case they want support the new DateTime JSR (310), which is
inspired / based on Joda.
-Matthias
On 10/31/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
What are the thoughts about providing a Joda DateTime converter in
Hi!
What are the thoughts about providing a Joda DateTime converter in the
upcoming commons project ?
BTW, we use Joda here for a long time, so I have something to contribute
Ciao,
Mario
I can live with that
Ron
On 10/31/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Since there where some discussions about what should be in this new
project and what not:
Renderkit independent components yes/no? Only static utils, convenient
base classes?
I have a suggestion that would solve
selectOneRenderer did not render disabled
--
Key: TOBAGO-528
URL: https://issues.apache.org/jira/browse/TOBAGO-528
Project: MyFaces Tobago
Issue Type: Bug
Components: Themes
Hi,
never ever read a question regarding woodstock noticed here :-)
I am not aware of issues. Also I am not are of a smooth integration.
Perhaps worth to try... and let others know ?
Sorry,
Matthias
On 10/31/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
Has anbody made experiences
[
https://issues.apache.org/jira/browse/TOBAGO-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-528.
-
Resolution: Fixed
selectOneRenderer did not render disabled
Hi,
Has anbody made experiences with combining Trinidad and Woodstock?
Are there any bigger issues to expect, such as e.g. when combining
RichFaces with Trinidad?
Is the skinning combinable? Thanks for any info!
Best wishes,
Wolfgang.
TabChangeListener tag should allow methodBinding
Key: TOBAGO-529
URL: https://issues.apache.org/jira/browse/TOBAGO-529
Project: MyFaces Tobago
Issue Type: Improvement
Components:
I can live with that as well, the name speaks for itself, but it's s
loong.
~ Simon
On 10/31/07, Ron Smits [EMAIL PROTECTED] wrote:
I can live with that
Ron
On 10/31/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Since there where some discussions about what should be in this new
Hi,
I am looking for documentation links regarding the use of Trinidad's help
facet.
More concretely speaking, I would like to to use it with Oracle Web help.
Thanks in advance.
Best wishes,
Wolfgang.
Never used that...
But... perhaps you can check old ADF Faces 10.x documentation and
try to get it into Trinidad.
Like here:
http://download-uk.oracle.com/docs/html/B25947_01/appendixa010.htm
the adf-faces-config.xml is named now trinidad-config.xml (for instance)
-M
On 10/31/07, [EMAIL
+1 for 1.0.4
On 10/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
to have the lightweight dialog working, you have to configure this:
org.apache.myfaces.trinidad.ENABLE_LIGHTWEIGHT_DIALOGS=true
in your web.xml. This feature works nice!
Should we make the lightweight dialog
Well, I think there's probably enough difference between the two goals
that we do need to separate projects, even though it contributes to
the Yet Another MyFaces Subproject quagmire. At least it's a step
in the right direction since we're looking at merging common code
rather than futher
I like Manfred Geiler idea around MyFaces JSF Commons.
Paul Spencer
Simon Lessard wrote:
I can live with that as well, the name speaks for itself, but it's s
loong.
~ Simon
On 10/31/07, Ron Smits [EMAIL PROTECTED] wrote:
I can live with that
Ron
On 10/31/07, Manfred Geiler [EMAIL
Hi!
I have a suggestion that would solve this (and the naming as well):
Let's start a new MLP* called MyFaces JSF Commons
which is itself an umbrella project for two artifacts** called
MyFaces JSF Commons Utils and MyFaces JSF Commons Components
For the artifact names I propose:
Please summarize the intent and proposed contents of each subproject on
a wiki page. A common refactoring page already exists [1]. The
resulting pages should be moved in each project's site documentation
Paul Spencer
[1] http://wiki.apache.org/myfaces/MyFaces_Commons_Refactoring
Simon
I am planing on attending ApacheCon in Atlanta this year. Is are their
any MyFaces gathering planned?
Paul Spencer
Please summarize the intent and proposed contents of each subproject on
a wiki page. A common refactoring page already exists [1]. The
resulting pages should be moved in each project's site documentation
Paul Spencer
[1] http://wiki.apache.org/myfaces/MyFaces_Commons_Refactoring
Simon
[
https://issues.apache.org/jira/browse/TRINIDAD-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539093
]
Catalin Kormos commented on TRINIDAD-769:
-
Hi Cristi,
Sorry, i think you'll have to provide any new files
On 10/31/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
I have a suggestion that would solve this (and the naming as well):
Let's start a new MLP* called MyFaces JSF Commons
which is itself an umbrella project for two artifacts** called
MyFaces JSF Commons Utils and MyFaces JSF
Hi,
i don't understand what should go into the utils and what into the
components parts.
I think we can mix static utils with renderkid independent components
in one library.
for renderkid dependend compeonents we have already tomahawk, tobago
and trinidad.
Regards,
Volker
2007/10/31,
We're discussing two completely different concepts here.
One is an api for writing new components. For component developers.
One is a library of common renderkit-independent components for use in
JSF applications. For application developers.
Attempting to combine them is going to shortchange
Hi!
which is itself an umbrella project for two artifacts** called
MyFaces JSF Commons Utils and MyFaces JSF Commons Components
I suggest that I prepare an initial setup, and check it in, so that
there is some concrete stuff we can talk about.
Ok?
I still don't get why we should
On 10/31/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
which is itself an umbrella project for two artifacts** called
MyFaces JSF Commons Utils and MyFaces JSF Commons Components
I suggest that I prepare an initial setup, and check it in, so that
there is some concrete
This is the official vote for the release of our new MyFaces Master-POM.
The current myfaces-master POM has some flaws as was discussed in [1].
I already have tested a complete build of core and tomahawk with the new master.
I have NOT tested Trinidad and Tobago yet (both currently do not
depend
The point is:
For myfaces-jsfcommons-components we must provide additional stuff in the
jar. You know: taglib, faces-config.xml, ...
This is what we do NOT want in the myfaces-jsfcommons-utils jars to
- keep it simple, and
- avoid unwanted side-effects
Please mind: Not yet sure, but the
+1
On 10/31/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
What are the thoughts about providing a Joda DateTime converter in the
upcoming commons project ?
-M
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
What is the problem having a taglib in the jar?
2007/10/31, Manfred Geiler [EMAIL PROTECTED]:
On 10/31/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
which is itself an umbrella project for two artifacts** called
MyFaces JSF Commons Utils and MyFaces JSF Commons
1. opening (background) window clickable (ie. not greyed out) for modal
popups in firefox
Firefox has a bug with performance and graying out multiple controls,
so it should not be used. The modal nature is still implemented
though.
-A
To avoid this I'd NOT include eg viewhandler or navigation handler in the jar.
Taglib wont harm if not used.
Instead we just document how to setup.
Mario
-Original Message-
From: Manfred Geiler [EMAIL PROTECTED]
Date: Wednesday, Okt 31, 2007 4:53 pm
Subject: Re: [result][vote] start up
Hi All,
We like to propose an enhancement to how and where Trinidad maintains
its view caches. Currently when the system is configured to use token
as the state persistent method, Trinidad will maintain all component
states in a ViewCache. This ViewCache is just a map that is maintained
in
A taglib and a faces-config in the META-INF are loaded/registered
automatically.
And as I already mentioned, it should be possible to use the commons utils
from the core impl. Automatically loading extensions(!) is not what we want
when using the myfaces core implementation.
There is some stuff in
A new approach to JSF error handling
Key: TOMAHAWK-1139
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1139
Project: MyFaces Tomahawk
Issue Type: Improvement
Reporter: Val Blant
I
[
https://issues.apache.org/jira/browse/TOMAHAWK-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539215
]
Val Blant commented on TOMAHAWK-1139:
-
Problem description:
This solution deals with JSF's error processing
[
https://issues.apache.org/jira/browse/TOMAHAWK-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539216
]
Val Blant commented on TOMAHAWK-1139:
-
The idea is as such:
MDF provides more flexible message decoration by
[
https://issues.apache.org/jira/browse/TOMAHAWK-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539216
]
vace117 edited comment on TOMAHAWK-1139 at 10/31/07 4:51 PM:
---
The idea is as such:
[
https://issues.apache.org/jira/browse/MYFACES-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-1741:
Status: Patch Available (was: Open)
JSR-252 Issue 21 - Provided an additional binding
[
https://issues.apache.org/jira/browse/MYFACES-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539290
]
Leonardo Uribe commented on MYFACES-1741:
-
After asking some questions on jsf ri dev mailing list, I
[
https://issues.apache.org/jira/browse/MYFACES-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539295
]
Leonardo Uribe commented on MYFACES-1729:
-
Fortunately there was a discussion about this on
49 matches
Mail list logo
