[jira] Updated: (MYFACES-2155) HtmlLinkRenderer did not recognize ankers (#)
[ https://issues.apache.org/jira/browse/MYFACES-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-2155: --- Status: Patch Available (was: Open) > HtmlLinkRenderer did not recognize ankers (#) > - > > Key: MYFACES-2155 > URL: https://issues.apache.org/jira/browse/MYFACES-2155 > Project: MyFaces Core > Issue Type: Bug > Reporter: Martin Haimberger > > HtmlLinkRenderer did not recognize ankers (#) and encoded them wrong if there > were f:params used (-> url#anker?paramname=paramvalue instead of > url?paramname=paramvalue#anker) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2155) HtmlLinkRenderer did not recognize ankers (#)
HtmlLinkRenderer did not recognize ankers (#) - Key: MYFACES-2155 URL: https://issues.apache.org/jira/browse/MYFACES-2155 Project: MyFaces Core Issue Type: Bug Reporter: Martin Haimberger HtmlLinkRenderer did not recognize ankers (#) and encoded them wrong if there were f:params used (-> url#anker?paramname=paramvalue instead of url?paramname=paramvalue#anker) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [proposal] jsf validation with annotations
Hi Gerhard, sounds fancy and simple! Nice work! I think i will take a closer look. How stable is it in the mean time? Regards, Martin On 4/3/08, Gerhard Petracek <[EMAIL PROTECTED]> wrote: > > sev-en is a new jsf-extension. > > sev-en allows jsf validation with annotations! > > some central features: > - cross-component validation (including cross-entity validation) > - support for jpa based validation > - zero configuration > - extensible (e.g. custom annotations) > > you will find some previews (descriptions [1], examples [2] and much more) > at the sev-en section [3] of my new open source blog. > > what's your opinion about this extension? > > regards, > gerhard > > [1] http://os890.blogspot.com/2008/03/new-jsf-extension.html > [2] http://os890.blogspot.com/2008/04/sev-en-preview-short-example.html > [3] http://os890.blogspot.com/search/label/sev-en > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces
[jira] Commented: (TOMAHAWK-1190) Exception in t:columns
[ https://issues.apache.org/jira/browse/TOMAHAWK-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566991#action_12566991 ] Martin Haimberger commented on TOMAHAWK-1190: - Hi Martin, i have corrected the problem with patch v2. Now they are Boolean Objects (the convention is stays for a boolean and not a Boolean). regards, Martin Haimberger > Exception in t:columns > -- > > Key: TOMAHAWK-1190 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1190 > Project: MyFaces Tomahawk > Issue Type: Bug > Reporter: Martin Haimberger >Assignee: Martin Haimberger > Attachments: HtmlColumns-patch_issue_1190_v2.patch > > > Hi, > the setter for the attributes sortable, defaultSorted, groupBy are Boolean > instead of boolean, which causes a exception if using this attributes. > Regards, > Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOMAHAWK-160) ADF Renderer Kit and HtmlCommandLink not rendered
[
https://issues.apache.org/jira/browse/TOMAHAWK-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566539#action_12566539
]
Martin Haimberger commented on TOMAHAWK-160:
Hi,
i will close this issue, because a patch (see issue 117) is already commited
and this is working again.
Regards,
Martin Haimberger
> ADF Renderer Kit and HtmlCommandLink not rendered
> -
>
> Key: TOMAHAWK-160
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-160
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Data Scroller
>Affects Versions: 1.1.2-SNAPSHOT
> Environment: ADF 10.1.3.04, SUN RI 1.1.01
>Reporter: Claudio Tasso
>Priority: Critical
> Attachments: patch1.patch
>
>
> ADF requires the installation of its custom RendererKit (oracle.adf.core),
> but it does not work well with some Tomahawk components.
> For example, let's examine the HtmlDataScrollerRenderer, which creates a
> HtmlCommandLink during the encoding of the HtmlDataScroller component.
> This is the code which creates the HtmlCommandLink:
> HtmlCommandLink link = (HtmlCommandLink) application
>.createComponent(HtmlCommandLink.COMPONENT_TYPE);
>
> scroller.getChildren().add(link);
> It seems to be quite standard: the compoent is created and the it's added to
> the HtmlDataScroller componet.
> This code works very well when the faces-config.xml DOES NOT contain the
> following line:
> oracle.adf.core
> But when this line is inserted, the HtmlCommandLink does not appear in the
> rendered page which is sent to the browser as HTML.
> The following JSP code contains an example:
> <%@ page language="java" pageEncoding="UTF-8"%>
> <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h" %>
> <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f" %>
> <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t"%>
>
>
>
>
>
>
>
>
>
>preserveDataModel="false" value="#{TestBean.persons}" var="item">
>
>value="#{item.name}">
>
>
>value="#{item.surname}">
>
>
>
>
> <%-- When the content of this facet
> is rendered, it should be surrounded by a link --%>
>
>
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TOMAHAWK-160) ADF Renderer Kit and HtmlCommandLink not rendered
[
https://issues.apache.org/jira/browse/TOMAHAWK-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Haimberger updated TOMAHAWK-160:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
see issue 117
> ADF Renderer Kit and HtmlCommandLink not rendered
> -
>
> Key: TOMAHAWK-160
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-160
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Data Scroller
>Affects Versions: 1.1.2-SNAPSHOT
> Environment: ADF 10.1.3.04, SUN RI 1.1.01
>Reporter: Claudio Tasso
>Priority: Critical
> Attachments: patch1.patch
>
>
> ADF requires the installation of its custom RendererKit (oracle.adf.core),
> but it does not work well with some Tomahawk components.
> For example, let's examine the HtmlDataScrollerRenderer, which creates a
> HtmlCommandLink during the encoding of the HtmlDataScroller component.
> This is the code which creates the HtmlCommandLink:
> HtmlCommandLink link = (HtmlCommandLink) application
>.createComponent(HtmlCommandLink.COMPONENT_TYPE);
>
> scroller.getChildren().add(link);
> It seems to be quite standard: the compoent is created and the it's added to
> the HtmlDataScroller componet.
> This code works very well when the faces-config.xml DOES NOT contain the
> following line:
> oracle.adf.core
> But when this line is inserted, the HtmlCommandLink does not appear in the
> rendered page which is sent to the browser as HTML.
> The following JSP code contains an example:
> <%@ page language="java" pageEncoding="UTF-8"%>
> <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h" %>
> <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f" %>
> <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t"%>
>
>
>
>
>
>
>
>
>
>preserveDataModel="false" value="#{TestBean.persons}" var="item">
>
>value="#{item.name}">
>
>
>value="#{item.surname}">
>
>
>
>
> <%-- When the content of this facet
> is rendered, it should be surrounded by a link --%>
>
>
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TOMAHAWK-1190) Exception in t:columns
[ https://issues.apache.org/jira/browse/TOMAHAWK-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated TOMAHAWK-1190: Status: Patch Available (was: Open) > Exception in t:columns > -- > > Key: TOMAHAWK-1190 > URL: https://issues.apache.org/jira/browse/TOMAHAWK-1190 > Project: MyFaces Tomahawk > Issue Type: Bug > Reporter: Martin Haimberger > Assignee: Martin Haimberger > Attachments: HtmlColumns-patch_issue_1190.patch > > > Hi, > the setter for the attributes sortable, defaultSorted, groupBy are Boolean > instead of boolean, which causes a exception if using this attributes. > Regards, > Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TOMAHAWK-1190) Exception in t:columns
Exception in t:columns -- Key: TOMAHAWK-1190 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1190 Project: MyFaces Tomahawk Issue Type: Bug Reporter: Martin Haimberger Attachments: HtmlColumns-patch_issue_1190.patch Hi, the setter for the attributes sortable, defaultSorted, groupBy are Boolean instead of boolean, which causes a exception if using this attributes. Regards, Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TOMAHAWK-117) dataScroller bug when using ADF - navigation icons not clickable
[
https://issues.apache.org/jira/browse/TOMAHAWK-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Haimberger updated TOMAHAWK-117:
---
Status: Patch Available (was: Open)
> dataScroller bug when using ADF - navigation icons not clickable
>
>
> Key: TOMAHAWK-117
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-117
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Data Scroller
> Environment: Windows/Unix/Weblogic
>Reporter: James Hickey
> Assignee: Martin Haimberger
> Attachments: datascroller_patch_issue_117.patch
>
>
> Hi - I have a strange issue with the t:dataScroller component where it
> renders correctly but is not accessible (i.e. renders no links) for any of
> the navigation links for forward/back buttons. The parent dataTable renders
> fine, complete with sortable headers. It seems that this might be an issue
> when ADF is deployed as deploying the separate samples WAR works fine. Below
> is a snippet of my JSP - I can replicate the behaviour when surrounding this
> with an f:view tag - help appreciated!
> PS - same issue both with release 1.1.1 and with 1.1.2 Nightly. Also seems to
> make no difference whether I use myFaces or the RI
> Thanks
> James
>headerClass="standardTable_Header" footerClass="standardTable_Header"
> rowClasses="standardTable_Row1,standardTable_Row2"
> columnClasses="standardTable_Column,standardTable_ColumnCentered,standardTable_Column"
> var="trade" value="#{ipbBuySellQueryController2.queryResultList}"
> preserveDataModel="false" rows="25" rowId="#{trade.id}"
> rowOnMouseOver="this.style.backgroundColor='#A5CBFF'"
> rowOnMouseOut="this.style.backgroundColor='#E0'"
> rowOnClick="this.style.backgroundColor='#FFE0E0'"
> rowOnDblClick="this.style.backgroundColor='#E0E0E0'"
> sortColumn="#{ipbBuySellQueryController2.sort}"
> sortAscending="#{ipbBuySellQueryController2.ascending}" preserveSort="true">
>
>
>value="#{trade.id}"/>
>
>
>
>
>
>
>
>
>
>
>value="#{trade.clientDescription}"/>
>
>
>
>
>
>
>
>
>
>
>value="#{trade.accountDescription}"/>
>
>
>fastStep="2" pageCountVar="pageCount" pageIndexVar="pageIndex"
> styleClass="scroller" paginator="true" paginatorMaxPages="10"
> paginatorTableClass="paginator"
> paginatorActiveColumnStyle="font-weight:bold;">
>
>url="/images/arrow-first.gif" border="1"/>
>
>
>url="/images/arrow-last.gif" border="1"/>
>
>
>url="/images/arrow-previous.gif" border="1"/>
>
>
>
[jira] Updated: (MYFACES-1809) Linkrenderer with TrinidadForm does not render parameters
[ https://issues.apache.org/jira/browse/MYFACES-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1809: --- Status: Patch Available (was: Open) > Linkrenderer with TrinidadForm does not render parameters > - > > Key: MYFACES-1809 > URL: https://issues.apache.org/jira/browse/MYFACES-1809 > Project: MyFaces Core > Issue Type: Bug > Components: General > Reporter: Martin Haimberger > Attachments: link_renderer_patch_issue_1809.patch > > > Hi, > If a Trinidad form is used with HtmlCommandLinks, links are rendered, but > link-parameters are ignored. > Regards, > Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1809) Linkrenderer with TrinidadForm does not render parameters
Linkrenderer with TrinidadForm does not render parameters - Key: MYFACES-1809 URL: https://issues.apache.org/jira/browse/MYFACES-1809 Project: MyFaces Core Issue Type: Bug Components: General Reporter: Martin Haimberger Hi, If a Trinidad form is used with HtmlCommandLinks, links are rendered, but link-parameters are ignored. Regards, Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Tomahawk, Myfaces 1.2 and Tomcat 6
Hi *, anyone running Tomahawk with MyFaces 12 and Tomcat 6 successfully? I have created the intellij project with the -Djsf=12 parameter, which is working fine for the creation, but no luck for running the whole thing. As Bruno has written, the jetty plugin works fine and starts. Anyone experiences with this? Regards, Martin Haimberger
[jira] Updated: (MYFACES-1628) Migrate Partial State Saving to 1.2
[ https://issues.apache.org/jira/browse/MYFACES-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1628: --- Status: Patch Available (was: Open) > Migrate Partial State Saving to 1.2 > --- > > Key: MYFACES-1628 > URL: https://issues.apache.org/jira/browse/MYFACES-1628 > Project: MyFaces Core > Issue Type: New Feature > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT > Reporter: Martin Haimberger > Assigned To: Martin Haimberger > Fix For: 1.2.0-SNAPSHOT > > Attachments: psspatch_MYFACES_1628.tar.gz > > > Migrate Partial State Saving to MyFaces 1.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1628) Migrate Partial State Saving to 1.2
Migrate Partial State Saving to 1.2 --- Key: MYFACES-1628 URL: https://issues.apache.org/jira/browse/MYFACES-1628 Project: MyFaces Core Issue Type: New Feature Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Reporter: Martin Haimberger Assigned To: Martin Haimberger Fix For: 1.2.0-SNAPSHOT Migrate Partial State Saving to MyFaces 1.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Tobago] demos ?
Hello Matthias, i will add the Tobago demos to the irian.at server as soon as possible. Regards, Martin Haimberger On 5/4/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Hello, anyone able to add the Tobago demos to the irian.at server as well ? -Matthias -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[jira] Updated: (MYFACES-1621) ViewResponseWrapper does not wrapped the OutputStreams
[ https://issues.apache.org/jira/browse/MYFACES-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1621: --- Status: Patch Available (was: Open) > ViewResponseWrapper does not wrapped the OutputStreams > -- > > Key: MYFACES-1621 > URL: https://issues.apache.org/jira/browse/MYFACES-1621 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT > Reporter: Martin Haimberger > Assigned To: Martin Haimberger > Fix For: 1.2.0-SNAPSHOT > > Attachments: MyFaces-1621.patch > > > If the wrapped Response is used and getOutputStream() is called, a null > pointer exception or an illegalState Exception is thrown. Thats because of > the ViewResponseWrapper does not care about OutputStreams and expects that > every wrapped Response uses the Writer. > Regards, > Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1621) ViewResponseWrapper does not wrapped the OutputStreams
ViewResponseWrapper does not wrapped the OutputStreams -- Key: MYFACES-1621 URL: https://issues.apache.org/jira/browse/MYFACES-1621 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Reporter: Martin Haimberger Assigned To: Martin Haimberger Fix For: 1.2.0-SNAPSHOT If the wrapped Response is used and getOutputStream() is called, a null pointer exception or an illegalState Exception is thrown. Thats because of the ViewResponseWrapper does not care about OutputStreams and expects that every wrapped Response uses the Writer. Regards, Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1606) dataTable with facet does not work
dataTable with facet does not work -- Key: MYFACES-1606 URL: https://issues.apache.org/jira/browse/MYFACES-1606 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Environment: Tomcat 6.0.10 Reporter: Martin Haimberger Fix For: 1.2.0-SNAPSHOT Hy, if i use a h:dataTable and use facet inside it like: an exception during the rendering is thrown: avax.servlet.ServletException: Must be called before the start element is closed (attribute 'scope') javax.faces.webapp.FacesServlet.service(FacesServlet.java:152) root cause java.lang.IllegalStateException: Must be called before the start element is closed (attribute 'scope') org.apache.myfaces.shared_impl.renderkit.html.HtmlResponseWriterImpl.writeAttribute(HtmlResponseWriterImpl.java:297) org.apache.myfaces.shared_impl.renderkit.html.HtmlTableRendererBase.renderColumnHeaderCell(HtmlTableRendererBase.java:835) org.apache.myfaces.shared_impl.renderkit.html.HtmlTableRendererBase.renderColumnChildHeaderOrFooterRow(HtmlTableRendererBase.java:777) org.apache.myfaces.shared_impl.renderkit.html.HtmlTableRendererBase.renderColumnHeaderOrFooterRow(HtmlTableRendererBase.java:741) org.apache.myfaces.shared_impl.renderkit.html.HtmlTableRendererBase.renderColumnHeaderRow(HtmlTableRendererBase.java:671) org.apache.myfaces.shared_impl.renderkit.html.HtmlTableRendererBase.renderFacet(HtmlTableRendererBase.java:574) org.apache.myfaces.shared_impl.renderkit.html.HtmlTableRendererBase.beforeBody(HtmlTableRendererBase.java:413) org.apache.myfaces.shared_impl.renderkit.html.HtmlTableRendererBase.encodeChildren(HtmlTableRendererBase.java:118) javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:527) org.apache.myfaces.shared_impl.renderkit.RendererUtils.renderChild(RendererUtils.java:438) org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.renderChildren(HtmlGridRendererBase.java:216) org.apache.myfaces.shared_impl.renderkit.html.HtmlGridRendererBase.encodeEnd(HtmlGridRendererBase.java:98) javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:539) javax.faces.component.UIComponent.encodeAll(UIComponent.java:250) javax.faces.component.UIComponent.encodeAll(UIComponent.java:247) javax.faces.component.UIComponent.encodeAll(UIComponent.java:247) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:314) org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132) javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) without facets there is no problem. Regards, Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1605) h:selectBooleanCheckbox h:selectManyCheckbox h:selectManyListbox h:selectManyMenu h:selectOneListbox h:selectOneMenu h:selectOneRadio broken
[
https://issues.apache.org/jira/browse/MYFACES-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Haimberger updated MYFACES-1605:
---
Status: Patch Available (was: Open)
> h:selectBooleanCheckbox h:selectManyCheckbox h:selectManyListbox
> h:selectManyMenu h:selectOneListbox h:selectOneMenu h:selectOneRadio broken
>
>
> Key: MYFACES-1605
> URL: https://issues.apache.org/jira/browse/MYFACES-1605
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-252
>Affects Versions: 1.2.0-SNAPSHOT
> Environment: JSF 1.2 with tomcat 6.0.10
> Reporter: Martin Haimberger
> Assigned To: Martin Haimberger
>Priority: Critical
> Fix For: 1.2.0-SNAPSHOT
>
> Attachments: selectitems.MYFACES-1605.patch
>
>
> Hi,
> Following Components are broken:
> h:selectBooleanCheckbox
> h:selectManyCheckbox
> h:selectManyListbox
> h:selectManyMenu
> h:selectOneListbox
> h:selectOneMenu
> h:selectOneRadio
> i used:
>
> value="#{testbean.entries}">
>
> the testbean.entires returns a list of SelectItems and entrie is a String.
> In the current MyFaces 1.1 Implementation this is working.
> the Stacktrace:
> javax.servlet.ServletException: /helloWorld.jsp(25,20) Unable to find setter
> method for attribute: value
> javax.faces.webapp.FacesServlet.service(FacesServlet.java:152)
> root cause
> javax.faces.FacesException: /helloWorld.jsp(25,20) Unable to find setter
> method for attribute: value
>
> org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:340)
>
> org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:260)
>
> org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
>
> org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
> javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
> root cause
> org.apache.jasper.JasperException: /helloWorld.jsp(25,20) Unable to find
> setter method for attribute: value
>
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
>
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
>
> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:148)
>
> org.apache.jasper.compiler.Generator$GenerateVisitor.evaluateAttribute(Generator.java:2756)
>
> org.apache.jasper.compiler.Generator$GenerateVisitor.generateSetters(Generator.java:2985)
>
> org.apache.jasper.compiler.Generator$GenerateVisitor.generateCustomStart(Generator.java:2169)
>
> org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1689)
> org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>
> org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1705)
> org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>
> org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1705)
> org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
>
> org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1705)
> org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
> org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
> org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
> org.apache.jasper.compiler.Generator.generate(Generator.java:3394)
> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:210)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
> org.apache.j
[jira] Created: (MYFACES-1605) h:selectBooleanCheckbox h:selectManyCheckbox h:selectManyListbox h:selectManyMenu h:selectOneListbox h:selectOneMenu h:selectOneRadio broken
h:selectBooleanCheckbox h:selectManyCheckbox h:selectManyListbox h:selectManyMenu h:selectOneListbox h:selectOneMenu h:selectOneRadio broken Key: MYFACES-1605 URL: https://issues.apache.org/jira/browse/MYFACES-1605 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Environment: JSF 1.2 with tomcat 6.0.10 Reporter: Martin Haimberger Priority: Critical Fix For: 1.2.0-SNAPSHOT Hi, Following Components are broken: h:selectBooleanCheckbox h:selectManyCheckbox h:selectManyListbox h:selectManyMenu h:selectOneListbox h:selectOneMenu h:selectOneRadio i used: the testbean.entires returns a list of SelectItems and entrie is a String. In the current MyFaces 1.1 Implementation this is working. the Stacktrace: javax.servlet.ServletException: /helloWorld.jsp(25,20) Unable to find setter method for attribute: value javax.faces.webapp.FacesServlet.service(FacesServlet.java:152) root cause javax.faces.FacesException: /helloWorld.jsp(25,20) Unable to find setter method for attribute: value org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:340) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:260) org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132) javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) root cause org.apache.jasper.JasperException: /helloWorld.jsp(25,20) Unable to find setter method for attribute: value org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:148) org.apache.jasper.compiler.Generator$GenerateVisitor.evaluateAttribute(Generator.java:2756) org.apache.jasper.compiler.Generator$GenerateVisitor.generateSetters(Generator.java:2985) org.apache.jasper.compiler.Generator$GenerateVisitor.generateCustomStart(Generator.java:2169) org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1689) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1705) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1705) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1705) org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386) org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392) org.apache.jasper.compiler.Node$Root.accept(Node.java:489) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336) org.apache.jasper.compiler.Generator.generate(Generator.java:3394) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:210) org.apache.jasper.compiler.Compiler.compile(Compiler.java:306) org.apache.jasper.compiler.Compiler.compile(Compiler.java:286) org.apache.jasper.compiler.Compiler.compile(Compiler.java:273) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:308) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:334) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:260) org.apache.myfaces.lifecycle.RenderResponseExecutor.execute
[jira] Commented: (MYFACES-1563) Re-rendered input components redisplay their locale value on non-immediate action
[ https://issues.apache.org/jira/browse/MYFACES-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492224 ] Martin Haimberger commented on MYFACES-1563: Hi, are u sure that you have tried this with jsf 1.2? The example is not working at all with the jsf 1.2 impl right now. Regards, Martin Haimberger > Re-rendered input components redisplay their locale value on non-immediate > action > - > > Key: MYFACES-1563 > URL: https://issues.apache.org/jira/browse/MYFACES-1563 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.1.5 > Environment: Tomcat 5.5, Jetty 6.1, Java 1.4.2, Java 1.5.0 >Reporter: sarah haas >Priority: Critical > Fix For: 1.1.5 > > Attachments: NonRenderedComp.java, nonRenderedComp.jsp, > PersonBean.java > > > Since the component was previously not rendered, its submitted value is null. > The local value that is set in restoreState is not null. This does not get > reset by validation since non-rendered components are not validated > (processValidators). Therefore the associated value-binding expression is not > evaluated in getValue,and hence the local value is returned. > It seems to me that restoreState should set the local value to null. This > would result in the value-binding expression being evaluated and displayed. > Example: > I have a number of input text fields and a select-one-menu (which has an > immedate valueChangeListener) a command button (with an non-immedate action). > The menu switches the rendered mode of some display fields. The button saves > the entered text and clears the input fields. > In addition I have a data-table which displays the saved data and contains a > column with a button, whose on-immediate action puts the selected data item > into the input fields. > I enter data in the input fields and save the data. It is displayed in the > table. Then I use the menu to select a mode in which some of the input text > fields are no longer rendered. I then select the original data from the > table. The fields which remain rendered are displayed and filled correctly. > However the fields which were previously NOT rendered are displayed but are > EMPTY. > This bug does not occur with Sun's reference implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JSF 1.2 status update
Hi Tim, thanks. Regards, Martin Haimberger On 4/24/07, Tim McConnell <[EMAIL PROTECTED]> wrote: Hi Martin, I am looking at MYFACES-1587 below and the corresponding Geronimo JIRA (GERONIMO-3038) Thanks, Tim McConnell Martin Haimberger wrote: > Hi *, > > Nice greatings from Christoph Ebner and me. A lot of issues have been > resolved since our last status update, but there are also some new > issues. > > Here is the updated list of last time: > > MYFACES-1563 - Martin will ovetake this from Christoph. > MYFACES-1255 - resolved > MYFACES-1264 - Christoph will do that. > MYFACES-1253 - resolved > MYFACES-1204 - resolved > MYFACES-1236 - This issues is open. Needs to be done if the JSF 1.2 > implementation is nearly done. Can somebody overtake this please? > MYFACES-1251 - resolved. > MYFACES-1217 - Implemented christoph will recheck this. > MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 > implementation is nearly done. Can somebody overtake this please? > MYFACES-1434 - Just two tags left, convertDateTimeTag patch available, > FacetTag is in progress. > MYFACES-1444 - resolved > MYFACES-1109 - Regarding the comment from Mathias Broekelmann, this is > not compatible with the JSF 1.2 specification. Could be done for > t:dataTable > MYFACES-1548 - resolved > MYFACES-1564 - could not reconstruct the bug. Can somebody take a look > at it to affirm? > MYFACES-1220 - closed > MYFACES-1221 - resolved > MYFACES-1230 - resolved > MYFACES-1582 - patch available (xsd attached) > MYFACES-1584 - resolved > MYFACES-1223 - low priority > > Here are the new, unassigned issues: > > MYFACES-1587 - Can somebody take a look at it? > MYFACES-1594 - Christoph will do that. > > We hope this helps. > > Regards, > Christoph Ebner and Martin Haimberger > > > On 4/20/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: >> Hy, >> >> a short update from my side: >> >> MYFACES-1204 - patch available. >> MYFACES-1434 - was allready done. >> MYFACES-1221 - tests available. >> >> Regards, >> Martin >> >> On 4/18/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: >> > Hey Martin, >> > >> > any updates here ? >> > (any patches that are still sitting in jira ?) >> > >> > -M >> > >> > On 4/6/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: >> > > Hi *, >> > > >> > > Nice greatings from Christoph Ebner and me. Now a short overview of >> > > the JSF 1.2 implementation status. We looked over the unassigned >> > > issues: >> > > >> > > MYFACES-1563 - Christoph will do that. >> > > MYFACES-1255 - Crosschecked with RI -> Only javadoc >> > > MYFACES-1264 - Christoph will do that. >> > > MYFACES-1253 - Crosschecked with RI -> Only javadoc and specification >> > > MYFACES-1204 - Martin (me) will check this. >> > > MYFACES-1236 - This issues is open. >> > > MYFACES-1251 - This issues is open. Needs to be done if the JSF 1.2 >> > > implementation is nearly done. >> > > MYFACES-1217 - Implemented christoph will recheck this. >> > > >> > > MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 >> > > implementation is nearly done. >> > > >> > > MYFACES-1434 - Martin (me) will do "Add element >> > > "deferred-value/method" for elements in the taglibs" >> > > MYFACES-1444 - patch available >> > > MYFACES-1109 - Regarding the comment from Mathias Broekelmann, >> this is >> > > not compatible with the JSF 1.2 specification. Could be done for >> > > t:dataTable >> > > MYFACES-1548 - patch available >> > > MYFACES-1564 - Christoph Ebner will do that. >> > > MYFACES-1220 - This issue is open. >> > > MYFACES-1221 - Martin (me) will test this with an own renderkit. >> > > MYFACES-1230 - Specification Request, someone should recheck this. >> > > MYFACES-1582 - patch available >> > > MYFACES-1584 - patch available >> > > MYFACES-1223 - low priority >> > > >> > > I hope this helps. >> > > >> > > Regards, >> > > Christoph Ebner and Martin Haimberger >> > > >> > >> > >> > -- >> > Matthias Wessendorf >> > http://tinyurl.com/fmywh >> > >> > further stuff: >> > blog: http://jroller.com/page/mwessendorf >> > mail: mwessendorf-at-gmail-dot-com >> > >> >
Re: JSF 1.2 status update
Hi *, Nice greatings from Christoph Ebner and me. A lot of issues have been resolved since our last status update, but there are also some new issues. Here is the updated list of last time: MYFACES-1563 - Martin will ovetake this from Christoph. MYFACES-1255 - resolved MYFACES-1264 - Christoph will do that. MYFACES-1253 - resolved MYFACES-1204 - resolved MYFACES-1236 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. Can somebody overtake this please? MYFACES-1251 - resolved. MYFACES-1217 - Implemented christoph will recheck this. MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. Can somebody overtake this please? MYFACES-1434 - Just two tags left, convertDateTimeTag patch available, FacetTag is in progress. MYFACES-1444 - resolved MYFACES-1109 - Regarding the comment from Mathias Broekelmann, this is not compatible with the JSF 1.2 specification. Could be done for t:dataTable MYFACES-1548 - resolved MYFACES-1564 - could not reconstruct the bug. Can somebody take a look at it to affirm? MYFACES-1220 - closed MYFACES-1221 - resolved MYFACES-1230 - resolved MYFACES-1582 - patch available (xsd attached) MYFACES-1584 - resolved MYFACES-1223 - low priority Here are the new, unassigned issues: MYFACES-1587 - Can somebody take a look at it? MYFACES-1594 - Christoph will do that. We hope this helps. Regards, Christoph Ebner and Martin Haimberger On 4/20/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: Hy, a short update from my side: MYFACES-1204 - patch available. MYFACES-1434 - was allready done. MYFACES-1221 - tests available. Regards, Martin On 4/18/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > Hey Martin, > > any updates here ? > (any patches that are still sitting in jira ?) > > -M > > On 4/6/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: > > Hi *, > > > > Nice greatings from Christoph Ebner and me. Now a short overview of > > the JSF 1.2 implementation status. We looked over the unassigned > > issues: > > > > MYFACES-1563 - Christoph will do that. > > MYFACES-1255 - Crosschecked with RI -> Only javadoc > > MYFACES-1264 - Christoph will do that. > > MYFACES-1253 - Crosschecked with RI -> Only javadoc and specification > > MYFACES-1204 - Martin (me) will check this. > > MYFACES-1236 - This issues is open. > > MYFACES-1251 - This issues is open. Needs to be done if the JSF 1.2 > > implementation is nearly done. > > MYFACES-1217 - Implemented christoph will recheck this. > > > > MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 > > implementation is nearly done. > > > > MYFACES-1434 - Martin (me) will do "Add element > > "deferred-value/method" for elements in the taglibs" > > MYFACES-1444 - patch available > > MYFACES-1109 - Regarding the comment from Mathias Broekelmann, this is > > not compatible with the JSF 1.2 specification. Could be done for > > t:dataTable > > MYFACES-1548 - patch available > > MYFACES-1564 - Christoph Ebner will do that. > > MYFACES-1220 - This issue is open. > > MYFACES-1221 - Martin (me) will test this with an own renderkit. > > MYFACES-1230 - Specification Request, someone should recheck this. > > MYFACES-1582 - patch available > > MYFACES-1584 - patch available > > MYFACES-1223 - low priority > > > > I hope this helps. > > > > Regards, > > Christoph Ebner and Martin Haimberger > > > > > -- > Matthias Wessendorf > http://tinyurl.com/fmywh > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
[jira] Commented: (MYFACES-1253) JSR-252 Issue #147: Clarified grammer with respect to component id.
[ https://issues.apache.org/jira/browse/MYFACES-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491302 ] Martin Haimberger commented on MYFACES-1253: Hi, the problem described in the bug 147 is not a bug in MyFaces 1.2. if a hyphen (-) is used in the id like : JSR-252 Issue #147: Clarified grammer with respect to component id. > --- > > Key: MYFACES-1253 > URL: https://issues.apache.org/jira/browse/MYFACES-1253 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > > Clarified grammer with respect to component id. > See > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=147 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1251) JSR-252 Issue #134: Backward compatability issues
[ https://issues.apache.org/jira/browse/MYFACES-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491230 ] Martin Haimberger commented on MYFACES-1251: Hi, have looked through the changes of this issue and as i can see, everything this issues covers is implemnted in MyFaces 1.2. Clonewriter is used and the methodes have moved as the jsf 1.2 spec says. Regards, Martin Haimberger > JSR-252 Issue #134: Backward compatability issues > - > > Key: MYFACES-1251 > URL: https://issues.apache.org/jira/browse/MYFACES-1251 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > > See > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=134 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1220) JSR-252 Issue # 48: Specify the algorithm used for client id generation as well as provide a way to allow the page author to specify exactly what the client id should
[ https://issues.apache.org/jira/browse/MYFACES-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491223 ] Martin Haimberger commented on MYFACES-1220: Hi, I have looked over this issue and it seems to me that this is implemented already. Regards, Martin Haimberger > JSR-252 Issue # 48: Specify the algorithm used for client id generation as > well as provide a way to allow the page author to specify exactly what the > client id should be, and preventing Faces from altering it. > - > > Key: MYFACES-1220 > URL: https://issues.apache.org/jira/browse/MYFACES-1220 > Project: MyFaces Core > Issue Type: New Feature > Components: JSR-252 >Reporter: Stan Silvert > > Specify the algorithm used for client id generation as well as provide a way > to allow the page author to specify exactly what the client id should be, and > preventing Faces from altering it. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=48 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: boolean value for selectBooleanCheckbox
Hi Paul, i have not seen this email from you and so i have written another solution for the bug, but i also don't know if this was the right way. Maybe someone can check if this solution is right. Regards, Martin Haimberger On 4/23/07, Paul McMahan <[EMAIL PROTECTED]> wrote: In order to address https://issues.apache.org/jira/browse/ MYFACES-1592 my current thinking is that the "value" attribute for the selectBooleanCheckbox tag needs to use: boolean instead of: Does that sound like the right approach? If so then I'm having some trouble figuring out how to make the maven faces plugin generate the tag this way since the "value" attribute is already present via inheritance. Any pointers on how to accomplish this? Best wishes, Paul
[jira] Updated: (MYFACES-1221) JSR-252 Issue #50: Allow an application to specify multiple render kits by introducing an optional "renderKitId" attribute on "".
[ https://issues.apache.org/jira/browse/MYFACES-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1221: --- Status: Patch Available (was: Open) > JSR-252 Issue #50: Allow an application to specify multiple render kits by > introducing an optional "renderKitId" attribute on "". > - > > Key: MYFACES-1221 > URL: https://issues.apache.org/jira/browse/MYFACES-1221 > Project: MyFaces Core > Issue Type: New Feature > Components: JSR-252 >Reporter: Stan Silvert > Assigned To: Martin Haimberger > Attachments: renderkitTest.tar.gz > > > Allow an application to specify multiple render kits by introducing an > optional "renderKitId" attribute on "". It is no longer required to > write a customer ViewHandler to incorporate a different render kit. Please > refer to Section 8.3 "ResponseStateManager" and Section 9.4.20 "" for > more details. > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=50 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JSF 1.2 project status
Hy, a short update from my side: MYFACES-1204 - patch available. MYFACES-1434 - was allready done. MYFACES-1221 - tests available. Regards, Martin On 4/18/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Hey Martin, any updates here ? (any patches that are still sitting in jira ?) -M On 4/6/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: > Hi *, > > Nice greatings from Christoph Ebner and me. Now a short overview of > the JSF 1.2 implementation status. We looked over the unassigned > issues: > > MYFACES-1563 - Christoph will do that. > MYFACES-1255 - Crosschecked with RI -> Only javadoc > MYFACES-1264 - Christoph will do that. > MYFACES-1253 - Crosschecked with RI -> Only javadoc and specification > MYFACES-1204 - Martin (me) will check this. > MYFACES-1236 - This issues is open. > MYFACES-1251 - This issues is open. Needs to be done if the JSF 1.2 > implementation is nearly done. > MYFACES-1217 - Implemented christoph will recheck this. > > MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 > implementation is nearly done. > > MYFACES-1434 - Martin (me) will do "Add element > "deferred-value/method" for elements in the taglibs" > MYFACES-1444 - patch available > MYFACES-1109 - Regarding the comment from Mathias Broekelmann, this is > not compatible with the JSF 1.2 specification. Could be done for > t:dataTable > MYFACES-1548 - patch available > MYFACES-1564 - Christoph Ebner will do that. > MYFACES-1220 - This issue is open. > MYFACES-1221 - Martin (me) will test this with an own renderkit. > MYFACES-1230 - Specification Request, someone should recheck this. > MYFACES-1582 - patch available > MYFACES-1584 - patch available > MYFACES-1223 - low priority > > I hope this helps. > > Regards, > Christoph Ebner and Martin Haimberger > -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
[jira] Updated: (MYFACES-1586) Wrong Name of Partial State Saving Parameter
[ https://issues.apache.org/jira/browse/MYFACES-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1586: --- Status: Patch Available (was: Open) > Wrong Name of Partial State Saving Parameter > > > Key: MYFACES-1586 > URL: https://issues.apache.org/jira/browse/MYFACES-1586 > Project: MyFaces Core > Issue Type: Improvement > Reporter: Martin Haimberger > Assigned To: Martin Haimberger >Priority: Minor > > The name of the partial state saving parameter should not start with > javax.faces, because its an myfaces specific parameter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1586) Wrong Name of Partial State Saving Parameter
Wrong Name of Partial State Saving Parameter Key: MYFACES-1586 URL: https://issues.apache.org/jira/browse/MYFACES-1586 Project: MyFaces Core Issue Type: Improvement Reporter: Martin Haimberger Assigned To: Martin Haimberger Priority: Minor The name of the partial state saving parameter should not start with javax.faces, because its an myfaces specific parameter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1204) JSR-252 Issue #8: Made UIViewRoot a source of PhaseEvent(s) for all phases of the request processing lifecycle except RestoreView.
[ https://issues.apache.org/jira/browse/MYFACES-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1204: --- Status: Patch Available (was: Open) > JSR-252 Issue #8: Made UIViewRoot a source of PhaseEvent(s) for all phases of > the request processing lifecycle except RestoreView. > -- > > Key: MYFACES-1204 > URL: https://issues.apache.org/jira/browse/MYFACES-1204 > Project: MyFaces Core > Issue Type: New Feature > Components: JSR-252 >Reporter: Stan Silvert > Assigned To: Martin Haimberger > Attachments: phaselistenerpatch.tar.gz > > > Made UIViewRoot a source of PhaseEvent(s) for all phases of the request > processing lifecycle except RestoreView. Provided additional "before" and > "after" phase listener attributes for the tag. Please see Section > 4.1.17 "UIViewRoot" for more details. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=8 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1436) Add element "deferred-value/method" for elements in the taglibs
[ https://issues.apache.org/jira/browse/MYFACES-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487224 ] Martin Haimberger commented on MYFACES-1436: Hi, as i can see, this work is already done. The h.tld and the myfaces_core.tld ( in the Meta-INF folder) already has the element deferred-value/method for each attribute. Regards, Martin Haimberger > Add element "deferred-value/method" for elements in the taglibs > --- > > Key: MYFACES-1436 > URL: https://issues.apache.org/jira/browse/MYFACES-1436 > Project: MyFaces Core > Issue Type: Sub-task > Components: JSR-252 >Reporter: Bruno Aranda > Assigned To: Martin Haimberger > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
JSF 1.2 project status
Hi *, Nice greatings from Christoph Ebner and me. Now a short overview of the JSF 1.2 implementation status. We looked over the unassigned issues: MYFACES-1563 - Christoph will do that. MYFACES-1255 - Crosschecked with RI -> Only javadoc MYFACES-1264 - Christoph will do that. MYFACES-1253 - Crosschecked with RI -> Only javadoc and specification MYFACES-1204 - Martin (me) will check this. MYFACES-1236 - This issues is open. MYFACES-1251 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. MYFACES-1217 - Implemented christoph will recheck this. MYFACES-1200 - This issues is open. Needs to be done if the JSF 1.2 implementation is nearly done. MYFACES-1434 - Martin (me) will do "Add element "deferred-value/method" for elements in the taglibs" MYFACES-1444 - patch available MYFACES-1109 - Regarding the comment from Mathias Broekelmann, this is not compatible with the JSF 1.2 specification. Could be done for t:dataTable MYFACES-1548 - patch available MYFACES-1564 - Christoph Ebner will do that. MYFACES-1220 - This issue is open. MYFACES-1221 - Martin (me) will test this with an own renderkit. MYFACES-1230 - Specification Request, someone should recheck this. MYFACES-1582 - patch available MYFACES-1584 - patch available MYFACES-1223 - low priority I hope this helps. Regards, Christoph Ebner and Martin Haimberger
[jira] Commented: (MYFACES-1466) Create JSR-252 implementation of ValidatorELTag called ValidatorTag
[ https://issues.apache.org/jira/browse/MYFACES-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483492 ] Martin Haimberger commented on MYFACES-1466: Hy, it seams this issue is implemented already. Can anybody please recheck? Regards, Martin Haimberger > Create JSR-252 implementation of ValidatorELTag called ValidatorTag > --- > > Key: MYFACES-1466 > URL: https://issues.apache.org/jira/browse/MYFACES-1466 > Project: MyFaces Core > Issue Type: New Feature > Components: JSR-252 >Reporter: Bruno Aranda > > It should contain the common code for all Validate(...)Tags -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1485) Implement JSR-252 core tag: FacetTag
[ https://issues.apache.org/jira/browse/MYFACES-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483483 ] Martin Haimberger commented on MYFACES-1485: Hy, the facettag seams to be implemented already for jsf 1.2. Regards, Martin Haimberger > Implement JSR-252 core tag: FacetTag > > > Key: MYFACES-1485 > URL: https://issues.apache.org/jira/browse/MYFACES-1485 > Project: MyFaces Core > Issue Type: Sub-task >Reporter: Andreas Berger > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1458) Implement JSR-252 core tag: SubviewTag
[ https://issues.apache.org/jira/browse/MYFACES-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1458: --- Status: Patch Available (was: Open) > Implement JSR-252 core tag: SubviewTag > -- > > Key: MYFACES-1458 > URL: https://issues.apache.org/jira/browse/MYFACES-1458 > Project: MyFaces Core > Issue Type: Sub-task > Components: JSR-252 >Reporter: Bruno Aranda > Assigned To: Martin Haimberger > Attachments: subviewTag.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1571) StringIndexOutOfBoundsException when request forwarded to plain JSP
[ https://issues.apache.org/jira/browse/MYFACES-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1571: --- Status: Patch Available (was: Open) > StringIndexOutOfBoundsException when request forwarded to plain JSP > --- > > Key: MYFACES-1571 > URL: https://issues.apache.org/jira/browse/MYFACES-1571 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT > Environment: nightly build, tomcat 6 >Reporter: Dennis Byrne > Attachments: statemarker.patch > > > I don't have time to look at this right now but here's the stack trace if > anyone else wants to take a swing at it. > javax.servlet.ServletException: String index out of range: -1 > javax.faces.webapp.FacesServlet.service(FacesServlet.java:152) > root cause > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > java.lang.AbstractStringBuilder.replace(AbstractStringBuilder.java:800) > java.lang.StringBuffer.replace(StringBuffer.java:392) > > org.apache.myfaces.application.jsp.JspViewHandlerImpl$StateMarkerAwareWriter.flushToWriter(JspViewHandlerImpl.java:398) > > org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:328) > > org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) > > org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1230) JSR-252 Issue #68: Specify that the component tree may be manipulated throughout the request processing lifecycle, except during render.
[ https://issues.apache.org/jira/browse/MYFACES-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482143 ] Martin Haimberger commented on MYFACES-1230: Hy, is this really an issue or only a clearification request to the jsf spec? Regards, Martin Haimberger > JSR-252 Issue #68: Specify that the component tree may be manipulated > throughout the request processing lifecycle, except during render. > > > Key: MYFACES-1230 > URL: https://issues.apache.org/jira/browse/MYFACES-1230 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > > Specify that the component tree may be manipulated throughout the request > processing lifecycle, except during render. Please see Section 2.2.6 "Render > Response" for more details. > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=68 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1224) JSR-252 Issue #55: For postback requests, in the "RestoreViewPhase", during ValueExpression examination for each component, specify that calling setValue() on each Val
[ https://issues.apache.org/jira/browse/MYFACES-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482139 ] Martin Haimberger commented on MYFACES-1224: Hy, this improvement is already implemented, because the JSF RI took the myfaces approach to call the setValue() methode parent first and then traversing the children. Regards, Martin Haimberger > JSR-252 Issue #55: For postback requests, in the "RestoreViewPhase", during > ValueExpression examination for each component, specify that calling > setValue() on each ValueExpression should be done "parent-first" > - > > Key: MYFACES-1224 > URL: https://issues.apache.org/jira/browse/MYFACES-1224 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > > For postback requests, in the "RestoreViewPhase", during ValueExpression > examination for each component in the component tree, specify that calling > the setValue() method on each ValueExpression, should be done in a > "parent-first" fashion, calling the setValue() method and then traversing the > children. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=55 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1202) JSR-252 Issue #5: Clarified the use of a string literal for the "action" attribute on ActionSource components.
[ https://issues.apache.org/jira/browse/MYFACES-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482121 ] Martin Haimberger commented on MYFACES-1202: Hy, this was a bug in the JSF RI 1.1 and worked in myfaces 1.1 and 1.2. In the UIComponent.setValueExpression the expression is checked if it is literal and if it is, the literal navigation outcome will be added. So i think this issue was never a new feature in myfaces, or i have missunderstood samething. Regards, Martin Haimberger > JSR-252 Issue #5: Clarified the use of a string literal for the "action" > attribute on ActionSource components. > -- > > Key: MYFACES-1202 > URL: https://issues.apache.org/jira/browse/MYFACES-1202 > Project: MyFaces Core > Issue Type: New Feature > Components: JSR-252 >Reporter: Stan Silvert > > Clarified the use of a string literal for the "action" attribute on > ActionSource components. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: JSF 1.2 Issues
Hy, provided patch for German locale. On 3/19/07, Cagatay Civici <[EMAIL PROTECTED]> wrote: Hi, MYFACES-1235 is done for English locale. Cagatay On 3/19/07, Matthias Wessendorf <[EMAIL PROTECTED] > wrote: > Martin, > > please do a comment on each of them > > https://issues.apache.org/jira/browse/MYFACES-1269 > That isn't complete, I added it only to abstract UIComponent, not UIData yet > > thx, > M > On 3/19/07, Martin Haimberger < [EMAIL PROTECTED]> wrote: > > Hy, > > > > most of the open JSF 1.2 Issues seams to be implemented already. I have taken > > a look to the following Issues: > > > > MYFACES-1221 > > MYFACES-1269 > > MYFACES-1226 > > MYFACES-1235 > > MYFACES-1381 > > > > Should i comment them that this issues seams to be implemented and > > some takes also a closer look to these, or should i set them to the > > resolved status? > > > > regards, > > Martin Haimberger > > > > > -- > Matthias Wessendorf > http://tinyurl.com/fmywh > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
[jira] Commented: (MYFACES-1226) JSR-252 Issue #59: Avoid EL expression evaluation for "value" attribute on "AttributeTag". "AttributeTag" now passes the expression to UIComponent for evaluation.
[ https://issues.apache.org/jira/browse/MYFACES-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482113 ] Martin Haimberger commented on MYFACES-1226: it seams that this is implemented yet. See org.apache.myfaces.taglib.core.AttributeTag. Can anyone take also a closer look to this issue? regards, Martin Haimberger > JSR-252 Issue #59: Avoid EL expression evaluation for "value" attribute on > "AttributeTag". "AttributeTag" now passes the expression to UIComponent for > evaluation. > --- > > Key: MYFACES-1226 > URL: https://issues.apache.org/jira/browse/MYFACES-1226 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > > Avoid EL expression evaluation for "value" attribute on "AttributeTag". > "AttributeTag" now passes the expression to UIComponent for evaluation. > See https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=59 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1381) JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: render not no-op
[ https://issues.apache.org/jira/browse/MYFACES-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482105 ] Martin Haimberger commented on MYFACES-1381: Regarding to the jsf 1.2 spezification section 3.1.12 there should nothing be done if not rendertype is set. The resolution of the corresponding jsf ri issue was set to later (jsf 2.0). I think this is no bug. > JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: > render not no-op > -- > > Key: MYFACES-1381 > URL: https://issues.apache.org/jira/browse/MYFACES-1381 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT >Reporter: Mike Kienenberger > Assigned To: Martin Haimberger > > JSR-252 Issue #303: Clarified the use of encodeChildren with no renderer: > render not no-op > https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=303 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1235) JSR-252 Issue #78: Added a more "user-friendly" default error message for UIInput "update model".
[ https://issues.apache.org/jira/browse/MYFACES-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1235: --- Status: Open (was: Patch Available) > JSR-252 Issue #78: Added a more "user-friendly" default error message for > UIInput "update model". > - > > Key: MYFACES-1235 > URL: https://issues.apache.org/jira/browse/MYFACES-1235 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > Assigned To: Martin Haimberger > > Added a more "user-friendly" default error message for UIInput "update > model". Please see Section 2.5.2.4 "Localized Application Messages" for more > details. > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=78 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1235) JSR-252 Issue #78: Added a more "user-friendly" default error message for UIInput "update model".
[ https://issues.apache.org/jira/browse/MYFACES-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1235: --- Status: Patch Available (was: Open) > JSR-252 Issue #78: Added a more "user-friendly" default error message for > UIInput "update model". > - > > Key: MYFACES-1235 > URL: https://issues.apache.org/jira/browse/MYFACES-1235 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > Assigned To: Martin Haimberger > > Added a more "user-friendly" default error message for UIInput "update > model". Please see Section 2.5.2.4 "Localized Application Messages" for more > details. > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=78 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1221) JSR-252 Issue #50: Allow an application to specify multiple render kits by introducing an optional "renderKitId" attribute on "".
[ https://issues.apache.org/jira/browse/MYFACES-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482073 ] Martin Haimberger commented on MYFACES-1221: it seams that this is implemented yet. Can anyone take also a closer look to this issue? regards, Martin Haimberger > JSR-252 Issue #50: Allow an application to specify multiple render kits by > introducing an optional "renderKitId" attribute on "". > - > > Key: MYFACES-1221 > URL: https://issues.apache.org/jira/browse/MYFACES-1221 > Project: MyFaces Core > Issue Type: New Feature > Components: JSR-252 >Reporter: Stan Silvert > > Allow an application to specify multiple render kits by introducing an > optional "renderKitId" attribute on "". It is no longer required to > write a customer ViewHandler to incorporate a different render kit. Please > refer to Section 8.3 "ResponseStateManager" and Section 9.4.20 "" for > more details. > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=50 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1235) JSR-252 Issue #78: Added a more "user-friendly" default error message for UIInput "update model".
[ https://issues.apache.org/jira/browse/MYFACES-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482072 ] Martin Haimberger commented on MYFACES-1235: done for English locale > JSR-252 Issue #78: Added a more "user-friendly" default error message for > UIInput "update model". > - > > Key: MYFACES-1235 > URL: https://issues.apache.org/jira/browse/MYFACES-1235 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-252 >Reporter: Stan Silvert > Assigned To: Martin Haimberger > > Added a more "user-friendly" default error message for UIInput "update > model". Please see Section 2.5.2.4 "Localized Application Messages" for more > details. > Also see > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=78 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
JSF 1.2 Issues
Hy, most of the open JSF 1.2 Issues seams to be implemented already. I have taken a look to the following Issues: MYFACES-1221 MYFACES-1269 MYFACES-1226 MYFACES-1235 MYFACES-1381 Should i comment them that this issues seams to be implemented and some takes also a closer look to these, or should i set them to the resolved status? regards, Martin Haimberger
[jira] Updated: (MYFACES-1565) Added a more "user-friendly" default error message for UIInput "update model".
[ https://issues.apache.org/jira/browse/MYFACES-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1565: --- Status: Patch Available (was: Open) > Added a more "user-friendly" default error message for UIInput "update > model". > --- > > Key: MYFACES-1565 > URL: https://issues.apache.org/jira/browse/MYFACES-1565 > Project: MyFaces Core > Issue Type: Improvement > Components: JSR-127 >Reporter: Martin Haimberger >Priority: Minor > Attachments: myfaces11_updatedmessage.patch > > > Added a more "user-friendly" default error message for UIInput "update > model". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1565) Added a more "user-friendly" default error message for UIInput "update model".
Added a more "user-friendly" default error message for UIInput "update model".
---
Key: MYFACES-1565
URL: https://issues.apache.org/jira/browse/MYFACES-1565
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-127
Reporter: Martin Haimberger
Priority: Minor
Added a more "user-friendly" default error message for UIInput "update model".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1548) UIComponent State change if getValueBinding() is called.
[ https://issues.apache.org/jira/browse/MYFACES-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1548: --- Status: Open (was: Patch Available) > UIComponent State change if getValueBinding() is called. > > > Key: MYFACES-1548 > URL: https://issues.apache.org/jira/browse/MYFACES-1548 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT > Reporter: Martin Haimberger > Fix For: 1.2.0-SNAPSHOT > > Attachments: UIComponentBase.patch > > > The Component State change if getValueBinding() is called and no > _valueExpressionMap is present. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1548) UIComponent State change if getValueBinding() is called.
[ https://issues.apache.org/jira/browse/MYFACES-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1548: --- Status: Patch Available (was: Open) > UIComponent State change if getValueBinding() is called. > > > Key: MYFACES-1548 > URL: https://issues.apache.org/jira/browse/MYFACES-1548 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT > Reporter: Martin Haimberger > Fix For: 1.2.0-SNAPSHOT > > Attachments: UIComponentBase.patch > > > The Component State change if getValueBinding() is called and no > _valueExpressionMap is present. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1548) UIComponent State change if getValueBinding() is called.
[ https://issues.apache.org/jira/browse/MYFACES-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1548: --- Status: Patch Available (was: Open) > UIComponent State change if getValueBinding() is called. > > > Key: MYFACES-1548 > URL: https://issues.apache.org/jira/browse/MYFACES-1548 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT > Reporter: Martin Haimberger > Fix For: 1.2.0-SNAPSHOT > > > The Component State change if getValueBinding() is called and no > _valueExpressionMap is present. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1548) UIComponent State change if getValueBinding() is called.
UIComponent State change if getValueBinding() is called. Key: MYFACES-1548 URL: https://issues.apache.org/jira/browse/MYFACES-1548 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Reporter: Martin Haimberger Fix For: 1.2.0-SNAPSHOT The Component State change if getValueBinding() is called and no _valueExpressionMap is present. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1544) Verbatim Components are not created during JSP dispatch
[ https://issues.apache.org/jira/browse/MYFACES-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1544: --- Status: Patch Available (was: Open) > Verbatim Components are not created during JSP dispatch > --- > > Key: MYFACES-1544 > URL: https://issues.apache.org/jira/browse/MYFACES-1544 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-252 >Affects Versions: 1.2.0-SNAPSHOT > Reporter: Martin Haimberger > Fix For: 1.2.0-SNAPSHOT > > > Hy, > Verbatim Components for text in the JSP Page are not created during JSP > dispatch > Regards > Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1544) Verbatim Components are not created during JSP dispatch
Verbatim Components are not created during JSP dispatch --- Key: MYFACES-1544 URL: https://issues.apache.org/jira/browse/MYFACES-1544 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 1.2.0-SNAPSHOT Reporter: Martin Haimberger Fix For: 1.2.0-SNAPSHOT Hy, Verbatim Components for text in the JSP Page are not created during JSP dispatch Regards Martin Haimberger -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Running MyFaces 1.2
Yes, that was the problem. Thanks! Greatings Martin Haimberger On 2/26/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: is your app folder containing javx.el ? -M On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: > Hy again, > > i have run the demoapplication with jetty and now i see an exception. > I dont know why Tomcat 6.0.9 has not shown this exeption. > > Maybe it helps: > > DEBUG [main] (DefaultFacesInitializer.java:83) - jspfactory = > [EMAIL PROTECTED] > 2007-02-26 16:11:58.556::WARN: failed > [EMAIL PROTECTED]/test-webapp,jar:file:/Developer/jetty-6.1.2rc0/webapps/test-webapp.war!/} > java.lang.LinkageError: Class javax/el/ExpressionFactory violates > loader constraints > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:365) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:336) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:365) > at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:336) > at javax.el.FactoryFinder.newInstance(FactoryFinder.java:52) > at javax.el.FactoryFinder.find(FactoryFinder.java:162) > at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:154) > at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:125) > at org.apache.jasper.runtime.JspApplicationContextImpl.getExpressionFactory(JspApplicationContextImpl.java:65) > at org.apache.myfaces.webapp.DefaultFacesInitializer.initFaces(DefaultFacesInitializer.java:88) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:57) > at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:512) > at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) > at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1201) > at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:482) > at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:444) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) > at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:147) > at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:141) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) > at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:147) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) > at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117) > at org.mortbay.jetty.Server.doStart(Server.java:210) > at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) > at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:929) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.mortbay.start.Main.invokeMain(Main.java:183) > at org.mortbay.start.Main.start(Main.java:497) > at org.mortbay.start.Main.main(Main.java:115) > > Do i have
Re: Running MyFaces 1.2
Hy again,
i have run the demoapplication with jetty and now i see an exception.
I dont know why Tomcat 6.0.9 has not shown this exeption.
Maybe it helps:
DEBUG [main] (DefaultFacesInitializer.java:83) - jspfactory =
[EMAIL PROTECTED]
2007-02-26 16:11:58.556::WARN: failed
[EMAIL
PROTECTED]/test-webapp,jar:file:/Developer/jetty-6.1.2rc0/webapps/test-webapp.war!/}
java.lang.LinkageError: Class javax/el/ExpressionFactory violates
loader constraints
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:365)
at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:336)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:365)
at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:336)
at javax.el.FactoryFinder.newInstance(FactoryFinder.java:52)
at javax.el.FactoryFinder.find(FactoryFinder.java:162)
at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:154)
at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:125)
at
org.apache.jasper.runtime.JspApplicationContextImpl.getExpressionFactory(JspApplicationContextImpl.java:65)
at
org.apache.myfaces.webapp.DefaultFacesInitializer.initFaces(DefaultFacesInitializer.java:88)
at
org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:57)
at
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:512)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:135)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1201)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:482)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:444)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:147)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:141)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:147)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:210)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:929)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.mortbay.start.Main.invokeMain(Main.java:183)
at org.mortbay.start.Main.start(Main.java:497)
at org.mortbay.start.Main.main(Main.java:115)
Do i have a wrong javax el package ?
Regards and thanks for your help.
Martin Haimberger
On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote:
Hy,
i have found the place in the code where the problem resists:
In the Method:
private void configureResolverForJSP(JspApplicationContext appCtx,
RuntimeConfig runtimeConfig)
{
FacesCompositeELResolver facesCompositeELResolver = new
FacesCompositeELResolver(Scope.JSP);
This is the last line which gets executed. But no exception is thrown:
--->>>>appCtx.addELResolver(facesCompositeELResolver);
Re: Running MyFaces 1.2
Hy,
i have found the place in the code where the problem resists:
In the Method:
private void configureResolverForJSP(JspApplicationContext appCtx,
RuntimeConfig runtimeConfig)
{
FacesCompositeELResolver facesCompositeELResolver = new
FacesCompositeELResolver(Scope.JSP);
This is the last line which gets executed. But no exception is thrown:
--->>>>appCtx.addELResolver(facesCompositeELResolver);
PhaseListener resolverForJSPInitializer = new ResolverForJSPInitializer(
createResolverBuilderForJSP(runtimeConfig),
facesCompositeELResolver);
LifecycleFactory factory = (LifecycleFactory)
FactoryFinder.getFactory(FactoryFinder.LIFECYCLE_FACTORY);
for (Iterator iter = factory.getLifecycleIds(); iter.hasNext();)
{
factory.getLifecycle(iter.next()).addPhaseListener(resolverForJSPInitializer);
}
}
Any Idea or is the current code from the svn repos not working ?
Regards,
Martin
On 2/26/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
You can run jetty as a m2 plugin. very neat !
-M
On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote:
> Sorry for spamming, but is there another Application Server which will
> work with MyFaces 1.2 and Intellij Idea ?
>
> Regards,
> Martin Haimberger
>
> On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote:
> > No nothing more. No Exception, nothing. I will try Jetty6.1.x, i hope
> > the myfaces1.2 will start.
> >
> > Regards,
> > Martin Haimberger
> >
> > On 2/26/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > > does the tomcat log say more?
> > >
> > > I am able to deploy a jsf 1.2 app with Jetty6.1.x
> > >
> > > -M
> > >
> > > On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote:
> > > > Hy *,
> > > >
> > > > i am going to help to develop myfaces 1.2. I have checked it out,
> > > > compiled it (with some difficulties, because some jars were not
> > > > found). I installed tomcat 6.0.9 alpha and i got this error:
> > > >
> > > > DEBUG [main] (HtmlRenderKitImpl.java:112) - add Renderer family =
> > > > javax.faces.SelectOne rendererType = javax.faces.Radio renderer class
> > > > = org.apache.myfaces.renderkit.html.HtmlRadioRenderer
> > > > INFO [main] (FacesConfigurator.java:972) - Serialization provider :
> > > > class org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory
> > > > Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start
> > > > SEVERE: Error listenerStart
> > > > Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start
> > > >
> > > > I am running Intellij 6.0.4 and tomcat 6.0.9 on MacOsX.
> > > >
> > > > Has someone any idea what i did wrong?
> > > >
> > > > Regards,
> > > > Martin Haimberger
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > http://tinyurl.com/fmywh
> > >
> > > further stuff:
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: Running MyFaces 1.2
Sorry for spamming, but is there another Application Server which will work with MyFaces 1.2 and Intellij Idea ? Regards, Martin Haimberger On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: No nothing more. No Exception, nothing. I will try Jetty6.1.x, i hope the myfaces1.2 will start. Regards, Martin Haimberger On 2/26/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > does the tomcat log say more? > > I am able to deploy a jsf 1.2 app with Jetty6.1.x > > -M > > On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: > > Hy *, > > > > i am going to help to develop myfaces 1.2. I have checked it out, > > compiled it (with some difficulties, because some jars were not > > found). I installed tomcat 6.0.9 alpha and i got this error: > > > > DEBUG [main] (HtmlRenderKitImpl.java:112) - add Renderer family = > > javax.faces.SelectOne rendererType = javax.faces.Radio renderer class > > = org.apache.myfaces.renderkit.html.HtmlRadioRenderer > > INFO [main] (FacesConfigurator.java:972) - Serialization provider : > > class org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory > > Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start > > SEVERE: Error listenerStart > > Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start > > > > I am running Intellij 6.0.4 and tomcat 6.0.9 on MacOsX. > > > > Has someone any idea what i did wrong? > > > > Regards, > > Martin Haimberger > > > > > -- > Matthias Wessendorf > http://tinyurl.com/fmywh > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
Re: Running MyFaces 1.2
No nothing more. No Exception, nothing. I will try Jetty6.1.x, i hope the myfaces1.2 will start. Regards, Martin Haimberger On 2/26/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: does the tomcat log say more? I am able to deploy a jsf 1.2 app with Jetty6.1.x -M On 2/26/07, Martin Haimberger <[EMAIL PROTECTED]> wrote: > Hy *, > > i am going to help to develop myfaces 1.2. I have checked it out, > compiled it (with some difficulties, because some jars were not > found). I installed tomcat 6.0.9 alpha and i got this error: > > DEBUG [main] (HtmlRenderKitImpl.java:112) - add Renderer family = > javax.faces.SelectOne rendererType = javax.faces.Radio renderer class > = org.apache.myfaces.renderkit.html.HtmlRadioRenderer > INFO [main] (FacesConfigurator.java:972) - Serialization provider : > class org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory > Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start > SEVERE: Error listenerStart > Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start > > I am running Intellij 6.0.4 and tomcat 6.0.9 on MacOsX. > > Has someone any idea what i did wrong? > > Regards, > Martin Haimberger > -- Matthias Wessendorf http://tinyurl.com/fmywh further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Running MyFaces 1.2
Hy *, i am going to help to develop myfaces 1.2. I have checked it out, compiled it (with some difficulties, because some jars were not found). I installed tomcat 6.0.9 alpha and i got this error: DEBUG [main] (HtmlRenderKitImpl.java:112) - add Renderer family = javax.faces.SelectOne rendererType = javax.faces.Radio renderer class = org.apache.myfaces.renderkit.html.HtmlRadioRenderer INFO [main] (FacesConfigurator.java:972) - Serialization provider : class org.apache.myfaces.shared_impl.util.serial.DefaultSerialFactory Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Feb 26, 2007 2:14:34 PM org.apache.catalina.core.StandardContext start I am running Intellij 6.0.4 and tomcat 6.0.9 on MacOsX. Has someone any idea what i did wrong? Regards, Martin Haimberger
[jira] Updated: (MYFACES-1543) mbean_source.jsp not working
[ https://issues.apache.org/jira/browse/MYFACES-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1543: --- Status: Patch Available (was: Open) > mbean_source.jsp not working > - > > Key: MYFACES-1543 > URL: https://issues.apache.org/jira/browse/MYFACES-1543 > Project: MyFaces Core > Issue Type: Bug > Components: website > Reporter: Martin Haimberger >Priority: Minor > > the mbean_source is not working if for example the myfaces_simple examples > are deployed not as docBase. The path the mbean_source.jsp generates is > related to the docBase directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-1543) mbean_source.jsp not working
mbean_source.jsp not working - Key: MYFACES-1543 URL: https://issues.apache.org/jira/browse/MYFACES-1543 Project: MyFaces Core Issue Type: Bug Components: website Reporter: Martin Haimberger Priority: Minor the mbean_source is not working if for example the myfaces_simple examples are deployed not as docBase. The path the mbean_source.jsp generates is related to the docBase directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r511461 [1/3] - in /myfaces: core/trunk/api/src/main/java/javax/faces/webapp/ core/trunk/impl/src/main/java/org/apache/myfaces/application/ core/trunk/impl/src/main/java/org/apache/myf
Hy, -is this: https://issues.apache.org/jira/browse/MYFACES-1541 ? please add the jira issue number in future commits yes this issue was the commit. I think adding private methods to javax.faces.xxx classes is fine, isnt't it ? What do you mean ? Have i added too much public methods ? Regards Martin Haimberger On 2/25/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: Thanks, Matthias On 2/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: mmarinschek > Date: Sun Feb 25 00:10:54 2007 > New Revision: 511461 > > URL: http://svn.apache.org/viewvc?view=rev&rev=511461 > Log: > partial state saving improvement > > Added: > myfaces/core/trunk/api/src/main/java/javax/faces/webapp/_DummyPageContextOutWriter.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/ > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/BufferedStringWriter.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/EncodeAllComponentUtil.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/FastStringWriter.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/PartialTreeStructureManager.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/PssJspStateManagerImpl.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/PssJspViewHandlerImpl.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/TempServletOutputStream.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/TreeStructComponent.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/UIViewRootWrapper.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/pss/ViewHandlerResponseWrapperHelperImpl.java > Modified: > myfaces/core/trunk/api/src/main/java/javax/faces/webapp/UIComponentTag.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/application/NavigationHandlerImpl.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/context/portlet/PortletExternalContextImpl.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/context/servlet/ServletExternalContextImpl.java > myfaces/core/trunk/impl/src/main/java/org/apache/myfaces/taglib/core/ViewTag.java > myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlResponseWriterImpl.java > myfaces/tomahawk/trunk/examples/simple/src/main/webapp/WEB-INF/web.xml > > Modified: myfaces/core/trunk/api/src/main/java/javax/faces/webapp/UIComponentTag.java > URL: http://svn.apache.org/viewvc/myfaces/core/trunk/api/src/main/java/javax/faces/webapp/UIComponentTag.java?view=diff&rev=511461&r1=511460&r2=511461 > == > --- myfaces/core/trunk/api/src/main/java/javax/faces/webapp/UIComponentTag.java (original) > +++ myfaces/core/trunk/api/src/main/java/javax/faces/webapp/UIComponentTag.java Sun Feb 25 00:10:54 2007 > @@ -26,6 +26,7 @@ > import javax.faces.application.Application; > import javax.faces.component.UIComponent; > import javax.faces.component.UIViewRoot; > +import javax.faces.component.UIOutput; > import javax.faces.context.FacesContext; > import javax.faces.context.ResponseWriter; > import javax.faces.context.ExternalContext; > @@ -35,8 +36,11 @@ > > import javax.servlet.jsp.JspException; > import javax.servlet.jsp.PageContext; > +import javax.servlet.jsp.JspWriter; > import javax.servlet.jsp.tagext.Tag; > +import javax.servlet.jsp.tagext.BodyContent; > import java.io.IOException; > +import java.io.Reader; > import java.util.*; > > /** > @@ -63,6 +67,12 @@ > > private static final String UNIQUE_ID_COUNTER_ATTR = UIComponentTag.class.getName() + ".UNIQUE_ID_COUNTER"; > > +private static final String PARTIAL_STATE_SAVING_METHOD_PARAM_NAME = "javax.faces.PARTIAL_STATE_SAVING_METHOD"; > +private static final String PARTIAL_STATE_SAVING_METHOD_ON = "true"; > +private static final String PARTIAL_STATE_SAVING_METHOD_OFF = "false"; > + > +private static final String BEFORE_VIEW_CONTEXT = "org.apache.myfaces.BEFORE_VIEW_CONTEXT"; > + > protected PageContext pageContext = null; > private Tag _parent = null; > > @@ -78,8 +88,36 @@ > private ResponseWriter _writer = null; > private Set _childrenAdded = null; > private Set _facetsAdded = null; > +private Boolean _partialStateSaving = null; > > private static Log log = LogFactory.
Re: Partial State-Saving
Hy Jacob,
you are right. This is an old artifact and i will remove.
Thanks for looking
Nice Regards
Martin Haimberger
On 2/25/07, Jacob Hookom <[EMAIL PROTECTED]> wrote:
This seams a bit odd:
private TreeStructComponent
internalBuildInitalTreeStructureToSave(UIComponent
component,FacesContext facesContext, Object state, int childIndex)
{
Object myState = null;
Map facetStateMap = null;
List childrenStateList = null;
if (state != null)
{
myState = ((Object[])state)[0];
facetStateMap = (Map)((Object[])state)[1];
childrenStateList = (List)((Object[])state)[2];
}
}
Under what assumptions is the state always going to be broken out that way?
Martin Marinschek wrote:
> Hey *,
>
> I've finally found the time to go through the partial state-saving
> stuff Martin Haimberger did through his Google SoC assignment and we
> have together made sure the kinks are polished out pretty much. The
> rest will:
>
> a) enable much less state saved per each request (by a factor of 3,
> 4), at least with the MyFaces examples, we haven't tried with
> real-world applications that much so far (we'd be happy about
> additional data from you)
> b) allow tree-building just like in 1.2. You basically get most 1.2
> features with 1.1 like this.
>
> The jira issue with the patch is:
>
> https://issues.apache.org/jira/browse/MYFACES-1541
>
> I wanted to wait with the commit until the release is out, and I
> encourage you to do a lot of testing. Martin will be around next week
> to fix anything that comes up.
>
> Martin, please create a WIKI page where you describe how stuff can be
> configured.
>
> regards,
>
> Martin
>
[jira] Created: (MYFACES-1541) Partial State Saving improvement to myfaces
Partial State Saving improvement to myfaces --- Key: MYFACES-1541 URL: https://issues.apache.org/jira/browse/MYFACES-1541 Project: MyFaces Core Issue Type: Improvement Components: General Affects Versions: 1.1.6-SNAPSHOT Reporter: Martin Haimberger Fix For: 1.1.6-SNAPSHOT Partial State Saving of the Component Tree to reduce the needed bandwith if client side state saving is activated or the used memory if server side state saving is used. There are two "modes" in which the partial state saving can be used, the faster one is if the jsp is only rendert once and a "template" of the component tree is generated and saved. The following request uses this "template" to construct the UIViewRoot and merge the partial state save. Before the state will get saved, the current UIViewRoot is compared to the template and only the components which differs are saved. In the secound mode the JSP is processed by every request, which is very usefull if Scripts are embedded inside the page. The secound reason is backword compatiblity because for example the f:loadbundle tag will load the bundle if the TAG is processed. The s:loadBundle component solves this problem, but if someone want to use partial state saving and is not willing to include the sandbox for the s:loadBundle component the secound mode will help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-1541) Partial State Saving improvement to myfaces
[ https://issues.apache.org/jira/browse/MYFACES-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Haimberger updated MYFACES-1541: --- Status: Patch Available (was: Open) > Partial State Saving improvement to myfaces > --- > > Key: MYFACES-1541 > URL: https://issues.apache.org/jira/browse/MYFACES-1541 > Project: MyFaces Core > Issue Type: Improvement > Components: General >Affects Versions: 1.1.6-SNAPSHOT > Reporter: Martin Haimberger > Fix For: 1.1.6-SNAPSHOT > > > Partial State Saving of the Component Tree to reduce the needed bandwith if > client side state saving is activated or the used memory if server side state > saving is used. There are two "modes" in which the partial state saving can > be used, the faster one is if the jsp is only rendert once and a "template" > of the component tree is generated and saved. The following request uses this > "template" to construct the UIViewRoot and merge the partial state save. > Before the state will get saved, the current UIViewRoot is compared to the > template and only the components which differs are saved. In the secound mode > the JSP is processed by every request, which is very usefull if Scripts are > embedded inside the page. The secound reason is backword compatiblity because > for example the f:loadbundle tag will load the bundle if the TAG is > processed. The s:loadBundle component solves this problem, but if someone > want to use partial state saving and is not willing to include the sandbox > for the s:loadBundle component the secound mode will help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Outcome of the Google Sommer of Code project Partial State Saving
Hy, Thanks for your great interrest. Sorry for the delay, but i had a lot of work the last days. The chosen strategie was to save the UIViewRoot as a "template" of the JSP's after executing the first time on the server. Before the UIViewRoot gets serialized for statesaving, we will diff the saved "template" UIViewRoot and the current UIViewRoot and save only the components which have different component states. The other components are marked to be the same like in the template. In the restoreview Phase these marked components were taken from the "template" and a whole UIViewRoot is restored. As a secound aspect the strings for the component classes are hold at the server and only id's are saved, which also saves about 5-10% of the savestate. I hope that helps. regards Martin Haimberger On 9/17/06, Adam Winer <[EMAIL PROTECTED]> wrote: Martin,Hey, very cool! Have you written up anything describing (a)?I'm very curious about the strategy chosen. -- AdamOn 9/13/06, Martin Haimberger <[EMAIL PROTECTED]> wrote:>> Hy everyone,>> my name is Martin Haimberger and i took part in the GSoC 2006 with the > Partial State Saving project for myfaces.> The two mayor things to implement were>a) Create an partial State Saving Tree>b) Render the Tree without calling dispatch() and let the jsp render it >> I used the tomahowk simple examples to do first performancetests. I> activated Clientside statesaving> and compaired their length:>>>>> displayValueOnly >>>> 11.450 org.savestate>> 6.060 partial.save.state>>>>>> Partial Savestate: 52,9%>>>>>> home.jsp >>>> 22.754 org.savestate>>6.316 partial.save.state>>>> Partial Savestate: 27,7%>>>>>>>> masterDetail >>>> 13.870 org.savestate>> 10.300 partial.save.state>>>> Partial Savestate: 74,3%>>>>>>>> selectbox >>>> 15.310 org.savestate>> 10.808 partial.save.state>>>> Partial Savestate with ID Map: 70,6%>>>>>> selectonecountry >>>> 3.494 org.savestate>> 1.896 partial.save.state>>>>>> Partial Savestate: 54,3%>>>>>>> > tree2NiceWrap>>>> 9.902 org.savestate>> 6.464 partial.save.state>>>> Partial Savestate: 65,3%>>>>>> >> dynamiclists>>>> 5.998 org.savestate>> 4.760 partial.save.state>>>> Partial Savestate with ID Map: 79,3%>>>> >> The secound test was a speed test how fast the page gets rendered without> dispatching to the jsp.>> The problem is that the response times of the same request fluctuate a lot> if it is called a certain times. So measuring is very difficult. >> But what i can say is that it is (after the first request) about 20% faster> than alway dispatching to the jsp who it was done till now.>>>> In the next weeks my Mentor, Martin Marinschek and I will adapt the code and > commit it to the svn server.>>>> Regards>> Martin Haimberger>>
Outcome of the Google Sommer of Code project Partial State Saving
Hy everyone, my name is Martin Haimberger and i took part in the GSoC 2006 with the Partial State Saving project for myfaces. The two mayor things to implement were a) Create an partial State Saving Tree b) Render the Tree without calling dispatch() and let the jsp render it I used the tomahowk simple examples to do first performancetests. I activated Clientside statesaving and compaired their length: displayValueOnly 11.450 org.savestate 6.060 partial.save.state Partial Savestate: 52,9% home.jsp 22.754 org.savestate 6.316 partial.save.state Partial Savestate: 27,7% masterDetail 13.870 org.savestate 10.300 partial.save.state Partial Savestate: 74,3% selectbox 15.310 org.savestate 10.808 partial.save.state Partial Savestate with ID Map: 70,6% selectonecountry 3.494 org.savestate 1.896 partial.save.state Partial Savestate: 54,3% tree2NiceWrap 9.902 org.savestate 6.464 partial.save.state Partial Savestate: 65,3% dynamiclists 5.998 org.savestate 4.760 partial.save.state Partial Savestate with ID Map: 79,3% The secound test was a speed test how fast the page gets rendered without dispatching to the jsp. The problem is that the response times of the same request fluctuate a lot if it is called a certain times. So measuring is very difficult. But what i can say is that it is (after the first request) about 20% faster than alway dispatching to the jsp who it was done till now. In the next weeks my Mentor, Martin Marinschek and I will adapt the code and commit it to the svn server. Regards Martin Haimberger
