[ https://issues.apache.org/jira/browse/TOBAGO-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144572#comment-15144572 ]
Hudson commented on TOBAGO-1524: -------------------------------- SUCCESS: Integrated in tobago-3.0.x #229 (See [https://builds.apache.org/job/tobago-3.0.x/229/]) Removing local state "currentMarkup" as preparation of TOBAGO-1524. It's no longer needed, because we haven no longer a layout phase on the server. remove "throws IOException" from prepareRender() (lofwyr: [http://svn.apache.org/viewvc/?view=rev&rev=1730009]) * tobago-3.0.x/tobago-theme/tobago-theme-standard/src/main/java/org/apache/myfaces/tobago/renderkit/html/standard/standard/tag/FileRenderer.java > Use standard ajax mechanism > --------------------------- > > Key: TOBAGO-1524 > URL: https://issues.apache.org/jira/browse/TOBAGO-1524 > Project: MyFaces Tobago > Issue Type: Improvement > Components: Core > Affects Versions: 3.0.0-alpha-2 > Reporter: Dennis Kieselhorst > Priority: Critical > Fix For: 3.0.0-beta-1 > > Attachments: ajax_30.patch > > > Tobago supports Ajax from the very beginning. With JSF 2.0 Ajax became part > of the standard (f:ajax). We should move over to the standard javascript to > enhance the robustness. Currently we have several open issues related to Ajax > requests. > Here are some aspects: > * Tobago supports CSP (Content Securty Policy): So, we don't render > JavaScript directly into the HTML > * Using jsf.js for partial reloading > * Using ClientBehaviour for <tc:suggest> -- This message was sent by Atlassian JIRA (v6.3.4#6332)