On Tue, Sep 15, 2009 at 8:55 AM, Paul Mander <paul.s.man...@gmail.com> wrote: > > I'd love to move off 1.1 but we are stuck with WebSphere 6.1. The following > discusses how you can get WAS 6.1 to work with JSF 1.2 but it involves too > much change which will break existing applications. > > http://www.denoo.info/2008/02/finally-jsf-12-and-facelets-on-websphere-61/ > > I do most of my work with large banks and they just don't move that quickly > I'm afraid.
I understand that, we (the MyFaces community) has no problem in (kinda) continuing the Trinidad 1.0.x stuff, therefore I asked to create a ticket to back-port the stuff ;-) I also know that you need the other fix, from the "testing release" thread. Still on my long list. -Matthias > > > > Matthias Wessendorf-4 wrote: >> >> On Tue, Sep 15, 2009 at 8:10 AM, Paul Mander <paul.s.man...@gmail.com> >> wrote: >>> >>> Thanks a lot Mamallan. That solved it. >>> >>> I wonder why the 1.0 branch is so out of step with the 1.2 branch (trunk) >> >> A while ago, we decided to focused on JSF 1.2, instead of 1.1. >> Most of the fixes over last year went into both. But some of them >> (including all new features) were only add to 1.2. version of Trinidad >> >> Our goal is really to motivate users to update to JSF 1.2, or JSF 2.0 >> once that specification is available. >> >> However, we can backport the TRINIDAD-1430 to 1.0.x version of Trinidad. >> do you mind to create a JIRA ticket for that ? The next release(s) of >> Trinidad >> 1.0.x are only maintenance releases, but there will be some. >> >> Thanks! >> Matthias >> >> >>> >>> >>> Mamallan Uthaman wrote: >>>> >>>> Hi Paul, >>>> >>>> Do you get any exception in the server log? I guess this could be due >>>> to Trinidad-1430. >>>> >>>> Thanks >>>> Mamallan >>>> >>>> >>>> >>>> Paul Mander wrote: >>>>> We've recently upgraded from 1.0.7 to 1.0.11 and found that we now >>>>> cannot >>>>> enter Turkish characters into forms whereas before we didn't have any >>>>> problem in this area. I have narrowed this down to 1.0.10 which was the >>>>> last >>>>> release when it worked. >>>>> >>>>> The problem arises when entering "YURTİÇİ" which contains the problem >>>>> characters. The page bean receives these in a garbled format using >>>>> 1.0.11 >>>>> (fine with 1.0.10). >>>>> >>>>> Looking through the release note all I can see that touches anything >>>>> relating to this is https://issues.apache.org/jira/browse/TRINIDAD-974. >>>>> It >>>>> mentioned in the comments about setting encoding levels for these jspx >>>>> files. I have tried >>>>> >>>>> <?xml version="1.0" encoding="ISO-8859-9"?> (Turkish) >>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>> >>>>> but they don't work. Interestingly they do garble the input is a >>>>> different >>>>> way. >>>>> >>>>> Has anyone got any ideas about this. It is extremely urgent that we get >>>>> this >>>>> fixed as soon as possible. >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/-TRINIDAD--character-encoding-issue-with-1.0.11-tp25436068p25448505.html >>> Sent from the MyFaces - Users mailing list archive at Nabble.com. >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> > > -- > View this message in context: > http://www.nabble.com/-TRINIDAD--character-encoding-issue-with-1.0.11-tp25436068p25448927.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
