[
https://issues.apache.org/jira/browse/TRINIDAD-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610163#action_12610163
]
Matthias Weßendorf commented on TRINIDAD-1139:
--
OK, now I got it.
the html
Hi Matthias,
Can you please put the fix for 1.2.8.1 branch as well? I have a Oracle
internal bug that is dependent on this fix.
Thanks,
Venkata
Matthias Weßendorf (JIRA) wrote:
[
Hi all!
As suggested by Matthias I provide a new patch for the InputDate problem
(see TRINIDAD-790). This one is against the 1.0.X trunk. I'm interested
in resolving this annoying bug because I have these components in
production.
I quote my previous post about the patch:
[...]
there were
Hi,
thanks for the patch.
I am already applying it.
thanks!
On Thu, Jul 3, 2008 at 10:42 AM, Gregor Sfiligoj
[EMAIL PROTECTED] wrote:
Hi all!
As suggested by Matthias I provide a new patch for the InputDate problem
(see TRINIDAD-790). This one is against the 1.0.X trunk. I'm interested in
[
https://issues.apache.org/jira/browse/TRINIDAD-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610169#action_12610169
]
Matthias Weßendorf commented on TRINIDAD-790:
-
thnaks for the patch.
[
https://issues.apache.org/jira/browse/TRINIDAD-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-790:
Resolution: Fixed
Fix Version/s: 1.2.9-core
1.0.9-core
check the system time. Is it diffrent than current date time??
Ok :-)
I saw that you have included it also in 1.2.X trunk!
Thank you!!
Matthias Wessendorf wrote:
Hi,
thanks for the patch.
I am already applying it.
thanks!
On Thu, Jul 3, 2008 at 10:42 AM, Gregor Sfiligoj
[EMAIL PROTECTED] wrote:
Hi all!
As suggested by Matthias I provide a new
Hi,
I have JSF page which contains a tr:inputDate component as given below:-
tr:inputDate binding=#{BB.inputDate1}/
As well as there is a commandButton
tr:commandButton action=#{BB.action}
In the Backing bean the action method is as follows:-
public String action(){
DateTimeConverter converter
[
https://issues.apache.org/jira/browse/TRINIDAD-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610223#action_12610223
]
Carsten Pieper commented on TRINIDAD-775:
-
Yes, indeed, the given workaround is
[
https://issues.apache.org/jira/browse/TRINIDAD-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610252#action_12610252
]
Matthias Weßendorf commented on TRINIDAD-745:
-
I think it is worth to add
[
https://issues.apache.org/jira/browse/TRINIDAD-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610253#action_12610253
]
Matthias Weßendorf commented on TRINIDAD-745:
-
and even worse, if the users
If that were done, I would recommend the name renderOne. choose in
JSF sounds closer to the select* prefix, reserved for UIInput
components. renderOne is clear in that it shows that it affects
rendering, where choose does not define what it does (one could argue
that it was a bad naming decision
[
https://issues.apache.org/jira/browse/MYFACES-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610346#action_12610346
]
Leonardo Uribe commented on MYFACES-1888:
-
After reproducing many error
Ok, as people seem happy to see tabs cleaned up done I'm doing it now.
But I'm leaving trailing whitespace alone for now; there is less benefit
and it does touch a whole lot of files.
To anyone who currently has checked-out directories with uncommitted
changes in them, I recommend running
The name t:renderOne sounds good to me.
On Thu, 2008-07-03 at 10:07 -0600, Andrew Robinson wrote:
If that were done, I would recommend the name renderOne. choose in
JSF sounds closer to the select* prefix, reserved for UIInput
components. renderOne is clear in that it shows that it affects
By the way:
* the detab.sh script is here:
http://svn.apache.org/repos/asf/myfaces/myfaces-build-tools/trunk/other/scripts/detab.sh
* I haven't touched tobago, trinidad or portlet-bridge. It's up to the
developers of those projects to choose when/if they want to do this.
I also fixed quite a
Sorry, but I think conflicts are now being reported when updating a
checkout dir for files where *all* of these were true:
* contains tabs
* did not have eol-style set to native
* was not first checked in from your native platform.
I'll try to think of a nice way to automatically clean up those
SVN merge takes -x -w arguments to ignore whitespace. I am not sure
about updating.
-Andrew
On Thu, Jul 3, 2008 at 4:39 PM, simon [EMAIL PROTECTED] wrote:
Sorry, but I think conflicts are now being reported when updating a
checkout dir for files where *all* of these were true:
* contains tabs
19 matches
Mail list logo