Re: Incompatibility of Tomahawk + JSF 2
Thanks Leonardo, I've downloaded the jar file and put in my /web-inf/lib folder. But I get the following error: java.lang.IllegalArgumentException at java.util.EventObject.init(EventObject.java:47) at javax.faces.event.SystemEvent.init(SystemEvent.java:67) at javax.faces.event.ComponentSystemEvent.init(ComponentSystemEvent.java:69) at com.sun.faces.lifecycle.RestoreViewPhase.deliverPostRestoreStateEvent(RestoreViewPhase.java:256) at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:245) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:107) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:308) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1661) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:937) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3810) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583) Could you tell me how I should config my application? And also, does this build work with JSF2 or I need Myfaces 2 to make it to work? Many thank Fiona -- View this message in context: http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29549725.html Sent from the My Faces - Dev mailing list archive at Nabble.com.
Re: Incompatibility of Tomahawk + JSF 2
Hi 2010/8/27 fionalee fiona@medicareaustralia.gov.au Thanks Leonardo, I've downloaded the jar file and put in my /web-inf/lib folder. But I get the following error: java.lang.IllegalArgumentException at java.util.EventObject.init(EventObject.java:47) at javax.faces.event.SystemEvent.init(SystemEvent.java:67) at javax.faces.event.ComponentSystemEvent.init(ComponentSystemEvent.java:69) at com.sun.faces.lifecycle.RestoreViewPhase.deliverPostRestoreStateEvent(RestoreViewPhase.java:256) at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:245) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:107) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:308) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1661) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:937) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3810) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583) Could you tell me how I should config my application? And also, does this build work with JSF2 or I need Myfaces 2 to make it to work? That one seems to be a problem not related to tomahawk. No special configuration is required. You can see an application running with jsf 2 and tomahawk here: http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/examples/simple20/ Tomahawk works with both myfaces and mojarra (ri). Remember if you use facelets, in jsf 2 this is included in myfaces/ri jars. best regards, Leonardo Uribe
Re: Incompatibility of Tomahawk + JSF 2
Leonardo, Many thanks for your help. I finally get Tomahawk working in my new project. The problem was something else. I should have had confident in you. You saved heaps for our project. Thanks regards Fiona -- View this message in context: http://old.nabble.com/Incompatibility-of-Tomahawk-%2B-JSF-2-tp29537768p29549942.html Sent from the My Faces - Dev mailing list archive at Nabble.com.
Re: hud...@myfaces
Done! On Thu, Aug 26, 2010 at 11:44 PM, Jakob Korherr jakob.korh...@gmail.com wrote: Hi Matthias, Can you please add an account for me too? I'd like to check the current20 build. Thanks! Jakob 2010/8/25 Matthias Wessendorf mat...@apache.org Thanks Bernd! Right now the following committers have been added: -Bernd Bohmann -Grant Smith -Matthias Wessendorf -M On Wed, Aug 25, 2010 at 8:20 AM, Bernd Bohmann bernd.bohm...@atanion.com wrote: Hello for trying hudson instead of continuum you need a hudson account. You can ask matthias for adding you to the hudson-jobadmin group on people.apache.org modify_appgroups.pl hudson-jobadmin --add=your apache username see: http://wiki.apache.org/general/Hudson#How_do_I_get_an_account for recommended or mandatory settings see: http://wiki.apache.org/general/Hudson#Are_there_recommended_or_mandatory_Hudson_settings_for_ASF_projects.3F Regards Bernd -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Commented: (MYFACES-2165) concurrent issue in initializing myfaces 1.1.6
[ https://issues.apache.org/jira/browse/MYFACES-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903344#action_12903344 ] Anudeep CA commented on MYFACES-2165: - Thanks a lot. This will be very much helpful. Regarding the UI issues faced when upgraded with higher versions of jars, below are the stack traces found. Although I am not sure if the errors are due to myfaces alone. I am posting them only for your information. Error for 1.2.6 jars: This error occurred when launching a page(page did not launch) having a data table with column for Date and time. (ApplicationDispatcher.java:719) [[jsp]] Servlet.service() for servlet jsp threw exception java.lang.IllegalArgumentException: Cannot convert IST of type class java.lang.String to class java.util.TimeZone at org.apache.el.lang.ELSupport.coerceToType(ELSupport.java:374) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:188) at org.apache.jasper.el.JspValueExpression.getValue(JspValueExpression.java:101) at org.apache.myfaces.shared_impl.taglib.UIComponentELTagUtils.evaluateValueExpression(UIComponentELTagUtils.java:378) at org.apache.myfaces.taglib.core.ConvertDateTimeTag.setConverterTimeZone(ConvertDateTimeTag.java:213) at org.apache.myfaces.taglib.core.ConvertDateTimeTag.createConverter(ConvertDateTimeTag.java:137) at javax.faces.webapp.ConverterELTag.doStartTag(ConverterELTag.java:62) at org.apache.myfaces.taglib.core.ConvertDateTimeTag.doStartTag(ConvertDateTimeTag.java:125) . An exception occurred javax.faces.FacesException: java.lang.IllegalArgumentException: Cannot convert IST of type class java.lang.String to class java.util.TimeZone at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:347) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.buildView(JspViewHandlerImpl.java:486) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:337) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:229) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:155) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:301) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) Errors found for 1.1.7 jars: Even this page had a data table. (ApplicationDispatcher.java:719) [[jsp]] Servlet.service() for servlet jsp threw exception java.lang.NullPointerException at javax.faces.component.html.HtmlOutputText.getStyleClass(HtmlOutputText.java:76) at sun.reflect.GeneratedMethodAccessor507.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javax.faces.component._ComponentAttributesMap.getComponentProperty(_ComponentAttributesMap.java:394) at javax.faces.component._ComponentAttributesMap.get(_ComponentAttributesMap.java:235) at org.apache.myfaces.shared_impl.renderkit.html.HtmlRendererUtils.renderHTMLAttributesWithOptionalStartElement(HtmlRendererUtils.java:585) at org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.renderOutputText(HtmlTextRendererBase.java:108) at org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.renderOutput(HtmlTextRendererBase.java:80) at org.apache.myfaces.shared_impl.renderkit.html.HtmlTextRendererBase.encodeEnd(HtmlTextRendererBase.java:57) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:775) at
[jira] Created: (TRINIDAD-1897) PPR Rendering sometimes not working in firefox when uploading files using inputfile due to a javascript error
PPR Rendering sometimes not working in firefox when uploading files using inputfile due to a javascript error - Key: TRINIDAD-1897 URL: https://issues.apache.org/jira/browse/TRINIDAD-1897 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.2.13-core Environment: Firefox 3.5.11 Reporter: Mike Toggweiler Uploading a file within firefox causes a javascript error while rerendeing part of a page using ppr on slow internet connectivities. Javascript error matched by firebug is: a56 is undefined Line 10433 Error occurs in function _getFirstElementFromFragment where accessing dom node doesn't work. Within debug mode dom nodes value may be evaluated to a real value, maybe there is a timing problem due to a slow internet connectivity? Same problem doesn't occur neither within IE nor on the development System on localhost within firefox. Do you have any idea? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
_SelectItemsUtil._ValueConverter
Hi,
what is the purpose of _SelectItemsUtil._ValueConverter in
UISelectMany.validateValue(FacesContext, Object) ?
Two weird things:
1) it wraps value into new String[] { value }
2) it calls UISelectMany.this.getConvertedValue and it leads to
Rendered.getConvertedValue call
I don't see sence in call of UISelectMany.this.getConvertedValue
because this already done: we are in method validateValue here and
conversion with Renderer.getConvertedValue is done already. This causes
calls to Renderer.getConvertedValue during process validation which is
unintented I think.
Regards,
Martin Kočí
Re: _SelectItemsUtil._ValueConverter
Hi Martin,
The purpose of this conversion is that the value of the SelectItems may be a
String, but the real (already converted) value of the UISelectMany may be
something else, e.g. Float. Imagine the following scenario:
h:selectManyCheckbox value=#{myBean.inputFloatArray}
f:selectItem itemValue=1.1 /
f:selectItem itemValue=1.2 /
f:selectItem itemValue=1.3 /
/h:selectManyCheckbox
The itemValues of all SelectItems are Strings, but the UISelectMany points
to a property which is of type Float[]. Now because of the fact that all
Strings can be converted into Floats, this scenario must work.
If you now take a look at _SelectItemsUtil.matchValue(), you can see that
not the component's value, but the value of the SelectItem is converted via
the _ValueConverter:
SelectItem item = selectItemsIter.next();
Object itemValue = item.getValue();
if(converter != null itemValue instanceof String)
{
itemValue = converter.getConvertedValue(context, (String)itemValue);
}
and then matched against the real value (again which is e.g. Float):
if (value==itemValue || value.equals(itemValue))
{
return true;
}
Furthermore the converter has to be invoked with the wrapped String in a
String[], because UISelectMany.getConvertedValue() needs a submittedValue of
type String[].
Is this clear for you or should I explain it in more detail?
Regards,
Jakob
2010/8/27 Martin Koci martin.k...@aura.cz
Hi,
what is the purpose of _SelectItemsUtil._ValueConverter in
UISelectMany.validateValue(FacesContext, Object) ?
Two weird things:
1) it wraps value into new String[] { value }
2) it calls UISelectMany.this.getConvertedValue and it leads to
Rendered.getConvertedValue call
I don't see sence in call of UISelectMany.this.getConvertedValue
because this already done: we are in method validateValue here and
conversion with Renderer.getConvertedValue is done already. This causes
calls to Renderer.getConvertedValue during process validation which is
unintented I think.
Regards,
Martin Kočí
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
[jira] Created: (MYFACES-2894) Eager bean is not created at application startup
Eager bean is not created at application startup
Key: MYFACES-2894
URL: https://issues.apache.org/jira/browse/MYFACES-2894
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.2-SNAPSHOT
Reporter: Nick Belaevski
For the following code:
managed-bean eager=true
managed-bean-nameeagerBean/managed-bean-name
managed-bean-classdemo.EagerBean/managed-bean-class
managed-bean-scopeapplication/managed-bean-scope
/managed-bean
package demo;
public class EagerBean {
public EagerBean() {
System.out.println(EagerBean.EagerBean());
}
}
bean is not being initialized at application startup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2894) Eager bean is not created at application startup
[
https://issues.apache.org/jira/browse/MYFACES-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903425#action_12903425
]
Jakob Korherr commented on MYFACES-2894:
looks like we oversaw this feature, there is nothing implemented so far.
Eager bean is not created at application startup
Key: MYFACES-2894
URL: https://issues.apache.org/jira/browse/MYFACES-2894
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.2-SNAPSHOT
Reporter: Nick Belaevski
For the following code:
managed-bean eager=true
managed-bean-nameeagerBean/managed-bean-name
managed-bean-classdemo.EagerBean/managed-bean-class
managed-bean-scopeapplication/managed-bean-scope
/managed-bean
package demo;
public class EagerBean {
public EagerBean() {
System.out.println(EagerBean.EagerBean());
}
}
bean is not being initialized at application startup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: _SelectItemsUtil._ValueConverter
Hi,
I understand that requirement but isn't it EL coercion task ? :
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=152
and from UISelectMany.validateValue JavaDoc:
...Before comparing each option, coerce the option value type to the
type of this component's value following the Expression Language
coercion rules ...
Regards,
Martin Kočí
Jakob Korherr píše v Pá 27. 08. 2010 v 15:31 +0200:
Hi Martin,
The purpose of this conversion is that the value of the SelectItems
may be a String, but the real (already converted) value of the
UISelectMany may be something else, e.g. Float. Imagine the following
scenario:
h:selectManyCheckbox value=#{myBean.inputFloatArray}
f:selectItem itemValue=1.1 /
f:selectItem itemValue=1.2 /
f:selectItem itemValue=1.3 /
/h:selectManyCheckbox
The itemValues of all SelectItems are Strings, but the UISelectMany
points to a property which is of type Float[]. Now because of the fact
that all Strings can be converted into Floats, this scenario must
work.
If you now take a look at _SelectItemsUtil.matchValue(), you can see
that not the component's value, but the value of the SelectItem is
converted via the _ValueConverter:
SelectItem item = selectItemsIter.next();
Object itemValue = item.getValue();
if(converter != null itemValue instanceof String)
{
itemValue = converter.getConvertedValue(context,
(String)itemValue);
}
and then matched against the real value (again which is e.g. Float):
if (value==itemValue || value.equals(itemValue))
{
return true;
}
Furthermore the converter has to be invoked with the wrapped String in
a String[], because UISelectMany.getConvertedValue() needs a
submittedValue of type String[].
Is this clear for you or should I explain it in more detail?
Regards,
Jakob
2010/8/27 Martin Koci martin.k...@aura.cz
Hi,
what is the purpose of _SelectItemsUtil._ValueConverter in
UISelectMany.validateValue(FacesContext, Object) ?
Two weird things:
1) it wraps value into new String[] { value }
2) it calls UISelectMany.this.getConvertedValue and it leads
to
Rendered.getConvertedValue call
I don't see sence in call of
UISelectMany.this.getConvertedValue
because this already done: we are in method validateValue here
and
conversion with Renderer.getConvertedValue is done already.
This causes
calls to Renderer.getConvertedValue during process validation
which is
unintented I think.
Regards,
Martin Kočí
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
Re: _SelectItemsUtil._ValueConverter
Hi,
Hmm, could be. I guess this code was introduced in JSF 1.1 (no unified EL
and thus no EL coercion available) and never changed in later versions.
If you can make the scenario work using EL coercion, please file an issue in
the JIRA. Thanks!
Regards,
Jakob
2010/8/27 Martin Koci martin.k...@aura.cz
Hi,
I understand that requirement but isn't it EL coercion task ? :
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=152
and from UISelectMany.validateValue JavaDoc:
...Before comparing each option, coerce the option value type to the
type of this component's value following the Expression Language
coercion rules ...
Regards,
Martin Kočí
Jakob Korherr píše v Pá 27. 08. 2010 v 15:31 +0200:
Hi Martin,
The purpose of this conversion is that the value of the SelectItems
may be a String, but the real (already converted) value of the
UISelectMany may be something else, e.g. Float. Imagine the following
scenario:
h:selectManyCheckbox value=#{myBean.inputFloatArray}
f:selectItem itemValue=1.1 /
f:selectItem itemValue=1.2 /
f:selectItem itemValue=1.3 /
/h:selectManyCheckbox
The itemValues of all SelectItems are Strings, but the UISelectMany
points to a property which is of type Float[]. Now because of the fact
that all Strings can be converted into Floats, this scenario must
work.
If you now take a look at _SelectItemsUtil.matchValue(), you can see
that not the component's value, but the value of the SelectItem is
converted via the _ValueConverter:
SelectItem item = selectItemsIter.next();
Object itemValue = item.getValue();
if(converter != null itemValue instanceof String)
{
itemValue = converter.getConvertedValue(context,
(String)itemValue);
}
and then matched against the real value (again which is e.g. Float):
if (value==itemValue || value.equals(itemValue))
{
return true;
}
Furthermore the converter has to be invoked with the wrapped String in
a String[], because UISelectMany.getConvertedValue() needs a
submittedValue of type String[].
Is this clear for you or should I explain it in more detail?
Regards,
Jakob
2010/8/27 Martin Koci martin.k...@aura.cz
Hi,
what is the purpose of _SelectItemsUtil._ValueConverter in
UISelectMany.validateValue(FacesContext, Object) ?
Two weird things:
1) it wraps value into new String[] { value }
2) it calls UISelectMany.this.getConvertedValue and it leads
to
Rendered.getConvertedValue call
I don't see sence in call of
UISelectMany.this.getConvertedValue
because this already done: we are in method validateValue here
and
conversion with Renderer.getConvertedValue is done already.
This causes
calls to Renderer.getConvertedValue during process validation
which is
unintented I think.
Regards,
Martin Kočí
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
[jira] Created: (MYFACES-2895) Messages component cannot be updated by ajax without wrapping it
Messages component cannot be updated by ajax without wrapping it
Key: MYFACES-2895
URL: https://issues.apache.org/jira/browse/MYFACES-2895
Project: MyFaces Core
Issue Type: Bug
Reporter: Nick Belaevski
When there are no faces messages generated, h:messages component does not
render no HTML tags, so it cannot be updated by ajax.
To reproduce:
h:messages id=messages /
h:commandButton value=Invoke listener by
type action=#{bean.generateMessage}
f:ajax render=messages /
/h:commandButton
No messages will appear. As a workaround messages component can be wrapped into
h:panelGroup that's id will be specified in 'render':
h:panelGroup id=messages
h:messages /
/h:panelGroup
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2896) PartialViewContextImpl ignores executeIds/renderIds/renderAll of wrapping PartialViewContext
PartialViewContextImpl ignores executeIds/renderIds/renderAll of wrapping PartialViewContext Key: MYFACES-2896 URL: https://issues.apache.org/jira/browse/MYFACES-2896 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.2-SNAPSHOT Reporter: Nick Belaevski When PartialViewContextImpl#processPartial(PhaseId phaseId) is executed, executeIds/renderIds/renderAll of wrapping PartialViewContext are ignored: this.getRenderIds() etc are called instead of calling _facesContext.getPartialViewContext().getExecuteIds() like is done for PartialResponseWriter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: _SelectItemsUtil._ValueConverter
I didn't totally think through if it is usable in this case, but more
general, if you can prevent it, do not use EL coercion. Why?
As specified, EL coercion will coerce null to 0 or an . For the next
version of the EL, this behaviour might be configurable.
best regards,
Martin
On 8/27/10, Jakob Korherr jakob.korh...@gmail.com wrote:
Hi,
Hmm, could be. I guess this code was introduced in JSF 1.1 (no unified EL
and thus no EL coercion available) and never changed in later versions.
If you can make the scenario work using EL coercion, please file an issue in
the JIRA. Thanks!
Regards,
Jakob
2010/8/27 Martin Koci martin.k...@aura.cz
Hi,
I understand that requirement but isn't it EL coercion task ? :
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=152
and from UISelectMany.validateValue JavaDoc:
...Before comparing each option, coerce the option value type to the
type of this component's value following the Expression Language
coercion rules ...
Regards,
Martin Kočí
Jakob Korherr píše v Pá 27. 08. 2010 v 15:31 +0200:
Hi Martin,
The purpose of this conversion is that the value of the SelectItems
may be a String, but the real (already converted) value of the
UISelectMany may be something else, e.g. Float. Imagine the following
scenario:
h:selectManyCheckbox value=#{myBean.inputFloatArray}
f:selectItem itemValue=1.1 /
f:selectItem itemValue=1.2 /
f:selectItem itemValue=1.3 /
/h:selectManyCheckbox
The itemValues of all SelectItems are Strings, but the UISelectMany
points to a property which is of type Float[]. Now because of the fact
that all Strings can be converted into Floats, this scenario must
work.
If you now take a look at _SelectItemsUtil.matchValue(), you can see
that not the component's value, but the value of the SelectItem is
converted via the _ValueConverter:
SelectItem item = selectItemsIter.next();
Object itemValue = item.getValue();
if(converter != null itemValue instanceof String)
{
itemValue = converter.getConvertedValue(context,
(String)itemValue);
}
and then matched against the real value (again which is e.g. Float):
if (value==itemValue || value.equals(itemValue))
{
return true;
}
Furthermore the converter has to be invoked with the wrapped String in
a String[], because UISelectMany.getConvertedValue() needs a
submittedValue of type String[].
Is this clear for you or should I explain it in more detail?
Regards,
Jakob
2010/8/27 Martin Koci martin.k...@aura.cz
Hi,
what is the purpose of _SelectItemsUtil._ValueConverter in
UISelectMany.validateValue(FacesContext, Object) ?
Two weird things:
1) it wraps value into new String[] { value }
2) it calls UISelectMany.this.getConvertedValue and it leads
to
Rendered.getConvertedValue call
I don't see sence in call of
UISelectMany.this.getConvertedValue
because this already done: we are in method validateValue here
and
conversion with Renderer.getConvertedValue is done already.
This causes
calls to Renderer.getConvertedValue during process validation
which is
unintented I think.
Regards,
Martin Kočí
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
--
Jakob Korherr
blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
[jira] Commented: (MYFACES-2458) Miscellaneous AJAX bugs
[
https://issues.apache.org/jira/browse/MYFACES-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903458#action_12903458
]
Nick Belaevski commented on MYFACES-2458:
-
I have two issues with 2.0.2-SNAPSHOT:
1) Function _Lang.getEventTarget(...) fails to find form if event is one of
ajax events (e.g. 'error'). In this case event contains 'source' property, but
'srcElement' or 'target' is checked
2) This fails:
h:commandButton value=Button action=#{bean.action}
f:ajax onerror=alert(1) /
/h:commandButton
alert is shown before request is actually submitted. This works as expected:
h:commandButton value=Button action=#{bean.action}
f:ajax onerror=function() {alert(1)} /
/h:commandButton
Miscellaneous AJAX bugs
---
Key: MYFACES-2458
URL: https://issues.apache.org/jira/browse/MYFACES-2458
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.0-alpha-2
Reporter: Curtiss Howard
Priority: Minor
There are a couple minor AJAX-related bugs:
* h:commandButton needs to append return false; for onclick when a behavior
chain is present.
* if f:ajax disabled=true, the AJAX call is still emitted.
* Possible issue with f:ajax execute=multiple ids. Seems the
javax.faces.partial.execute request param may differ from Sun RI.
* Unable to restore StateHolder when listener is specified for f:ajax.
* f:ajax onevent not being handled.
* f:ajax onerror not being handled.
* f:ajax render=@all not working correctly.
* f:ajax render=@form not working correctly.
* f:ajax render=@this not working correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2894) Eager bean is not created at application startup
[
https://issues.apache.org/jira/browse/MYFACES-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr resolved MYFACES-2894.
Fix Version/s: 2.0.2-SNAPSHOT
Resolution: Fixed
This works now.
Actually we did not support this feature at all until now (we did not even
check the eager attribute in the faces-config or in @ManagedBean).
Eager bean is not created at application startup
Key: MYFACES-2894
URL: https://issues.apache.org/jira/browse/MYFACES-2894
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.2-SNAPSHOT
Reporter: Nick Belaevski
Assignee: Jakob Korherr
Fix For: 2.0.2-SNAPSHOT
For the following code:
managed-bean eager=true
managed-bean-nameeagerBean/managed-bean-name
managed-bean-classdemo.EagerBean/managed-bean-class
managed-bean-scopeapplication/managed-bean-scope
/managed-bean
package demo;
public class EagerBean {
public EagerBean() {
System.out.println(EagerBean.EagerBean());
}
}
bean is not being initialized at application startup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2165) concurrent issue in initializing myfaces 1.1.6
[ https://issues.apache.org/jira/browse/MYFACES-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903503#action_12903503 ] Leonardo Uribe commented on MYFACES-2165: - The error found with 1.1.7: (ApplicationDispatcher.java:719) [[jsp]] Servlet.service() for servlet jsp threw exception java.lang.NullPointerException at javax.faces.component.html.HtmlOutputText.getStyleClass(HtmlOutputText.java:76 was solved on MYFACES-2006. 1.1.8 jars released include this fix. So it could be good if you try 1.1.8 jars and if works I suggest you use them. I'll investigate the one related to ConvertDateTimeTag concurrent issue in initializing myfaces 1.1.6 -- Key: MYFACES-2165 URL: https://issues.apache.org/jira/browse/MYFACES-2165 Project: MyFaces Core Issue Type: Bug Affects Versions: 1.1.6 Environment: tomcat 6.0.18 java 1.6.0_06 Reporter: xuxiankun Assignee: Leonardo Uribe Priority: Critical Fix For: 1.1.7 Attachments: myfaces-1.1.5-patched.zip, MYFACES-2165.patch after starting tomcat, we will get a error when i visit a faces page. we can fix this issue by restarting tomcat. so i think it's concurrent issue. java.lang.NullPointerException at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getServletMapping(JspViewHandlerImpl.java:388) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:222) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216) at org.apache.shale.validator.faces.ValidatorViewHandler.renderView(ValidatorViewHandler.java:130) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:146) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:147) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at cn.com.brilliance.begen.webapp.servlet.BeGenFilter.doFilter(BeGenFilter.java:56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at cn.com.brilliance.begen.webapp.servlet.LoginServlet.doPost(LoginServlet.java:91) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at
[jira] Commented: (TRINIDAD-1894) setting org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT to false leads to exception
[
https://issues.apache.org/jira/browse/TRINIDAD-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903512#action_12903512
]
Jeanne Waldman commented on TRINIDAD-1894:
--
See https://issues.apache.org/jira/browse/TRINIDAD-147. The workaround says to
use
context-param
param-nameorg.apache.myfaces.trinidad.resource.DEBUG/param-name
param-valuetrue/param-value
/context-param
setting org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT to false leads to
exception
Key: TRINIDAD-1894
URL: https://issues.apache.org/jira/browse/TRINIDAD-1894
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 2.0.0.3-core
Environment: Java 6, Apache Tomcat 6/WebLogic 11
Reporter: Christoph Kainrath
Priority: Minor
context-param
param-nameorg.apache.myfaces.trinidad.DEBUG_JAVASCRIPT/param-name
param-valuefalse/param-value
/context-param
in web.xml leads to:
java.lang.NullPointerException
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.LibraryScriptlet._isDebug(LibraryScriptlet.java:223)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.LibraryScriptlet.getLibraryName(LibraryScriptlet.java:126)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.LibraryScriptlet.getLibraryURL(LibraryScriptlet.java:145)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.LibraryScriptlet.outputScriptletImpl(LibraryScriptlet.java:98)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.Scriptlet.outputScriptlet(Scriptlet.java:62)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.XhtmlUtils.addLib(XhtmlUtils.java:141)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.Scriptlet.outputDependency(Scriptlet.java:154)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.AliasedScriptlet.outputScriptletImpl(AliasedScriptlet.java:127)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.jsLibs.Scriptlet.outputScriptlet(Scriptlet.java:62)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.XhtmlUtils.addLib(XhtmlUtils.java:141)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.PanelPartialRootRenderer.encodeAll(PanelPartialRootRenderer.java:108)
at
org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.BodyRenderer.encodeAll(BodyRenderer.java:81)
at
org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:488)
If I remove the context-param element from my web.xml it works fine!
static private boolean _isDebug(FacesContext context)
{
if (_debugJavascript == null) {
String debugJavascript = context.
getExternalContext().getInitParameter(_DEBUG_JAVASCRIPT);
if (debugJavascript != null) {
if (debugJavascript.equalsIgnoreCase(true)) {
_debugJavascript = Boolean.TRUE;
// if Apache MyFaces Trinidad is running in production stage
// running with JavaScript debugging is not desired, therefore
// we generate a WARNING message; otherwise we just inform the user
if (context.isProjectStage(ProjectStage.Production))
{
_LOG.warning(RUNNING_DEBUG_JAVASCRIPT_IN_PRODUCTION_STAGE);
}
else
{
_LOG.info(RUNNING_DEBUG_JAVASCRIPT);
}
}
} else {
// if the _DEBUG_JAVASCRIPT parameter has NOT been specified, let us
// apply the DEFAULT values for the certain Project Stages:
// -PRODUCTION we want this value to be FALSE;
// -other stages we use TRUE
_debugJavascript = !(context.isProjectStage(ProjectStage.Production));
if (_debugJavascript)
{
_LOG.info(RUNNING_DEBUG_JAVASCRIPT);
}
}
}
return _debugJavascript.booleanValue();
}
-- _debugJavascript is only initialized if
(debugJavascript.equalsIgnoreCase(true)). Please insert something like
else _debugJavascript = Boolean.FALSE;
Thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2165) concurrent issue in initializing myfaces 1.1.6
[ https://issues.apache.org/jira/browse/MYFACES-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903521#action_12903521 ] Leonardo Uribe commented on MYFACES-2165: - The error found in 1.2.6: (ApplicationDispatcher.java:719) [[jsp]] Servlet.service() for servlet jsp threw exception java.lang.IllegalArgumentException: Cannot convert IST of type class java.lang.String to class java.util.TimeZone at org.apache.el.lang.ELSupport.coerceToType(ELSupport.java:374) It was solved on MYFACES-2177 which was fixed on 1.2.7. It could be good if you try 1.2.9 jars and if works I strongly suggest you use them, because it is considered the latest releases contains many fixed issues. concurrent issue in initializing myfaces 1.1.6 -- Key: MYFACES-2165 URL: https://issues.apache.org/jira/browse/MYFACES-2165 Project: MyFaces Core Issue Type: Bug Affects Versions: 1.1.6 Environment: tomcat 6.0.18 java 1.6.0_06 Reporter: xuxiankun Assignee: Leonardo Uribe Priority: Critical Fix For: 1.1.7 Attachments: myfaces-1.1.5-patched.zip, MYFACES-2165.patch after starting tomcat, we will get a error when i visit a faces page. we can fix this issue by restarting tomcat. so i think it's concurrent issue. java.lang.NullPointerException at org.apache.myfaces.application.jsp.JspViewHandlerImpl.getServletMapping(JspViewHandlerImpl.java:388) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:222) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216) at org.apache.shale.validator.faces.ValidatorViewHandler.renderView(ValidatorViewHandler.java:130) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:216) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:146) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:147) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at cn.com.brilliance.begen.webapp.servlet.BeGenFilter.doFilter(BeGenFilter.java:56) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at cn.com.brilliance.begen.webapp.servlet.LoginServlet.doPost(LoginServlet.java:91) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at
[jira] Commented: (MYFACES-2895) Messages component cannot be updated by ajax without wrapping it
[
https://issues.apache.org/jira/browse/MYFACES-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903629#action_12903629
]
Werner Punz commented on MYFACES-2895:
--
I am not sure if this really is a myfaces but, this sounds more like a spec bug
to me...
Messages component cannot be updated by ajax without wrapping it
Key: MYFACES-2895
URL: https://issues.apache.org/jira/browse/MYFACES-2895
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.2-SNAPSHOT
Reporter: Nick Belaevski
When there are no faces messages generated, h:messages component does not
render no HTML tags, so it cannot be updated by ajax.
To reproduce:
h:messages id=messages /
h:commandButton value=Invoke listener by
type action=#{bean.generateMessage}
f:ajax render=messages /
/h:commandButton
No messages will appear. As a workaround messages component can be wrapped
into h:panelGroup that's id will be specified in 'render':
h:panelGroup id=messages
h:messages /
/h:panelGroup
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (MYFACES-2895) Messages component cannot be updated by ajax without wrapping it
[
https://issues.apache.org/jira/browse/MYFACES-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903629#action_12903629
]
Werner Punz edited comment on MYFACES-2895 at 8/27/10 4:59 PM:
---
I am not sure if this really is a myfaces but, this sounds more like a spec bug
to me...
How is the mojarra behavior in this case, I assume the same.
was (Author: werpu):
I am not sure if this really is a myfaces but, this sounds more like a spec
bug to me...
Messages component cannot be updated by ajax without wrapping it
Key: MYFACES-2895
URL: https://issues.apache.org/jira/browse/MYFACES-2895
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.2-SNAPSHOT
Reporter: Nick Belaevski
When there are no faces messages generated, h:messages component does not
render no HTML tags, so it cannot be updated by ajax.
To reproduce:
h:messages id=messages /
h:commandButton value=Invoke listener by
type action=#{bean.generateMessage}
f:ajax render=messages /
/h:commandButton
No messages will appear. As a workaround messages component can be wrapped
into h:panelGroup that's id will be specified in 'render':
h:panelGroup id=messages
h:messages /
/h:panelGroup
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2458) Miscellaneous AJAX bugs
[ https://issues.apache.org/jira/browse/MYFACES-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903638#action_12903638 ] Werner Punz commented on MYFACES-2458: -- One sidenote to the execute multiple ids problem I recently ran into this issue while testing my code, and opened a discussion on the open mailinglist regarding it, this is somewhat of a weird problem because @this is added implicitely more or less by mojarra, which is somewhat of an undocumented feature, on the other hand is @this an explicit parameter which can be set in the execute phase. Just for the sake of keeping this valid I did not clone Mojarras behavior in this area, because I personally thought that the behavior of MyFaces is correct and Mojarras was not. The discussion in the open list not really gave a decisive clue on what was the really correct approach. Either way after rethingking it, it is probably better to try to keep a 100% compatibility to Mojarra in this shady area, and thanks for fixing it. Miscellaneous AJAX bugs --- Key: MYFACES-2458 URL: https://issues.apache.org/jira/browse/MYFACES-2458 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.0-alpha-2 Reporter: Curtiss Howard Priority: Minor There are a couple minor AJAX-related bugs: * h:commandButton needs to append return false; for onclick when a behavior chain is present. * if f:ajax disabled=true, the AJAX call is still emitted. * Possible issue with f:ajax execute=multiple ids. Seems the javax.faces.partial.execute request param may differ from Sun RI. * Unable to restore StateHolder when listener is specified for f:ajax. * f:ajax onevent not being handled. * f:ajax onerror not being handled. * f:ajax render=@all not working correctly. * f:ajax render=@form not working correctly. * f:ajax render=@this not working correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Result (was: [VOTE] release for myfaces site skin v 1)
Hi Thanks to all people who vote. We have 6 +1 Gerhard Petracek Jakob Korherr Mark Struberg Jan-Kees van Andel Matthias Wessendorf Leonardo Uribe so we can continue with the necessary steps to release myfaces site skin v 1. best regards, Leonardo Uribe
