The MyFaces voting habits so far:
Public:
- code changes
- releases
- repository changes, refactoring
- misc
Private (ie. only PMC members):
- new committers
- new PMC members
I think this was a good way in the past and we should keep that procedure.
--Manfred
On 7/19/07, Matthias
BTW, thanks Matthias for the successful 1.2 release.
Good to know that someone keeps the business running while oneself is
lying in the sun beeing on vacation... ;-)
Regarding the repo structure. We had some discussions before. One
proposal was the follwing structure. And AFAIR there where no
tc:object did not work in ajax requests
---
Key: TOBAGO-455
URL: https://issues.apache.org/jira/browse/TOBAGO-455
Project: MyFaces Tobago
Issue Type: Bug
Affects Versions: 1.0.11
Environment:
javascript: Tobago.openPopupWithAction() should allow options.
--
Key: TOBAGO-456
URL: https://issues.apache.org/jira/browse/TOBAGO-456
Project: MyFaces Tobago
Issue Type:
[
https://issues.apache.org/jira/browse/TOBAGO-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-456.
-
Resolution: Fixed
javascript: Tobago.openPopupWithAction() should allow options.
Hi,
there are any plan to apply this fix to 1.2? When 1.2 will become trunk?
I look at SVN and see that trunk is 1.0.2 yet...
Thanks,
Bruno E. Grossi
Matthias Wessendorf wrote:
yeah,
Adam plays magician and makes the trunk (JSF 1.1-style) become JSF
1.2-style, once in a while :-)
We
Manfred,
+1 for the following!
/branches
/branches/1_1_6
/branches/1_2_1
/tags
/tags/1_1_2
/tags/1_1_3
/tags/1_1_4
/tags/1_1_5
/tags/1_2_0
/tags/1_2_1
/1_1_x --- the trunk for JSF 1.1 development
/1_2_x --- the trunk for JSF 1.2 development
Are their any changes
The Datascroller causes a class cast exception in MyFaces 1.2
-
Key: TOMAHAWK-1064
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1064
Project: MyFaces Tomahawk
Issue Type:
[
https://issues.apache.org/jira/browse/TOMAHAWK-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514651
]
Werner Punz commented on TOMAHAWK-1064:
---
Ok it seems to be an error in the examples, other datascrolling
Hi,
I am working on the client side NumberConverter, therefore I'd like to
change four methods in the Trinidad API
(org.apache.myfaces.trinidad.convert.NumberConverter)
In order to send down the attributes of maxIntegerDigits,
maxFractionDigits,... I need to check if they have been set on the
/branches
/branches/1_1_6
/branches/1_2_1
/tags
/tags/1_1_2
/tags/1_1_3
/tags/1_1_4
/tags/1_1_5
/tags/1_2_0
/tags/1_2_1
/1_1_x --- the trunk for JSF 1.1 development
/1_2_x --- the trunk for JSF 1.2 development
I like that tomcat style.
-M
The great advantage: We can do
+1
On 7/23/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
/branches
/branches/1_1_6
/branches/1_2_1
/tags
/tags/1_1_2
/tags/1_1_3
/tags/1_1_4
/tags/1_1_5
/tags/1_2_0
/tags/1_2_1
/1_1_x --- the trunk for JSF 1.1 development
/1_2_x --- the trunk for JSF 1.2
[
https://issues.apache.org/jira/browse/MYFACES-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved MYFACES-1684.
-
Resolution: Fixed
fixed, please check out the 1.2.1-branch and check your app
Once 1.0.2 is released, we'll re-branch 1.2 to get ready for a 1.2.2
release, and that'll have the fix.
We're still debating when to make 1.2 trunk - for now, our assumption
is that a large majority of the Trinidad users are still on JSF 1.1.
-- Adam
On 7/23/07, Bruno E. Grossi [EMAIL
This behavior of getMaxIntegerDigits seems wrong, shouldn't we be
calling the version of resolveInteger that takes a default value?
Thanks,
Gabrielle
Matthias Wessendorf wrote:
Hi,
I am working on the client side NumberConverter, therefore I'd like to
change four methods in the Trinidad API
Actually +1 to the original mail. The RI's numberConverter looks like it
returns 0 as well
Thanks,
Gab
Gabrielle Crawford wrote:
This behavior of getMaxIntegerDigits seems wrong, shouldn't we be
calling the version of resolveInteger that takes a default value?
Thanks,
Gabrielle
[
https://issues.apache.org/jira/browse/TOMAHAWK-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514752
]
Joshua Wojcik commented on TOMAHAWK-94:
---
Can you add the code for the call too
[
https://issues.apache.org/jira/browse/TOMAHAWK-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514752
]
Joshua Wojcik edited comment on TOMAHAWK-94 at 7/23/07 12:33 PM:
-
Can you add the
[
https://issues.apache.org/jira/browse/TOBAGO-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514802
]
Guido Dubois commented on TOBAGO-422:
-
When you are fixing this? I'm waiting for this...
facelets - gridlayout
Enabled exception handling like in Facelets for the rest of the MyFaces
LifeCycle
-
Key: MYFACES-1685
URL: https://issues.apache.org/jira/browse/MYFACES-1685
Project:
[
https://issues.apache.org/jira/browse/MYFACES-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514850
]
Matthias Weßendorf commented on MYFACES-1685:
-
he is tomcat-pmc :-)
With permission of Jacob Hookom, I've enabled Exception Handling just like
in Facelets now also for the rest of the JSF-Lifecycle - it will also work
with plain JSP.
I've also cleaned up the stack-traces, so that you actually see causing
exceptions (if any Servlet-Exceptions are in the chain) -
Please add your company to this list
http://wiki.apache.org/myfaces/Companies_using_Trinidad
Thx!
Matthias
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
If your are using MyFaces (1.1.x || 1.2.x) and your company isn't listed here:
http://wiki.apache.org/myfaces/Companies_Using_MyFaces
Please add it!
Thx,
Matthias
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
24 matches
Mail list logo