[jira] [Commented] (MYFACES-3399) PostAddToViewEvent is being published incoherently with spec's javadoc

[ https://issues.apache.org/jira/browse/MYFACES-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152735#comment-13152735 ] Jesús Pérez Alcaide (ISBAN) commented on MYFACES-3399: -- Sorry for

Re: [core extcdi] is required to create another proposal about windowId?

Hi! The ClientSideWindowHandler solution in CODI looks good so far, but there is still a lot to do. And like every technology, it has it's pros and cons... What do you think about making the windowId provider pluggable in MyFaces core first? The REAL problem with JSF and multiple tabs is

Re: [VOTE] release of myfaces core 2.0.10

looks good +1 LieGrue, strub - Original Message - From: Leonardo Uribe lu4...@gmail.com To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Thursday, November 17, 2011 6:53 AM Subject: [VOTE] release of myfaces core 2.0.10 Hi, I was running the needed tasks to get

[jira] [Created] (TOBAGO-1049) Tree inside of the Sheet (aka TreeTable)

Tree inside of the Sheet (aka TreeTable) Key: TOBAGO-1049 URL: https://issues.apache.org/jira/browse/TOBAGO-1049 Project: MyFaces Tobago Issue Type: New Feature Reporter: Udo Schnurpfeil

[jira] [Commented] (MYFACES-3400) jsf.js: improvement of the encoding handling

[ https://issues.apache.org/jira/browse/MYFACES-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152840#comment-13152840 ] Werner Punz commented on MYFACES-3400: -- Here is a final result of my investigation.

Re: [VOTE] release of myfaces core 2.1.4 (take 2)

+1 successfully tested with our app. source release looks fine too. LieGrue, strub - Original Message - From: Leonardo Uribe lu4...@gmail.com To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Thursday, November 17, 2011 1:12 AM Subject: [VOTE] release of myfaces core

Re: [VOTE] release of myfaces core 2.0.10

+1 Regards, Jakob 2011/11/18 Mark Struberg strub...@yahoo.de: looks good +1 LieGrue, strub - Original Message - From: Leonardo Uribe lu4...@gmail.com To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Thursday, November 17, 2011 6:53 AM Subject: [VOTE] release of

Re: [VOTE] release of myfaces core 2.1.4 (take 2)

+1 Regards, Jakob 2011/11/18 Mark Struberg strub...@yahoo.de: +1 successfully tested with our app. source release looks fine too. LieGrue, strub - Original Message - From: Leonardo Uribe lu4...@gmail.com To: MyFaces Development dev@myfaces.apache.org Cc: Sent: Thursday,

[jira] [Created] (MYFACES-3402) Partial Response Writer always returns an ?xml version='1.0' encoding='utf-8'? ignoring the response encoding

Partial Response Writer always returns an ?xml version='1.0' encoding='utf-8'? ignoring the response encoding --- Key: MYFACES-3402 URL:

Re: [core extcdi] is required to create another proposal about windowId?

Hi, PS: btw, a PhD student in my institute made me aware of a trick with the browser history. I think Jakob also already researched in this direction: https://github.com/balupton/history.js/wiki/Intelligent-State-Handling This mechanism does only 1 GET request (mine does 2), but with pure

[jira] [Commented] (MYFACES-3402) Partial Response Writer always returns an ?xml version='1.0' encoding='utf-8'? ignoring the response encoding

[ https://issues.apache.org/jira/browse/MYFACES-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152873#comment-13152873 ] Werner Punz commented on MYFACES-3402: -- Additionally to that, if you pass special

[jira] [Created] (MYFACES-3403) jsf.js: uri encoding only works on UTF.-8 encoding

jsf.js: uri encoding only works on UTF.-8 encoding -- Key: MYFACES-3403 URL: https://issues.apache.org/jira/browse/MYFACES-3403 Project: MyFaces Core Issue Type: Bug Reporter:

Re: [core extcdi] is required to create another proposal about windowId?

I now tend to do the following (just atm creating a better playground example in CODI + hack on the ClientSideWindowHandler): a.) the cookie thingy is pretty bääh. it just doesn't work if a user clicks quickly through a list and opens lots of 'detail pages' on different tabs within 2 seconds.

Re: [VOTE] release of myfaces core 1.2.11

+1 On Thu, Nov 17, 2011 at 11:47 AM, Leonardo Uribe lu4...@gmail.com wrote: +1 2011/11/17 Leonardo Uribe lu4...@gmail.com: Hi, I was running the needed tasks to get the 1.2.11 release of Apache MyFaces core out. The artifacts passed all TCK tests. Please note that this vote

Re: [VOTE] release of myfaces core 1.2.11

+1 source-release.zip looks good. Happy that I dont use JSF-1.x anymore, so I cannot say anything about the runtime quality ;) LieGrue, strub From: Grant Smith work.gr...@gmail.com To: MyFaces Development dev@myfaces.apache.org Sent: Friday, November 18,

Re: [VOTE] release of myfaces core 2.1.4 (take 2)

+1 Sent from my iPhone On Nov 18, 2011, at 2:08 PM, Jakob Korherr jakob.korh...@gmail.com wrote: +1 Regards, Jakob 2011/11/18 Mark Struberg strub...@yahoo.de: +1 successfully tested with our app. source release looks fine too. LieGrue, strub - Original Message -

Re: [core extcdi] is required to create another proposal about windowId?

Hi MS The ClientSideWindowHandler solution in CODI looks good so far, but there MS is still a lot to do. MS And like every technology, it has it's pros and cons... MS What do you think about making the windowId provider pluggable in MyFaces MS core first? I have been thinking about every

Re: [core extcdi] is required to create another proposal about windowId?

1. To implement 2. it is necessary a requestId. MyFaces FlashImpl uses a counter and store its value inside a cookie The trick could be the same which I do atm for the 2nd windowId request: Each URL always contains the windowId, and the cookie name also contains the windowId. This way 2 tabs

Re: [core extcdi] is required to create another proposal about windowId?

2011/11/18 Mark Struberg strub...@yahoo.de: 1. To implement 2. it is necessary a requestId. MyFaces FlashImpl uses a counter and store its value inside a cookie The trick could be the same which I do atm for the 2nd windowId request: Each URL always contains the windowId, and the cookie