Not unless MyFaces has the same issue.. It's now looking more like thurs. We're waiting for a fix..
The issue I fixed, just FYI was a problem with using facelets. Without getting too technical, Facelets allows you to add multiple values per facet. To maintain compatibility, it wraps these values in a UIPanel. Unfortunately, in the RI at least, the UIPanel was intermittently applied to facets containing one value and so it was possible for the collectionModel to retrieve a component it was expecting. So I added code which handled an erroneous UIPanel. On Feb 11, 2011, at 11:33 AM, Michael Gitelman <[email protected]> wrote: > > Hi Scott, > > Thank you. I could wait until Tuesday or Wednesday. I would appreciate if you > let me know when the latest binaries are available. > > The bad news is that I tried my code against MyFaces implementation instead > of Mojarra and got the same results. > > Any thought? > > > > > Best regards, > > > > > > Michael Gitelman > > [email protected] > > -----Original Message----- > From: Scott O'Bryan [mailto:[email protected]] > Sent: Thursday, February 10, 2011 7:41 PM > To: [email protected] > Subject: Re: Trinidad 2.0 > > Well, you can retrieve the artifacts (via mvn) from > https://repository.apache.org/content/repositories/snapshots or you can > download the latest trunk by following the instructions here here: > http://myfaces.apache.org/trinidad/source-repository.html > > Now, that said, it's likely I'll be beginning the release process for > another Trinidad beta tomorrow (unless there are any objections) which > means that we're looking at a release of Tues or Wed of next week if > you'd rather wait for the binaries. > > Scott > > > > CONFIDENTIALITY NOTICE > This e-mail message from Delphi Technology, Inc. is intended only for the > individual or entity to which it is addressed. This e-mail may contain > information that is privileged, confidential and exempt from disclosure under > applicable law. If you are not the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this > communication is strictly prohibited. If you received this e-mail by > accident, please notify the sender immediately and destroy this e-mail and > all copies of it.
