All,
please note that there is a new skin - called suede - added that mimics
the Oracle browser look and feel that exist for ADF Faces in 10.1.3.
Frank
Cristi Toth wrote:
Hi Andrew,
These are very good initiatives and htey would have good impact for
promoting Trinidad.
I would
NotSerializableException for
org.apache.myfaces.custom.fileupload.UploadedFileDefaultMemoryImpl$1
-
Key: TOMAHAWK-1208
URL:
oamSetHiddenInput function missing for myfaces core 1.2 if ...
--
Key: MYFACES-1830
URL: https://issues.apache.org/jira/browse/MYFACES-1830
Project: MyFaces Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/MYFACES-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574496#action_12574496
]
Leonardo Uribe commented on MYFACES-1504:
-
Trinidad override HtmlCommandButton
tr:table rowSelection attribute expressions not able to change the value
Key: TRINIDAD-981
URL: https://issues.apache.org/jira/browse/TRINIDAD-981
Project: MyFaces Trinidad
[
https://issues.apache.org/jira/browse/TRINIDAD-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574538#action_12574538
]
Renzo Tomaselli commented on TRINIDAD-967:
--
well, the proposed path raises some
ComponentRef
Key: TRINIDAD-982
URL: https://issues.apache.org/jira/browse/TRINIDAD-982
Project: MyFaces Trinidad
Issue Type: Improvement
Affects Versions: 1.0.6-core
Reporter: Tomas Havelka
Fix For:
Sortable model for localized texts
--
Key: TRINIDAD-983
URL: https://issues.apache.org/jira/browse/TRINIDAD-983
Project: MyFaces Trinidad
Issue Type: Improvement
Affects Versions: 1.0.6-core
PanelTabbed problem with invalid state
--
Key: TRINIDAD-984
URL: https://issues.apache.org/jira/browse/TRINIDAD-984
Project: MyFaces Trinidad
Issue Type: Improvement
Affects Versions: 1.0.6-core
Yeah I saw it and, please take no offense, would not want to use it. I
really would like to make a slick one on-par with RichFaces that
embraces the MyFaces proposed LnF (rounded corners, gradients,
shading, etc.).
-Andrew
On Mon, Mar 3, 2008 at 3:05 AM, Frank Nimphius
[EMAIL PROTECTED] wrote:
I am seeing more and more users setting the fix release as a way to
put down when they seem to want to have it fixed by. It was my
understanding that this should only be used to mark what release the
actual fix has been placed in. If so, is there a way that we can put
security around the fix
Andrew,
no problem. I am not advocating the Oracle Look and Feel as the best
look and feel you can build ;-)
Frank
Andrew Robinson wrote:
Yeah I saw it and, please take no offense, would not want to use it. I
really would like to make a slick one on-par with RichFaces that
embraces the
IMO - By the time that the bug is resolved I think it should reflect the
actual version it was fixed in. If there is a hot bug though (like a
major issue), sometimes its cool to signify that something needs to be
done about it by the next major release because then it's clear how many
open
Hi Andrew,
On Mon, Mar 3, 2008 at 5:37 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
I am seeing more and more users setting the fix release as a way to
put down when they seem to want to have it fixed by. It was my
understanding that this should only be used to mark what release the
actual
JSF12 UIComponentClassicTagBase.getCreated is broken, breaking
t:updateActionListener
-
Key: MYFACES-1831
URL: https://issues.apache.org/jira/browse/MYFACES-1831
That sums it up, thx Matthias, you the man.
On Mon, Mar 3, 2008 at 10:05 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi Andrew,
On Mon, Mar 3, 2008 at 5:37 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
I am seeing more and more users setting the fix release as a way to
put down
[
https://issues.apache.org/jira/browse/MYFACES-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574617#action_12574617
]
Andrew Robinson commented on MYFACES-1831:
--
Note that t:updateActionListener is
Maximum date on tr:validateDateTimeRange is maximum date minus 1
--
Key: TRINIDAD-985
URL: https://issues.apache.org/jira/browse/TRINIDAD-985
Project: MyFaces Trinidad
Issue
[
https://issues.apache.org/jira/browse/MYFACES-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574694#action_12574694
]
imario edited comment on MYFACES-1831 at 3/3/08 11:31 AM:
[
https://issues.apache.org/jira/browse/MYFACES-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574694#action_12574694
]
Mario Ivankovits commented on MYFACES-1831:
---
Hmmm ... for what I have seen in
Hey everyone,
I'm thinking of logging a JIRA ticket to add a Portlet profile and
config file to the Trinidad Demos to allow us to run Trinidad in a
portlet environment under jetty. This would be handy for testing
Trinidad with a portal environment and will allow us to more easily test
the
[
https://issues.apache.org/jira/browse/TRINIDAD-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary VanMatre updated TRINIDAD-986:
---
Status: Patch Available (was: Open)
EXTERNAL DIALOG FAILING TO RESIZE TO CONTENT
EXTERNAL DIALOG FAILING TO RESIZE TO CONTENT
Key: TRINIDAD-986
URL: https://issues.apache.org/jira/browse/TRINIDAD-986
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Hi,
On Mon, Mar 3, 2008 at 9:29 PM, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hey everyone,
I'm thinking of logging a JIRA ticket to add a Portlet profile and
config file to the Trinidad Demos to allow us to run Trinidad in a
portlet environment under jetty. This would be handy for testing
Hi
I'm doing the related tasks of move sandbox components that has reached the
conditions to be upgraded. Finally the list proposed is this:
s:convertBoolean
s:convertDateTime
s:convertNumber
s:form
s:inputSuggest
s:inputSuggestAjax
s:pprPanelGroup
s:passwordStrength
s:selectManyPicklist
Leonardo,
My limitRendered is pretty much not going to change (feature
complete), would this be a good candidate to promote as well or should
it be considered for the commons project instead?
http://myfaces.apache.org/sandbox/limitRendered.html
-Andrew
On Mon, Mar 3, 2008 at 1:59 PM, Leonardo
Will DOJO be optional for tomahawk or will promoting these components
force more 3rd party library dependencies to be added to tomahawk
(regarding the Ajax components)?
On Mon, Mar 3, 2008 at 1:59 PM, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi
I'm doing the related tasks of move sandbox
My limitRendered is pretty much not going to change (feature
complete), would this be a good candidate to promote as well or should
it be considered for the commons project instead?
Yes, you are right. Has doc, site doc and the examples works with RI and
Myfaces. It was a typo error on my list
We can reference the component on the tld of tomahawk, but the hypotetical
DOJO commons module jar should be referenced too. How we can do this
optional?
Maven has an optional scope on dependencies. Believe it looks like:
dependency
groupId /
artifactId /
version /
Hi Kenneth,
How is this going? Were you able to create a patch?
Maria wants me to tell her whether or not this will be done by this Friday.
Thanks,
Jeanne
Kenneth tang (JIRA) wrote, On 2/28/2008 10:36 AM PT:
[
it's:
optionaltrue/optional
On Mon, Mar 3, 2008 at 10:24 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
We can reference the component on the tld of tomahawk, but the
hypotetical
DOJO commons module jar should be referenced too. How we can do this
optional?
Maven has an optional scope
optionaltrue/optional
Ah, Ok, I never used it before.
But checking the code of dojo component I cannot see any external lib (since
all dojo javascript are copied on src/main/resources).
hmmm, bad memory, thanks Cristi
On Mon, Mar 3, 2008 at 2:31 PM, Cristi Toth [EMAIL PROTECTED] wrote:
it's:
optionaltrue/optional
On Mon, Mar 3, 2008 at 10:24 PM, Andrew Robinson
[EMAIL PROTECTED] wrote:
We can reference the component on the tld of tomahawk, but the
hypotetical
[
https://issues.apache.org/jira/browse/MYFACES-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574755#action_12574755
]
Simon Kitching commented on MYFACES-1831:
-
Drat. I meant getCreated always
This was meant for Kenneth only. Sorry, Jeanne
Jeanne Waldman wrote, On 3/3/2008 1:23 PM PT:
Hi Kenneth,
How is this going? Were you able to create a patch?
Maria wants me to tell her whether or not this will be done by this
Friday.
Thanks,
Jeanne
Kenneth tang (JIRA) wrote, On 2/28/2008
On Mon, 2008-03-03 at 15:59 -0500, Leonardo Uribe wrote:
Hi
I'm doing the related tasks of move sandbox components that has
reached the conditions to be upgraded. Finally the list proposed is
this:
s:convertBoolean
s:convertDateTime
s:convertNumber
s:form
s:inputSuggest
Hello,
I've been a MyFaces/Tomawahk user for the last few years. For the
longest time, it completely served my needs and was very happy with
the level of support that I received from the community. About a year
ago, I decided to adopt JBoss Seam and a way to augment my own
implementation
On Mon, Mar 3, 2008 at 4:58 PM, simon [EMAIL PROTECTED] wrote:
The list of components is fine. And I very much appreciate all your work
on this and the tomahawk bugs you've been fixing recently.
However at the risk of sounding like a broken record, I would like to
point out that AFAIK there
add 'scoped-id-holder' and 'multi-scoped-id-holder' to transform.xsl and
transform12.xsl
Key: TRINIDAD-987
URL: https://issues.apache.org/jira/browse/TRINIDAD-987
I agree with Leonardo totally. Just because you have a 2.0 branch does
not mean that you drop support for 1.1. It simply means that things
which cannot be made 1.1 compatible continue to migrate and that the
stuff which is already in place, embraces any emerging standards.
Furthermore, it
40 matches
Mail list logo
