Re: [JSF 2.0] Final draft available, branch synchronized
Wonderful news... I will rework the javascript ajax apis this week on thursday. Generally there is not too much work on the api side to do a helper function has been added. Werner Simon Lessard schrieb: Hi all, This is a simple post to inform you that the final JSF 2.0 draft was released yesterday (http://jcp.org/aboutJava/communityprocess/pfd/jsr314/index.html) and that the 2.0 branch is in sync with it (at least to my knowledge). Not everything is integrated of course, but all API classes and methods should be there (except enums for component attributes, I hope we can pluginize those). If you check the code you can find different kinds of TODO: // TODO: IMPLEMENT HERE Means the logic should be coded inline where the comment is. Can be found in both API and IMPL. // TODO: IMPLEMENT IMPL Means the logic should be implemented in myfaces-impl while the api side most likely throws an UnsupportedOperationException. Can be found in API only. // TODO: PLUGINIZE Means the class might be generable by maven plugin, but adding the metadta/code for it to work as yet to be done. This is mainly for the new enums for component attributes, the TODO is in the UIComponent class. // TODO: VALIDATE Means the code should be reviewed against the spec or the use case should be thought about to determine if the algorithm used is correct. Can be found in both API and IMPL. // TODO: DEFINE Means the spec is silent on the algorithm or the constant values. Found in API, currently only in ExceptionQueuedEventContext I think. I'll go to the EG with it. // TODO: REPORT Means that I must raise something I consider invalid as an issue to the EG. Found in both API and IMPL. // TODO: REFACTOR Means the code should be moved to a more logical spot. Found in Facelets mainly where I had to move some code around so that it would compile with the new API. // TODO: PROFILE Means I think an alternative algorithm could be faster, but think more thourough thinking should be put to it. Mostly found in Facelets and its extensive use of Arrays.binarySearch instead of faster but more memory consuming HashMap. Help on any part is welcome, but what's left of error handling (validating where exceptions should be shallowed or rethrown and some missing ErrorHandler code) and component tree visitiing was reserved for Google SoC I think so let not deal with those for now. Thanks, ~ Simon
[jira] Created: (TRINIDAD-1448) PPR confused about content types
PPR confused about content types Key: TRINIDAD-1448 URL: https://issues.apache.org/jira/browse/TRINIDAD-1448 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.11-core Reporter: Stephane Epardaud Something is wrong in PPR: # My browser sends an AJAX (PPR) request accepting text/html first # CoreRenderKit.createResponseWriter() calls _chooseContentType() which selects HTML # An HtmlResponseWriter is created # Since it is a PPR, the HtmlResponseWriter is wrapped inside a PPRResponseWriter # The PPRResponseWriter and XmlHttpServletResponse serve what they pretend is an XML (text/xml) document # The view rendering uses the HtmlResponseWriter to render HTML inside that PPR XML document (this is already wrong since HTML cannot be inserted in XML) # The HtmlResponseWriter uses HTMLEscapes to replace perfectly valid UTF-8 chars such as #uA0 (no-break space) by nbsp; which is NOT VALID in XML # The browser fails to load this invalid XML document as it contains HTML in some places # The PPR request fails Now, I am not sure how to patch this since it is not obvious whether the response should be forced to really be XML and thus use XhtmlResponseWriter and just bypass the mime type selection, or whether *since we are serving HTML as selected by the client* the PPRResponseWriter should serve HTML. If you don't have the time to fix this, please can you guide me so I can send a proper patch since I need this ASAP and will patch it any way works for us ;) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1423) Alignment issue in Blackberry 4.7, if tr:selectBooleanRadio is a child of tr:panelFormLayout
[ https://issues.apache.org/jira/browse/TRINIDAD-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1423: - Resolution: Fixed Fix Version/s: 1.2.12-core Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) Alignment issue in Blackberry 4.7, if tr:selectBooleanRadio is a child of tr:panelFormLayout Key: TRINIDAD-1423 URL: https://issues.apache.org/jira/browse/TRINIDAD-1423 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Environment: Blackberry 4.7 Reporter: Mamallan Uthaman Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: Trinidad-1423.patch Text and value attribute of tr:selectBooleanRadio are out of alignment, if tr:selectBooleanRadio is a child of tr:panelFormLayout. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1430) Character encoding problem with Majorra introduced by issue TRINIDAD-1272
[ https://issues.apache.org/jira/browse/TRINIDAD-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1430: - Resolution: Fixed Fix Version/s: 1.2.12-core Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) Character encoding problem with Majorra introduced by issue TRINIDAD-1272 - Key: TRINIDAD-1430 URL: https://issues.apache.org/jira/browse/TRINIDAD-1430 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Environment: JSF 1.2 RI (Majorra) Facelets 1.1.14 Glassfish 9.1 Reporter: Luka Surija Assignee: Matthias Weßendorf Fix For: 1.2.12-core Attachments: TRINIDAD-1430.patch TRINIDAD-1272 - Support for WAP2.0 Browser without JavaScript (svn revision 713294) introduced a character encoding problem with non-us characters with JSF RI (Majorra), Glassfish 9.1 and Facelets 1.1.14. The problem is not in displaying this characters, but in submitting. For example šđžćč is correctly displayed in tr:inputText, but after submitting the same value, it is displayed as Å¡Ä'Å¾Ä‡Ä . This problem is not only with croatian characters, but also with German umlauts and probably other non us characters. This error is related with error in server log: PWC4011: Unable to set request character encoding to UTF-8 from context /, because request parameters have already been read, or ServletRequest.getReader() has already been called -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTVAL-39) extensible skip validation support
[ https://issues.apache.org/jira/browse/EXTVAL-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTVAL-39. Resolution: Fixed Fix Version/s: 1.1.2-SNAPSHOT 1.2.2-SNAPSHOT extensible skip validation support -- Key: EXTVAL-39 URL: https://issues.apache.org/jira/browse/EXTVAL-39 Project: MyFaces Extensions Validator Issue Type: Improvement Components: Core Affects Versions: 1.2.1, 1.1.1 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Priority: Minor Fix For: 1.2.2-SNAPSHOT, 1.1.2-SNAPSHOT skipable validation strategies are marked with @SkipValidationSupport it should be possible to provide custom markers as well as the class names of the validation strategies. besides custom markers it allows to provide add-ons for custom configuration approaches. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTVAL-39) extensible skip validation support
extensible skip validation support -- Key: EXTVAL-39 URL: https://issues.apache.org/jira/browse/EXTVAL-39 Project: MyFaces Extensions Validator Issue Type: Improvement Components: Core Affects Versions: 1.1.1, 1.2.1 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Priority: Minor skipable validation strategies are marked with @SkipValidationSupport it should be possible to provide custom markers as well as the class names of the validation strategies. besides custom markers it allows to provide add-ons for custom configuration approaches. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1427) In mobile browsers, date picker of tr:inputDate is rendered when it is not working.
[ https://issues.apache.org/jira/browse/TRINIDAD-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1427: - Resolution: Fixed Fix Version/s: 1.2.12-core Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) In mobile browsers, date picker of tr:inputDate is rendered when it is not working. - Key: TRINIDAD-1427 URL: https://issues.apache.org/jira/browse/TRINIDAD-1427 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Environment: Windows Mobile 6 Reporter: Mamallan Uthaman Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1427.patch Currently, data picker of tr:inputDate is not working in mobile browsers. An issue(Trinidad-1203) was created to fix this problem. The current patch for this issue hasn't fixed the problem so it is better to remove the date picker from tr:inputDate until Trinidad-1203 is resolved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1425) In mobile browsers, onClick event script not working for tr:selectBooleanRadio
[ https://issues.apache.org/jira/browse/TRINIDAD-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1425: - Resolution: Fixed Fix Version/s: 1.2.12-core Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) In mobile browsers, onClick event script not working for tr:selectBooleanRadio Key: TRINIDAD-1425 URL: https://issues.apache.org/jira/browse/TRINIDAD-1425 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Environment: windows mobile 6 Reporter: Mamallan Uthaman Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1425.patch In mobile browsers, onClick script of tr:SelectBooleanRadio is not working if the autosubmit is enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1416) In mobile browsers, inlineStyle attribute of tr:train is not working
[ https://issues.apache.org/jira/browse/TRINIDAD-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1416: - Resolution: Fixed Fix Version/s: 1.2.12-core Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) In mobile browsers, inlineStyle attribute of tr:train is not working --- Key: TRINIDAD-1416 URL: https://issues.apache.org/jira/browse/TRINIDAD-1416 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.10-core Environment: Windows mobile 6 Reporter: Mamallan Uthaman Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1416.patch For mobile browsers, tr:train is not supporting inlineStyle attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1426) In mobile browsers, a warning message is generated on using action facet in tr:table
[ https://issues.apache.org/jira/browse/TRINIDAD-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1426: - Resolution: Fixed Fix Version/s: 1.2.12-core Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) In mobile browsers, a warning message is generated on using action facet in tr:table --- Key: TRINIDAD-1426 URL: https://issues.apache.org/jira/browse/TRINIDAD-1426 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.11-core Environment: Windows Mobile 6 Reporter: Mamallan Uthaman Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1426-branch.patch, TRINIDAD-1426.patch On using action facet in tr:table, below warning message is generated WARNING: Illegal HTML: cannot put a td element in a div element. I propose to fix the underlying cause for this warning message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [JSF 2.0] Final draft available, branch synchronized
yes, correct. I think I should pay more attention to the (so called) open mailing list (which is seriously only semi-open) -Matthias On Tue, Apr 7, 2009 at 10:37 AM, Werner Punz werner.p...@gmail.com wrote: Wonderful news... I will rework the javascript ajax apis this week on thursday. Generally there is not too much work on the api side to do a helper function has been added. Werner Simon Lessard schrieb: Hi all, This is a simple post to inform you that the final JSF 2.0 draft was released yesterday (http://jcp.org/aboutJava/communityprocess/pfd/jsr314/index.html) and that the 2.0 branch is in sync with it (at least to my knowledge). Not everything is integrated of course, but all API classes and methods should be there (except enums for component attributes, I hope we can pluginize those). If you check the code you can find different kinds of TODO: // TODO: IMPLEMENT HERE Means the logic should be coded inline where the comment is. Can be found in both API and IMPL. // TODO: IMPLEMENT IMPL Means the logic should be implemented in myfaces-impl while the api side most likely throws an UnsupportedOperationException. Can be found in API only. // TODO: PLUGINIZE Means the class might be generable by maven plugin, but adding the metadta/code for it to work as yet to be done. This is mainly for the new enums for component attributes, the TODO is in the UIComponent class. // TODO: VALIDATE Means the code should be reviewed against the spec or the use case should be thought about to determine if the algorithm used is correct. Can be found in both API and IMPL. // TODO: DEFINE Means the spec is silent on the algorithm or the constant values. Found in API, currently only in ExceptionQueuedEventContext I think. I'll go to the EG with it. // TODO: REPORT Means that I must raise something I consider invalid as an issue to the EG. Found in both API and IMPL. // TODO: REFACTOR Means the code should be moved to a more logical spot. Found in Facelets mainly where I had to move some code around so that it would compile with the new API. // TODO: PROFILE Means I think an alternative algorithm could be faster, but think more thourough thinking should be put to it. Mostly found in Facelets and its extensive use of Arrays.binarySearch instead of faster but more memory consuming HashMap. Help on any part is welcome, but what's left of error handling (validating where exceptions should be shallowed or rethrown and some missing ErrorHandler code) and component tree visitiing was reserved for Google SoC I think so let not deal with those for now. Thanks, ~ Simon -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Trinidad Warnings
Hi, can someone told me that the reason for the following warnings is? - MenuContentHa W org.apache.myfaces.trinidadinternal.menu.MenuContentHandlerImpl endDocument CREATE_TREE_WARNING: Empty Tree! - GlobalConfigu W org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl _attachRequestContext RequestContext had not been properly released on earlier request. Best Regards, Jan
[jira] Created: (TRINIDAD-1449) Support for onclick Attribute for tr:showDetail
Support for onclick Attribute for tr:showDetail --- Key: TRINIDAD-1449 URL: https://issues.apache.org/jira/browse/TRINIDAD-1449 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 1.2.11-core Reporter: Bernd Bohmann Priority: Minor It would be nice if tr:showDetail supports the onclick attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1449) Support for onclick Attribute for tr:showDetail
[ https://issues.apache.org/jira/browse/TRINIDAD-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Bohmann updated TRINIDAD-1449: Status: Patch Available (was: Open) Support for onclick Attribute for tr:showDetail --- Key: TRINIDAD-1449 URL: https://issues.apache.org/jira/browse/TRINIDAD-1449 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 1.2.11-core Reporter: Bernd Bohmann Priority: Minor Attachments: TRINIDAD-1449.patch It would be nice if tr:showDetail supports the onclick attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Trinidad Warnings
On Tue, Apr 7, 2009 at 4:18 PM, Zmitko, Jan jan.zmi...@adbag.de wrote: Hi, can someone told me that the reason for the following warnings is? - MenuContentHa W org.apache.myfaces.trinidadinternal.menu.MenuContentHandlerImpl endDocument CREATE_TREE_WARNING: Empty Tree! For [1] we added code to create menu model if tree is empty. - GlobalConfigu W org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl _attachRequestContext RequestContext had not been properly released on earlier request. Is the filter exectured twice ? Or do you have multiple Trinidad JARs (two -impl or so) on the classpath ? -Matthias [1] http://issues.apache.org/jira/browse/TRINIDAD-101 Best Regards, Jan -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Commented: (TRINIDAD-1449) Support for onclick Attribute for tr:showDetail
[ https://issues.apache.org/jira/browse/TRINIDAD-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12696551#action_12696551 ] Matthias Weßendorf commented on TRINIDAD-1449: -- looks like onclick is not the only one that is missing Support for onclick Attribute for tr:showDetail --- Key: TRINIDAD-1449 URL: https://issues.apache.org/jira/browse/TRINIDAD-1449 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 1.2.11-core Reporter: Bernd Bohmann Priority: Minor Attachments: TRINIDAD-1449.patch It would be nice if tr:showDetail supports the onclick attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
reCaptcha with Trinidad
Has anyone used reCaptcha in a Trinidad app? I'm trying to figure out the best way to do this. If anyone has successfully used reCaptcha, I would be interested in seeing how it was done. This may be a good component to add in a future release. Information about the API is available at http://recaptcha.net/ -Alan
[jira] Commented: (TRINIDAD-1449) Support for onclick Attribute for tr:showDetail
[ https://issues.apache.org/jira/browse/TRINIDAD-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12696557#action_12696557 ] Bernd Bohmann commented on TRINIDAD-1449: - Yes, but I need onclick only :-) Support for onclick Attribute for tr:showDetail --- Key: TRINIDAD-1449 URL: https://issues.apache.org/jira/browse/TRINIDAD-1449 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 1.2.11-core Reporter: Bernd Bohmann Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1449.patch It would be nice if tr:showDetail supports the onclick attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1449) Support for onclick Attribute for tr:showDetail
[ https://issues.apache.org/jira/browse/TRINIDAD-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf updated TRINIDAD-1449: - Resolution: Fixed Fix Version/s: 1.2.12-core Assignee: Matthias Weßendorf Status: Resolved (was: Patch Available) Support for onclick Attribute for tr:showDetail --- Key: TRINIDAD-1449 URL: https://issues.apache.org/jira/browse/TRINIDAD-1449 Project: MyFaces Trinidad Issue Type: Improvement Components: Components Affects Versions: 1.2.11-core Reporter: Bernd Bohmann Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1449.patch It would be nice if tr:showDetail supports the onclick attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1416) In mobile browsers, inlineStyle attribute of tr:train is not working
[ https://issues.apache.org/jira/browse/TRINIDAD-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12696647#action_12696647 ] Mamallan Uthaman commented on TRINIDAD-1416: Please apply this patch to the branch 1.2.11.2 as well. In mobile browsers, inlineStyle attribute of tr:train is not working --- Key: TRINIDAD-1416 URL: https://issues.apache.org/jira/browse/TRINIDAD-1416 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.10-core Environment: Windows mobile 6 Reporter: Mamallan Uthaman Assignee: Matthias Weßendorf Priority: Minor Fix For: 1.2.12-core Attachments: TRINIDAD-1416.patch For mobile browsers, tr:train is not supporting inlineStyle attribute. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: reCaptcha with Trinidad
FYI there's a reCaptche JSF component in PrimeFaces. See the demo here; http://www.rehberharitam.com/primefaces-examples/ui/captcha.jsf On Apr 7, 2009, at 3:43 PM, Alan Hancock wrote: Has anyone used reCaptcha in a Trinidad app? I'm trying to figure out the best way to do this. If anyone has successfully used reCaptcha, I would be interested in seeing how it was done. This may be a good component to add in a future release. Information about the API is available at http://recaptcha.net/ -Alan
[jira] Created: (ORCHESTRA-40) A transaction token component inspired by the struts transaction processor
A transaction token component inspired by the struts transaction processor -- Key: ORCHESTRA-40 URL: https://issues.apache.org/jira/browse/ORCHESTRA-40 Project: MyFaces Orchestra Issue Type: New Feature Components: Conversation Affects Versions: 1.3.1 Reporter: Bernd Bohmann A transactionToken Component for orchestra inspired by the struts transaction processor. The transaction token is to be used for enforcing a single request for a particular transaction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ORCHESTRA-40) A transaction token component inspired by the struts transaction processor
[ https://issues.apache.org/jira/browse/ORCHESTRA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Bohmann updated ORCHESTRA-40: --- Status: Patch Available (was: Open) A transaction token component inspired by the struts transaction processor -- Key: ORCHESTRA-40 URL: https://issues.apache.org/jira/browse/ORCHESTRA-40 Project: MyFaces Orchestra Issue Type: New Feature Components: Conversation Affects Versions: 1.3.1 Reporter: Bernd Bohmann Assignee: Simon Kitching Attachments: ORCHESTRA-40.patch A transactionToken Component for orchestra inspired by the struts transaction processor. The transaction token is to be used for enforcing a single request for a particular transaction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: reCaptcha with Trinidad
Many thanks! I'll check it out. -Alan via iPhone On Apr 7, 2009, at 1:33 PM, Cagatay Civici cagatay.civ...@gmail.com wrote: FYI there's a reCaptche JSF component in PrimeFaces. See the demo here; http://www.rehberharitam.com/primefaces-examples/ui/captcha.jsf On Apr 7, 2009, at 3:43 PM, Alan Hancock wrote: Has anyone used reCaptcha in a Trinidad app? I'm trying to figure out the best way to do this. If anyone has successfully used reCaptcha, I would be interested in seeing how it was done. This may be a good component to add in a future release. Information about the API is available at http://recaptcha.net/ -Alan
[orchestra] transaction token patch, session timeout fix
Hi Bernd, I'm keen to look at your patch in JIRA, but it will probably have to wait until this weekend. I hope that's ok https://issues.apache.org/jira/browse/ORCHESTRA-40 This reminds me that you did a follow-up patch (r759100) to your previous Orchestra patch, and Mario had a few comments on it. We both have been busy though, and haven't got around to emailing about it. Your commit was about preventing a cannot remove current contexxt conversation exception while clearing conversations. I presume this actually happened for you, but neither Mario nor I can figure out why that would ever happen. Is there a chance you can look into what actually causes this? Or suggest how we could duplicate this? The SessionListener should never have a FrameworkAdapter in its thread, and so should never have any request param that references a conversation context id. So it's puzzling why you would get that exception. It would also be nice if the new code in the SessionListener would use a finally block to reset the FrameworkAdapter to null, so that if anything does throw an exception then we don't leak the threadlocal var. I can do that myself later .. but if you're investigating the question above, then maybe you could test this at the same time? Also, it might be nice to remove the context from the wiper thread before destroying it, rather than after... Cheers, Simon
[jira] Resolved: (EXTVAL-40) metadata extraction interceptor
[ https://issues.apache.org/jira/browse/EXTVAL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved EXTVAL-40. Resolution: Fixed Fix Version/s: 1.1.2-SNAPSHOT 1.2.2-SNAPSHOT metadata extraction interceptor --- Key: EXTVAL-40 URL: https://issues.apache.org/jira/browse/EXTVAL-40 Project: MyFaces Extensions Validator Issue Type: New Feature Components: Core Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.2.2-SNAPSHOT, 1.1.2-SNAPSHOT interceptor which is called after the metadata extraction and before the validation process it allows to add/change/remove constraints of the target property to remove all metadata entries a new api is needed: PropertyInformation#resetMetaDataEntries the method call is logged to avoid that an add-on removes metadata entries without logging it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTVAL-40) metadata extraction interceptor
metadata extraction interceptor --- Key: EXTVAL-40 URL: https://issues.apache.org/jira/browse/EXTVAL-40 Project: MyFaces Extensions Validator Issue Type: New Feature Components: Core Reporter: Gerhard Petracek Assignee: Gerhard Petracek interceptor which is called after the metadata extraction and before the validation process it allows to add/change/remove constraints of the target property to remove all metadata entries a new api is needed: PropertyInformation#resetMetaDataEntries the method call is logged to avoid that an add-on removes metadata entries without logging it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
