Sorry for the off topic post, but this is big news:
http://www.oracle.com/us/corporate/press/176988
Sending this again with the proper heading:
By default, when Java Lists/Arrays are used as models in Trinidad
table/tree/treeTable components, they are wrapped in a SortableModel
instance.
The problem with SortableModel is that it uses row indexes as row keys. This
makes SortableModel immutable
what happened to this vote ?
-Matthias
On Fri, Jul 23, 2010 at 7:30 PM, Scott O'Bryan darkar...@gmail.com wrote:
+1
On 07/22/2010 04:41 AM, Matthias Wessendorf wrote:
+1
On Wed, Jul 21, 2010 at 10:18 PM, Michael Freedman
michael.freed...@oracle.com wrote:
+1
On 7/20/2010 2:09 PM,
Hi,
Thanks a lot for your answer, i've got more questions below so that i
can follow your advice correctly.
On 9 October 2010 00:06, Leonardo Uribe lu4...@gmail.com wrote:
Note VariableMapper has build time scope, or in other words, it is set
and discarded when facelets builds the component
Hi,
If my test page calls a composite component in level 1:
xmlns:level1=http://java.sun.com/jsf/composite/level1;
level1:button value=test1
f:actionListener for=button1 binding=#{myBean.action1} /
/level1:button
where level1 button passes the action
[
https://issues.apache.org/jira/browse/TRINIDAD-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yee-Wah Lee updated TRINIDAD-1920:
--
Status: Patch Available (was: Open)
DateTimeRangevalidator fails across multiple
Hi Ganesh,
This is a known problem of the JSF 2.0 spec, see [1]. Sadly it was
(re-)targeted for 2.2.
The problem is that when the ation listener is retargeted (from the
composite component to the inner (implementation) component), it
cannot be retargeted to another composite component, because
But anyhow, please open an issue for this. Thanks!
Regards,
Jakob
2010/10/12 Jakob Korherr jakob.korh...@gmail.com:
Hi Ganesh,
This is a known problem of the JSF 2.0 spec, see [1]. Sadly it was
(re-)targeted for 2.2.
The problem is that when the ation listener is retargeted (from the
Hi
I remember this one. Fortunately, MyFaces has many, many tests for composite
components. It also has a test for this specific issue and it works well:
testCompositeActionSource.xhtml
h:form id=testForm1
testComposite:compositeActionSource
f:actionListener for=button2
Hi
I tried your example and work in this way:
test page calls a composite component in level 1:
xmlns:level1=http://java.sun.com/jsf/composite/level1;
level1:button value=test1
f:actionListener for=button1 binding=#{myBean.action1}
/
/level1:button
level1
Actually, I had deferred sending the results message pending us
actually doing/pushing the release which I thought was imminent. Alas I
am still awaiting getting some free time from the developer tasked to do
this but that slot never seems to open up -- so its now 2+ months since
this was
[
https://issues.apache.org/jira/browse/TRINIDAD-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson resolved TRINIDAD-1919.
---
Resolution: Fixed
Fix Version/s: 2.0.0.3-core
var and varStatus of the
[
https://issues.apache.org/jira/browse/TRINIDAD-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12920401#action_12920401
]
Tadashi Enomori commented on TRINIDAD-1933:
---
I reviewed the patches and they
Hi Mike,
you should send out the result vote roughly 72hrs after the vote has
started. When you do the release based on the vote - is your timing
thingy ;)
best regards,
Martin
On 10/12/10, Michael Freedman michael.freed...@oracle.com wrote:
Actually, I had deferred sending the results
14 matches
Mail list logo
