Hi!
Doesn't this change break backward compatibility completley?
The value of the alias= attribute now has to be defined differently,
instead of the el-expressesion just the name needs to be set.
Even if this change is logical to me, a new tomahawk release will break
any existing application
[
https://issues.apache.org/jira/browse/TOMAHAWK-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607496#action_12607496
]
Christian Kaltepoth commented on TOMAHAWK-64:
-
Thank you very much for looking
[
https://issues.apache.org/jira/browse/TOMAHAWK-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607509#action_12607509
]
Tomasz Bech commented on TOMAHAWK-1034:
---
As I wrote, it is workaround.
Some .js
XmlMenuModel: action is interpreted as ValueExpression
--
Key: TRINIDAD-1134
URL: https://issues.apache.org/jira/browse/TRINIDAD-1134
Project: MyFaces Trinidad
Issue Type: Bug
Hi,
I have a requirement where I need to render the tr:inputDate component such=
that on opening the calendar popup, dates before a certain date can't be s=
elected.=C2=A0 How can this be brought about???
Dushyant
Best Jokes, Best Friends, Best Food and more. Go to
[
https://issues.apache.org/jira/browse/TOMAHAWK-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607544#action_12607544
]
Simon Kitching commented on TOMAHAWK-1266:
--
Ok, I've found the real cause of
On Tue, Jun 24, 2008 at 2:20 AM, dushyant agarwal
[EMAIL PROTECTED] wrote:
Hi,
I have a requirement where I need to render the tr:inputDate component such=
that on opening the calendar popup, dates before a certain date can't be s=
elected.=C2=A0 How can this be brought about???
This is not
[
https://issues.apache.org/jira/browse/ORCHESTRA-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607631#action_12607631
]
Simon Kitching commented on ORCHESTRA-18:
-
This issue should be fixed by the new
[
https://issues.apache.org/jira/browse/ORCHESTRA-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607632#action_12607632
]
Simon Kitching commented on ORCHESTRA-22:
-
This is using Orchestra in a Portlet.
[
https://issues.apache.org/jira/browse/ORCHESTRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607635#action_12607635
]
skitching edited comment on ORCHESTRA-1 at 6/24/08 7:54 AM:
[
https://issues.apache.org/jira/browse/ORCHESTRA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching reopened ORCHESTRA-4:
Reopening as requested in comments
Clean up build files
[
https://issues.apache.org/jira/browse/ORCHESTRA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Kitching reopened ORCHESTRA-15:
-
Reopening as there are still portlet-related issues with orchestra and this
issue has
Hi All,
I'm about to start working on a new Orchestra feature (basic dialog
support).
It therefore seems a good idea to get an Orchestra release out before I
start messing with the trunk. In particular, there are two bugs which
are fixed in trunk and would be good to have in an official
Simon,
How much work is required to support portlets in Orchestra?
~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer
Hello Simon,
On Tue, Jun 24, 2008 at 8:45 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi All,
I'm about to start working on a new Orchestra feature (basic dialog
support).
It therefore seems a good idea to get an Orchestra release out before I
start messing with the trunk. In
Hi
Alias property only receive el expression. There was a mistake on a commit
the example page, which was reverted (sorry!). Alias never receive string
only values. The change applied throws an expression when alias=someString
instead alias=#{somebean}. Previously other non descriptive error is
[
https://issues.apache.org/jira/browse/MYFACES-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607688#action_12607688
]
Greg Lloyd commented on MYFACES-1838:
-
Is there any work around for this, maybe by
[
https://issues.apache.org/jira/browse/MYFACES-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12606998#action_12606998
]
keywan edited comment on MYFACES-1493 at 6/24/08 11:26 AM:
---
[
https://issues.apache.org/jira/browse/TRINIDAD-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607730#action_12607730
]
Gary Kind commented on TRINIDAD-1134:
-
The action attribute, as per the spec, is
Hi
The following converters and validators are proposed to be moven from
sandbox to tomahawk core:
s:convertBoolean
s:convertDateTime
s:convertNumber
s:validateCompareTo
s:validateCSV
s:validateISBN
s:validateUrl
In tomahawk core, the related files should be moved from sandbox/core to
core. In
+1
On Tue, Jun 24, 2008 at 2:45 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi
The following converters and validators are proposed to be moven from
sandbox to tomahawk core:
s:convertBoolean
s:convertDateTime
s:convertNumber
s:validateCompareTo
s:validateCSV
s:validateISBN
+1, we are waiting for this release, rather cutting our own release to pick
up 2 mentioned bugs
-D
kito99 wrote:
Simon,
How much work is required to support portlets in Orchestra?
~~~
Kito D. Mann - Author, JavaServer
Can someone help me figure out where the CAPTCHA tag disappeared to? I've
tried tomahawk and sandbox latest builds and it's not in either.
Thanks.
Mike
This component was upgraded from sandbox to tomahawk. On the latest code is
here.
regards
Leonardo Uribe
On Tue, Jun 24, 2008 at 2:52 PM, Michael Angelo [EMAIL PROTECTED] wrote:
Can someone help me figure out where the CAPTCHA tag disappeared to? I've
tried tomahawk and sandbox latest builds
Hi,
converters should go into commons not into tomahawk.
Why is this only planed for the 1.2 branch?
Regards,
Volker
2008/6/24 Leonardo Uribe [EMAIL PROTECTED]:
Hi
The following converters and validators are proposed to be moven from
sandbox to tomahawk core:
s:convertBoolean
[
https://issues.apache.org/jira/browse/MYFACES-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Concini updated MYFACES-1879:
-
Status: Patch Available (was: Open)
Problems with myfaces when java2 security is
[
https://issues.apache.org/jira/browse/TOMAHAWK-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607749#action_12607749
]
Leonardo Uribe commented on TOMAHAWK-1283:
--
Thanks for the zipped test, it
On Tue, Jun 24, 2008 at 3:05 PM, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
converters should go into commons not into tomahawk.
Why is this only planed for the 1.2 branch?
That is the hidden reason why I request a vote for this. All validators and
converters should be on myfaces-commons.
[
https://issues.apache.org/jira/browse/ORCHESTRA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernhard Huemer updated ORCHESTRA-17:
-
Status: Patch Available (was: Reopened)
RequestParameterFacesContextFactory only
[
https://issues.apache.org/jira/browse/ORCHESTRA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607762#action_12607762
]
Bernhard Huemer commented on ORCHESTRA-17:
--
I've created a patch that is
HtmlDataScroller should inherit UIPanel instead HtmlPanelGroup
--
Key: TOMAHAWK-1289
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1289
Project: MyFaces Tomahawk
Issue Type:
I downloaded tomahawk 1.1.6 and 1.1.7 today. I looked in the TLD and added
to my build path in MyEclipse. The code assist shows all t: tags and
CAPTCHA is not there.
[
https://issues.apache.org/jira/browse/TOMAHAWK-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607783#action_12607783
]
Leonardo Uribe commented on TOMAHAWK-1014:
--
Allow define custom converter on
[
https://issues.apache.org/jira/browse/TOMAHAWK-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607792#action_12607792
]
Leonardo Uribe commented on TOMAHAWK-887:
-
I cannot reproduce this error. Is
[
https://issues.apache.org/jira/browse/TOMAHAWK-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607797#action_12607797
]
Leonardo Uribe commented on TOMAHAWK-1180:
--
h:commandLink or t:commandLink
You are obviously a busy man and I hate to keep bugging you with this. If I am
wrong I am going to feel like an idiot. I cannot find CAPTCHA in either of
the libraries (sandbox or tomahawk).
Please help!!
I really need this tonight!
Thanks a lot!!
Please look at:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.7-SNAPSHOT/tomahawk-1.1.7-SNAPSHOT.jar
checking the file META-INF/tomahawk.tld captcha is here
regards
Leonardo Uribe
On Tue, Jun 24, 2008 at 7:16 PM, Michael Angelo [EMAIL PROTECTED]
The location that you provided for me did in fact download a version of the
jar file that had CAPTCHA. The tomahawk.tld date/time stamp in that .jar file
is 6/18/2008. The date/time stamp from the one I downloaded from the link
below is 1/8/2008.
Why not doing a check out of the source?
If it is that urgent, that should be ok to try..
-M
On Tue, Jun 24, 2008 at 7:11 PM, Michael Angelo [EMAIL PROTECTED] wrote:
The location that you provided for me did in fact download a version of the
jar file that had CAPTCHA. The tomahawk.tld
On Tue, Jun 24, 2008 at 1:52 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
On Tue, Jun 24, 2008 at 3:05 PM, Volker Weber [EMAIL PROTECTED] wrote:
Hi,
converters should go into commons not into tomahawk.
+1
Why is this only planed for the 1.2 branch?
That is the hidden reason why I
[
https://issues.apache.org/jira/browse/TOMAHAWK-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607842#action_12607842
]
Leonardo Uribe commented on TOMAHAWK-922:
-
I have committed on core12 the changes
[
https://issues.apache.org/jira/browse/TRINIDAD-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1129.
--
Resolution: Fixed
Server-side validation does not work when using Sun JSF
42 matches
Mail list logo
