[jira] [Created] (MYFACES-4426) not refreshed when is changed during invoke application
Bauke Scholtz created MYFACES-4426: -- Summary: not refreshed when is changed during invoke application Key: MYFACES-4426 URL: https://issues.apache.org/jira/browse/MYFACES-4426 Project: MyFaces Core Issue Type: Bug Reporter: Bauke Scholtz [https://stackoverflow.com/q/70609500] * have a * change locale via UIViewRoot#setLocale() during invoke application * expectation: reflects changed locale during render response -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (MYFACES-4120) ResourceHandler#markResourceRendered() should be retained during ajax rebuild
[ https://issues.apache.org/jira/browse/MYFACES-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042808#comment-16042808 ] Bauke Scholtz edited comment on MYFACES-4120 at 6/8/17 2:58 PM: The problem is not in JavaScript side. It does it all correct. The problem is in JSF side, it is not "in sync" with JavaScript side. The isResourceRendered() incorrectly returns false while the resource is "rendered" (loaded) in JavaScript side. And, you got the isRenderAll() backwards. I didn't mean when it returns true but when it returns false. I.e. there's no renderAll. was (Author: balusc): The problem is not in JavaScript side. It does it all correct. The problem is in JSF side, it is not "in sync" with JavaScript side. The isResourceRendered() incorrectly returns false while the resource is rendered in JavaScript side. And, you got the isRenderAll() backwards. I didn't mean when it returns true but when it returns false. I.e. there's no renderAll. > ResourceHandler#markResourceRendered() should be retained during ajax rebuild > - > > Key: MYFACES-4120 > URL: https://issues.apache.org/jira/browse/MYFACES-4120 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0 > Environment: TomEE 7.0.3 with MyFaces 2.3.0-SNAPSHOT >Reporter: Bauke Scholtz >Assignee: Leonardo Uribe > > While running OmniFaces IT suite on today's MyFaces 2.3.0-SNAPSHOT, I noticed > a bug in ResourceHandler#isResourceRendered() during an ajax navigation back > to the same view (more specifically, when FacesContext#setViewRoot() is > invoked with a new UIViewRoot of same viewId during an ajax postback). > During restore view phase, all already-rendered resources are correctly > marked via markResourceRendered(). However, this is in turn stored as a > transient UIViewRoot attribute. As a consequence, when the UIViewRoot gets > changed during the very same ajax request, they are all lost, causing > isResourceRendered() to incorrectly return false. > Basically, the markResourceRendered() of the previous view should be > remembered for the next view when PartialViewContext#isAjaxRequest() returns > true and isRenderAll() returns false. > In MyFaces 2.2 (and possibly earlier) the behavior of markResourceRendered() > and isResourceRendered() was internally correctly implemented via > org.apache.myfaces.RENDERED_SCRIPT_RESOURCES_SET context attribute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MYFACES-4120) ResourceHandler#markResourceRendered() should be retained during ajax rebuild
[ https://issues.apache.org/jira/browse/MYFACES-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042808#comment-16042808 ] Bauke Scholtz commented on MYFACES-4120: The problem is not in JavaScript side. It does it all correct. The problem is in JSF side, it is not "in sync" with JavaScript side. The isResourceRendered() incorrectly returns false while the resource is rendered in JavaScript side. And, you got the isRenderAll() backwards. I didn't mean when it returns true but when it returns false. I.e. there's no renderAll. > ResourceHandler#markResourceRendered() should be retained during ajax rebuild > - > > Key: MYFACES-4120 > URL: https://issues.apache.org/jira/browse/MYFACES-4120 > Project: MyFaces Core > Issue Type: Bug >Affects Versions: 2.3.0 > Environment: TomEE 7.0.3 with MyFaces 2.3.0-SNAPSHOT >Reporter: Bauke Scholtz >Assignee: Leonardo Uribe > > While running OmniFaces IT suite on today's MyFaces 2.3.0-SNAPSHOT, I noticed > a bug in ResourceHandler#isResourceRendered() during an ajax navigation back > to the same view (more specifically, when FacesContext#setViewRoot() is > invoked with a new UIViewRoot of same viewId during an ajax postback). > During restore view phase, all already-rendered resources are correctly > marked via markResourceRendered(). However, this is in turn stored as a > transient UIViewRoot attribute. As a consequence, when the UIViewRoot gets > changed during the very same ajax request, they are all lost, causing > isResourceRendered() to incorrectly return false. > Basically, the markResourceRendered() of the previous view should be > remembered for the next view when PartialViewContext#isAjaxRequest() returns > true and isRenderAll() returns false. > In MyFaces 2.2 (and possibly earlier) the behavior of markResourceRendered() > and isResourceRendered() was internally correctly implemented via > org.apache.myfaces.RENDERED_SCRIPT_RESOURCES_SET context attribute. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYFACES-4120) ResourceHandler#markResourceRendered() should be retained during ajax rebuild
Bauke Scholtz created MYFACES-4120: -- Summary: ResourceHandler#markResourceRendered() should be retained during ajax rebuild Key: MYFACES-4120 URL: https://issues.apache.org/jira/browse/MYFACES-4120 Project: MyFaces Core Issue Type: Bug Affects Versions: 2.3.0 Environment: TomEE 7.0.3 with MyFaces 2.3.0-SNAPSHOT Reporter: Bauke Scholtz While running OmniFaces IT suite on today's MyFaces 2.3.0-SNAPSHOT, I noticed a bug in ResourceHandler#isResourceRendered() during an ajax navigation back to the same view (more specifically, when FacesContext#setViewRoot() is invoked with a new UIViewRoot of same viewId during an ajax postback). During restore view phase, all already-rendered resources are correctly marked via markResourceRendered(). However, this is in turn stored as a transient UIViewRoot attribute. As a consequence, when the UIViewRoot gets changed during the very same ajax request, they are all lost, causing isResourceRendered() to incorrectly return false. Basically, the markResourceRendered() of the previous view should be remembered for the next view when PartialViewContext#isAjaxRequest() returns true and isRenderAll() returns false. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MYFACES-4057) Serializable ViewScopeContextualStorage references non-serializable BeanManager
Bauke Scholtz created MYFACES-4057:
--
Summary: Serializable ViewScopeContextualStorage references
non-serializable BeanManager
Key: MYFACES-4057
URL: https://issues.apache.org/jira/browse/MYFACES-4057
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.2.10
Environment: TomEE 7.0.0 and 7.0.1
Reporter: Bauke Scholtz
Test case:
1. Have this CDI bean with JSF CDI view scope.
{code}@Named @ViewScoped
public class Bean implements Serializable {}{code}
2. Have this minimal page mapped to JSF servlet.
{code}#{bean}{code}
3. Open this page in a server using OpenWebBeans as CDI implementation (TomEE
for example) and have session persistence enabled (already default in TomEE).
4. Restart the server.
5. On shutdown below warning is logged.
{code}
ARNING: Cannot serialize session attribute openWebBeansSessionContext for
session 34F40C623600849F43AD2153F2EB75D8
java.io.NotSerializableException: org.apache.webbeans.container.BeanManagerImpl
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
...{code}
6. After restart below exception is thrown during deserializing session (stack
trace comes from TomEE 7.0.0).
{code}java.lang.NullPointerException
at
org.apache.webbeans.proxy.NormalScopeProxyFactory.createNormalScopeProxy(NormalScopeProxyFactory.java:121)
at
org.apache.webbeans.intercept.NormalScopedBeanInterceptorHandler.readResolve(NormalScopedBeanInterceptorHandler.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
{code}
Root cause appears to be that the serializable
{{org.apache.myfaces.cdi.view.ViewScopeContextualStorage}} class has a
{{BeanManager}} property while the interface is not declared serializable.
Related: https://issues.apache.org/jira/browse/OWB-1123
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MYFACES-4052) Multiple with same name encodes only last one in link URL
[
https://issues.apache.org/jira/browse/MYFACES-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341338#comment-15341338
]
Bauke Scholtz edited comment on MYFACES-4052 at 6/21/16 8:12 AM:
-
Related: https://en.wikipedia.org/wiki/Query_string#Web_forms
{quote}
While there is no definitive standard, most web frameworks allow multiple
values to be associated with a single field (e.g.
field1=value1=value2=value3).
{quote}
For what is worth, Servlet API follows this.
was (Author: balusc):
Related: https://en.wikipedia.org/wiki/Query_string#Web_forms For what is
worth, Servlet API follows this.
> Multiple with same name encodes only last one in link URL
> ---
>
> Key: MYFACES-4052
> URL: https://issues.apache.org/jira/browse/MYFACES-4052
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.2.10
> Environment: TomEE 7.0.0
>Reporter: Bauke Scholtz
>Assignee: Leonardo Uribe
>
> Consider:
> {code}
>
>
>
>
> {code}
> MyFaces 2.2.10 renders only last one in link URL instead of both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MYFACES-4052) Multiple with same name encodes only last one in link URL
[
https://issues.apache.org/jira/browse/MYFACES-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341338#comment-15341338
]
Bauke Scholtz commented on MYFACES-4052:
Related: https://en.wikipedia.org/wiki/Query_string#Web_forms For what is
worth, Servlet API follows this.
> Multiple with same name encodes only last one in link URL
> ---
>
> Key: MYFACES-4052
> URL: https://issues.apache.org/jira/browse/MYFACES-4052
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.2.10
> Environment: TomEE 7.0.0
>Reporter: Bauke Scholtz
>Assignee: Leonardo Uribe
>
> Consider:
> {code}
>
>
>
>
> {code}
> MyFaces 2.2.10 renders only last one in link URL instead of both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MYFACES-4052) Multiple with same name encodes only last one in link URL
[
https://issues.apache.org/jira/browse/MYFACES-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339278#comment-15339278
]
Bauke Scholtz edited comment on MYFACES-4052 at 6/20/16 10:11 AM:
--
You mean, you interpreted the spec as: "if there are multiple values in the
**same** source, the latter value must replace all instances of the previous
value"?
was (Author: balusc):
You mean, you interpreted the spec as: "if there are multiple values in the
same source, the latter value must replace all instances of the previous value"?
> Multiple with same name encodes only last one in link URL
> ---
>
> Key: MYFACES-4052
> URL: https://issues.apache.org/jira/browse/MYFACES-4052
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.2.10
> Environment: TomEE 7.0.0
>Reporter: Bauke Scholtz
>Assignee: Leonardo Uribe
>
> Consider:
> {code}
>
>
>
>
> {code}
> MyFaces 2.2.10 renders only last one in link URL instead of both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MYFACES-4052) Multiple with same name encodes only last one in link URL
[
https://issues.apache.org/jira/browse/MYFACES-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339278#comment-15339278
]
Bauke Scholtz commented on MYFACES-4052:
You mean, you interpreted the spec as: "if there are multiple values in the
same source, the latter value must replace all instances of the previous value"?
> Multiple with same name encodes only last one in link URL
> ---
>
> Key: MYFACES-4052
> URL: https://issues.apache.org/jira/browse/MYFACES-4052
> Project: MyFaces Core
> Issue Type: Bug
>Affects Versions: 2.2.10
> Environment: TomEE 7.0.0
>Reporter: Bauke Scholtz
>Assignee: Leonardo Uribe
>
> Consider:
> {code}
>
>
>
>
> {code}
> MyFaces 2.2.10 renders only last one in link URL instead of both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MYFACES-4052) Multiple with same name encodes only last one in link URL
Bauke Scholtz created MYFACES-4052:
--
Summary: Multiple with same name encodes only last one
in link URL
Key: MYFACES-4052
URL: https://issues.apache.org/jira/browse/MYFACES-4052
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.2.10
Environment: TomEE 7.0.0
Reporter: Bauke Scholtz
Consider:
{code}
{code}
MyFaces 2.2.10 renders only last one in link URL instead of both.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MYFACES-4040) name conflicts with attributes
Bauke Scholtz created MYFACES-4040:
--
Summary: name conflicts with attributes
Key: MYFACES-4040
URL: https://issues.apache.org/jira/browse/MYFACES-4040
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.2.9
Reporter: Bauke Scholtz
https://java.net/jira/browse/JAVASERVERFACES-4115 also applies to MyFaces.
{code}
{code}
In MyFaces, the actual behavior is equal to and
request.getParameter("execute") returns null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MYFACES-4001) Outdated java.sun.com XML namespaces in 2.2 tagdoc
Bauke Scholtz created MYFACES-4001: -- Summary: Outdated java.sun.com XML namespaces in 2.2 tagdoc Key: MYFACES-4001 URL: https://issues.apache.org/jira/browse/MYFACES-4001 Project: MyFaces Core Issue Type: Improvement Reporter: Bauke Scholtz https://myfaces.apache.org/core22/myfaces-impl/tagdoc.html Old java.sun.com XML namespaces need to be replaced by xmlns.jcp.org XML namespaces which was introduced since Java EE 7. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MYFACES-4001) Outdated java.sun.com XML namespaces in 2.2 tagdoc
[ https://issues.apache.org/jira/browse/MYFACES-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588675#comment-14588675 ] Bauke Scholtz commented on MYFACES-4001: No, I can't. Outdated java.sun.com XML namespaces in 2.2 tagdoc -- Key: MYFACES-4001 URL: https://issues.apache.org/jira/browse/MYFACES-4001 Project: MyFaces Core Issue Type: Improvement Reporter: Bauke Scholtz https://myfaces.apache.org/core22/myfaces-impl/tagdoc.html Old java.sun.com XML namespaces need to be replaced by xmlns.jcp.org XML namespaces which was introduced since Java EE 7. See also http://stackoverflow.com/a/30780147/157882 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYFACES-3992) f:ajax doesn't append javax.faces.ViewState back on re-render of form in stateless view
Bauke Scholtz created MYFACES-3992: -- Summary: f:ajax doesn't append javax.faces.ViewState back on re-render of form in stateless view Key: MYFACES-3992 URL: https://issues.apache.org/jira/browse/MYFACES-3992 Project: MyFaces Core Issue Type: Bug Affects Versions: 2.2.8 Environment: MyFaces 2.2.8 + Tomcat 8.0.21 Reporter: Bauke Scholtz http://stackoverflow.com/q/30530686/157882 javax.faces.ViewState hidden input field get lost when f:ajax updates a form in a stateless view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYFACES-3942) f:viewParam binding causes NPE because UIViewRoot is null
Bauke Scholtz created MYFACES-3942:
--
Summary: f:viewParam binding causes NPE because UIViewRoot is
null
Key: MYFACES-3942
URL: https://issues.apache.org/jira/browse/MYFACES-3942
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.2.6
Environment: Tomcat 8.0.14 and TomEE 2.0.0 snapshot.
Reporter: Bauke Scholtz
Using {{binding}} attribute on {{f:viewParam}} as follows:
{code}
f:viewParam name=foo binding=#{foo} /
{code}
causes regardless of the binding location (Facelet itself as demonstrated
above, request scoped bean, session scoped bean, etc) the following exception:
{code}
java.lang.NullPointerException
at
org.apache.myfaces.view.facelets.tag.jsf.ComponentTagHandlerDelegate.createComponent(ComponentTagHandlerDelegate.java:534)
at
org.apache.myfaces.view.facelets.tag.jsf.ComponentTagHandlerDelegate.apply(ComponentTagHandlerDelegate.java:284)
at
javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:50)
at
org.apache.myfaces.view.facelets.tag.jsf.core.ViewMetadataHandler.apply(ViewMetadataHandler.java:85)
at
org.apache.myfaces.view.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:195)
at
org.apache.myfaces.view.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:59)
at
org.apache.myfaces.view.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:48)
at
org.apache.myfaces.view.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:188)
at
org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage$FaceletViewMetadata.createMetadataView(FaceletViewDeclarationLanguage.java:2752)
at
org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:255)
at
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:196)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:143)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
...
{code}
Turns out that {{UIViewRoot}} is {{null}} while the code didn't expect that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MYFACES-3537) TagLibraryConfig doesn't recognize facelet-taglibdescription
Bauke Scholtz created MYFACES-3537:
--
Summary: TagLibraryConfig doesn't recognize
facelet-taglibdescription
Key: MYFACES-3537
URL: https://issues.apache.org/jira/browse/MYFACES-3537
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 2.1.7
Environment: Windows 7 x64, JDK 1.7.0_4, Eclipse Indigo SR2, Tomcat
7.0.27, MyFaces 2.1.7
Reporter: Bauke Scholtz
The trigger is this OmniFaces issue:
http://code.google.com/p/omnifaces/issues/detail?id=9
OmniFaces has a {{description}} element right before {{namespace}} element
in the taglib.xml files which describes the taglib.
{code:xml}
facelet-taglib id=o
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd;
version=2.0
descriptionOmniFaces UI components./description
namespacehttp://omnifaces.org/ui/namespace
...
/facelet-taglib
{code}
It get parsed fine on Mojarra, but on MyFaces 2.1.7 the following exception
occurs:
{code}
Caused by: org.xml.sax.SAXException: Error Handling
[jar:file:/C:/Users/BalusC/Documents/Work/M4N/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp2/wtpwebapps/omnifaces_test/WEB-INF/lib/omnifaces.jar!/META-INF/omnifaces-ui.taglib.xml@20,33]
description
at
org.apache.myfaces.view.facelets.compiler.TagLibraryConfig$LibraryHandler.endElement(TagLibraryConfig.java:609)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
at
org.apache.myfaces.view.facelets.compiler.TagLibraryConfig.create(TagLibraryConfig.java:788)
... 37 more
{code}
Removing the {{description}} element solves the problem. But this is not what
we want. Putting the {{description}} element _after_ the {{namespace}}
element also solves the problem, but Eclipse marks the XML invalid according
the XSD.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOMAHAWK-1551) f:ajax doesn't work in t:selectOneRadio layout=spread
f:ajax doesn't work in t:selectOneRadio layout=spread
---
Key: TOMAHAWK-1551
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1551
Project: MyFaces Tomahawk
Issue Type: Bug
Components: selectOneRadio / radio
Affects Versions: 1.1.10
Environment: Mojarra 2.0.3, Tomcat 6.0.29, Eclipse 3.6, Windows XP
Reporter: Bauke Scholtz
The f:ajax doesn't work in t:selectOneRadio layout=spread. Judging the HTML
source, it incorrectly obtains the client ID of t:selectOneRadio instead of the
one of the t:radio (or just this) as first argument of the ajax function.
This is been used in document.getElementById() which in turns returns
null/undefinied and breaks the ajax function.
XHTML source:
t:selectOneRadio id=item value=#{bean.item} layout=spread
f:selectItems value=#{bean.items} /
f:ajax event=click /
/t:selectOneRadio
t:radio for=item index=0 /
t:radio for=item index=0 /
Generated HTML source (labels omitted):
input id=form:item:0 type=radio name=form:item value=item1
onclick=mojarra.ab('form:item',event,'click',0,0) /
input id=form:item:1 type=radio name=form:item value=item2
onclick=mojarra.ab('form:item',event,'click',0,0) /
Expected HTML source (labels omitted):
input id=form:item:0 type=radio name=form:item value=item1
onclick=mojarra.ab('form:item:0',event,'click',0,0) /
input id=form:item:1 type=radio name=form:item value=item2
onclick=mojarra.ab('form:item:1',event,'click',0,0) /
OR
input id=form:item:0 type=radio name=form:item value=item1
onclick=mojarra.ab(this,event,'click',0,0) /
input id=form:item:1 type=radio name=form:item value=item2
onclick=mojarra.ab(this,event,'click',0,0) /
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOMAHAWK-1485) t:dataList should not render li element when iterated element is not rendered
[
https://issues.apache.org/jira/browse/TOMAHAWK-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12829299#action_12829299
]
Bauke Scholtz commented on TOMAHAWK-1485:
-
Well, I know that, that's also why I didn't report it as a bug. but as an
improvement. It could just check if none of its direct children are rendered.
t:dataList should not render li element when iterated element is not
rendered
---
Key: TOMAHAWK-1485
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1485
Project: MyFaces Tomahawk
Issue Type: Improvement
Components: Data List
Affects Versions: 1.1.9
Environment: Tomcat 6.0.20, Mojarra 1.2_14, Tomahawk 1.1.9,
commons-el 1.0, commons-fileupload 1.2.1, commons-io 1.4, commons-logging
1.1.1
Reporter: Bauke Scholtz
Assignee: Leonardo Uribe
The following code example:
%...@taglib uri=http://java.sun.com/jsf/core; prefix=f %
%...@taglib uri=http://myfaces.apache.org/tomahawk; prefix=t %
%
request.setAttribute(list, java.util.Arrays.asList(1, 2, 3, 4, 5));
%
f:view
!doctype html
html lang=en
head
titleTomahawk t:dataList demo/title
/head
body
t:dataList value=#{list} var=item layout=unorderedList
t:outputText value=#{item} rendered=#{item % 2 == 0} /
/t:dataList
/body
/html
/f:view
results in following:
*
* 2
*
* 4
*
while the following is expected:
* 2
* 4
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (TOMAHAWK-1485) t:dataList should not render li element when iterated element is not rendered
t:dataList should not render li element when iterated element is not rendered
---
Key: TOMAHAWK-1485
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1485
Project: MyFaces Tomahawk
Issue Type: Improvement
Components: Data List
Affects Versions: 1.1.9
Environment: Tomcat 6.0.20, Mojarra 1.2_14, Tomahawk 1.1.9, commons-el
1.0, commons-fileupload 1.2.1, commons-io 1.4, commons-logging 1.1.1
Reporter: Bauke Scholtz
The following code example:
%...@taglib uri=http://java.sun.com/jsf/core; prefix=f %
%...@taglib uri=http://myfaces.apache.org/tomahawk; prefix=t %
%
request.setAttribute(list, java.util.Arrays.asList(1, 2, 3, 4, 5));
%
f:view
!doctype html
html lang=en
head
titleTomahawk t:dataList demo/title
/head
body
t:dataList value=#{list} var=item layout=unorderedList
t:outputText value=#{item} rendered=#{item % 2 == 0} /
/t:dataList
/body
/html
/f:view
results in following:
*
* 2
*
* 4
*
while the following is expected:
* 2
* 4
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-1979) null-Values from View converted to standard-values using tomcat 6.0.16 or 6.0.18
[ https://issues.apache.org/jira/browse/MYFACES-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640894#action_12640894 ] Bauke Scholtz commented on MYFACES-1979: This is actually behaviour by EL specification. Please vote against this behaviour if you want: https://jsp-spec-public.dev.java.net/issues/show_bug.cgi?id=183 null-Values from View converted to standard-values using tomcat 6.0.16 or 6.0.18 -- Key: MYFACES-1979 URL: https://issues.apache.org/jira/browse/MYFACES-1979 Project: MyFaces Core Issue Type: Bug Affects Versions: 1.2.4 Environment: myfaces core 1.2.4, tomahawk 1.1.7, sandbox 1.1.7, tomcat 6.0.16 or 6.0.18 Reporter: Martin Winkler Hi there, Using tomcat 6.0.16 or 6.0.18 there seems to be a bug with myfaces (currently using 1.2.4, but had the bug with 1.2.2, too). If I leave Input-Fields empty, the model is updatet with default-values (e.g. 0 for a Long-variable or a zero-length String for a String-variable) for the corresponding variables instead of null-Values. I think the bug is not located in converters. Found some information here: http://www.icefaces.org/JForum/posts/list/8024.page It would be good to use tomcat 6.0.18 because in older versions there is a security issue. With tomcat 6.0.14 everythiing is allright .. Thanks, Martin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
