[jira] [Commented] (MYFACES-4114) Add disabled attribute to h:button

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094554#comment-16094554
 ] 

Dora Rajappan commented on MYFACES-4114:


This feature is in myfaces 2.3.x branch. I tested it today from portlet bridge 
also and works fine . Please close this.

> Add disabled attribute to h:button
> --
>
> Key: MYFACES-4114
> URL: https://issues.apache.org/jira/browse/MYFACES-4114
> Project: MyFaces Core
>  Issue Type: New Feature
>Reporter: Leonardo Uribe
>Assignee: Leonardo Uribe
> Attachments: myfaces-4114.patch
>
>
> Implemented, but not in HtmlOutcomeTargetButton



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4125) Response committed too early due to flush from StateWriter

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094770#comment-16094770
 ] 

Dora Rajappan commented on MYFACES-4125:


This is not getting deployed in pluto 2.0. Trying with pluto 3.0/myfaces 2.2. 
Its deployed and throws exception in mojarra2.2 with glassfish. Is mojarra 
behaviour correct? http://localhost:8080/StateWriter/error.xhtml.

 This page isn’t working

localhost redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS

> Response committed too early due to flush from StateWriter
> --
>
> Key: MYFACES-4125
> URL: https://issues.apache.org/jira/browse/MYFACES-4125
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.12
>Reporter: Eduardo Breijo
> Attachments: server.log, StateWriter.war
>
>
> We've found a problem where it seems that MyFaces is flushing output too 
> early in the RENDER_RESPONSE PHASE. As a result the response is committed 
> before we have a chance to handle an error in that phase. 
> This is because the renderView method from FaceletViewDeclarationLanguage 
> calls writer.endDocument() which ends up calling the flush() method from 
> StateWriter. This commit behavior is different between 2.0 and 2.2.  It looks 
> like a flush() was empty on 2.0, and now a call was added, which causes the 
> issue we are seeing.
> Here's a sample app:
> 1) Drive a request: localhost:9080/StateWriter/index.xhtml
> 2) You should be able to see in the logs that response was committed, so 
> redirect to error.xhtml cannot be performed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4125) Response committed too early due to flush from StateWriter

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096219#comment-16096219
 ] 

Dora Rajappan commented on MYFACES-4125:


The same State Writer flush is carried over to 2.3.x.

> Response committed too early due to flush from StateWriter
> --
>
> Key: MYFACES-4125
> URL: https://issues.apache.org/jira/browse/MYFACES-4125
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.12
>Reporter: Eduardo Breijo
> Attachments: server.log, StateWriter.war
>
>
> We've found a problem where it seems that MyFaces is flushing output too 
> early in the RENDER_RESPONSE PHASE. As a result the response is committed 
> before we have a chance to handle an error in that phase. 
> This is because the renderView method from FaceletViewDeclarationLanguage 
> calls writer.endDocument() which ends up calling the flush() method from 
> StateWriter. This commit behavior is different between 2.0 and 2.2.  It looks 
> like a flush() was empty on 2.0, and now a call was added, which causes the 
> issue we are seeing.
> Here's a sample app:
> 1) Drive a request: localhost:9080/StateWriter/index.xhtml
> 2) You should be able to see in the logs that response was committed, so 
> redirect to error.xhtml cannot be performed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4125) Response committed too early due to flush from StateWriter

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096116#comment-16096116
 ] 

Dora Rajappan commented on MYFACES-4125:


True in myfaces 2.2  drive request is not going to the error page and logs got 
in console given below.
java.lang.RuntimeException: after Render Response.
- Resonse commited = true.
Trying to resolve. Pluto3/,myfaces 2.2 StateWrite app is deployed and simulated 
this bug.
Pluto3 lib requires commons-beanutils-1.9.2, commons-collections-3.2.2, 
commons-digester-2.1,commons-logging-1.1.1 in its lib to deploy StateWriter 
with myfaces 2.2 jars.

> Response committed too early due to flush from StateWriter
> --
>
> Key: MYFACES-4125
> URL: https://issues.apache.org/jira/browse/MYFACES-4125
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.12
>Reporter: Eduardo Breijo
> Attachments: server.log, StateWriter.war
>
>
> We've found a problem where it seems that MyFaces is flushing output too 
> early in the RENDER_RESPONSE PHASE. As a result the response is committed 
> before we have a chance to handle an error in that phase. 
> This is because the renderView method from FaceletViewDeclarationLanguage 
> calls writer.endDocument() which ends up calling the flush() method from 
> StateWriter. This commit behavior is different between 2.0 and 2.2.  It looks 
> like a flush() was empty on 2.0, and now a call was added, which causes the 
> issue we are seeing.
> Here's a sample app:
> 1) Drive a request: localhost:9080/StateWriter/index.xhtml
> 2) You should be able to see in the logs that response was committed, so 
> redirect to error.xhtml cannot be performed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4125) Response committed too early due to flush from StateWriter

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096214#comment-16096214
 ] 

Dora Rajappan commented on MYFACES-4125:


I commented the flush. Ran build. All tests passed. Deployed and ran the test 
it works like mojarra.

StateWriter
 public void flush() throws IOException
{
   /* if (!this.writtenState)
{
this.out.flush();
}*/
}

Is this the solution?

> Response committed too early due to flush from StateWriter
> --
>
> Key: MYFACES-4125
> URL: https://issues.apache.org/jira/browse/MYFACES-4125
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.2.12
>Reporter: Eduardo Breijo
> Attachments: server.log, StateWriter.war
>
>
> We've found a problem where it seems that MyFaces is flushing output too 
> early in the RENDER_RESPONSE PHASE. As a result the response is committed 
> before we have a chance to handle an error in that phase. 
> This is because the renderView method from FaceletViewDeclarationLanguage 
> calls writer.endDocument() which ends up calling the flush() method from 
> StateWriter. This commit behavior is different between 2.0 and 2.2.  It looks 
> like a flush() was empty on 2.0, and now a call was added, which causes the 
> issue we are seeing.
> Here's a sample app:
> 1) Drive a request: localhost:9080/StateWriter/index.xhtml
> 2) You should be able to see in the logs that response was committed, so 
> redirect to error.xhtml cannot be performed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103055#comment-16103055
 ] 

Dora Rajappan commented on MYFACES-4127:


Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
Cannot return null from a non-dependent producer method:  Producer for Producer 
Method [Map] with qualifiers [@FlowMap @Any] declared as 
[[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped public 
org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
declared on Managed Bean [class 
org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
[@Any @Default]
at 
org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
at 
org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:184)
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:94)
at 
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
at 
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99)
at 
org.jboss.weld.proxies.Map$1822649053$Proxy$_$$_WeldClientProxy.isEmpty(Unknown 
Source)
at guess.ConfigItems.postConstruct(ConfigItems.java:29)
Got the above exception for the said scenario. Trying to resolve.

> Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
> 
>
> Key: MYFACES-4127
> URL: https://issues.apache.org/jira/browse/MYFACES-4127
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Priority: Minor
>
> When @FlowMap is injected on a RequestScoped bean, and you try to use that 
> object (which should be null since we are not inside of a flow), an 
> unexpected exception is thrown. This was noted after JIRA issue: 
> https://issues.apache.org/jira/browse/MYFACES-4126
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
> Cannot return null from a non-dependent producer method: Producer for 
> Producer Method [Map] with qualifiers [@FlowMap @Any] 
> declared as [[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped 
> public 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
> declared on Managed Bean [class 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
> [@Any @Default]
>   at 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap(ApplicationScopeObjectProducer.java:73)
>   StackTrace:
>   at 
> org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
>   at [internal classes]
>   at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>   at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>   at [internal classes]
>   at java.lang.String.valueOf(String.java:2994)
>   at java.lang.StringBuilder.append(StringBuilder.java:131)
>   at 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)
> On Mojarra 2.3, we get a different exception which looks more appropriate.
> org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active 
> contexts for scope type javax.faces.flow.FlowScoped
>   
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:623)
>   
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
>   
> org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
>   
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
>   
> org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
>   
> org.jboss.weld.util.Map$1302817811$Proxy$_$$_WeldClientProxy.toString(Unknown 
> Source)
>   java.lang.String.valueOf(String.java:2994)
>   java.lang.StringBuilder.append(StringBuilder.java:131)
>   
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103105#comment-16103105
 ] 

Dora Rajappan commented on MYFACES-4127:


Could you please put and war and source for this scenario. I am getting the 
same exception if I made the bean to @Applicationscoped also!!!

> Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
> 
>
> Key: MYFACES-4127
> URL: https://issues.apache.org/jira/browse/MYFACES-4127
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Priority: Minor
>
> When @FlowMap is injected on a RequestScoped bean, and you try to use that 
> object (which should be null since we are not inside of a flow), an 
> unexpected exception is thrown. This was noted after JIRA issue: 
> https://issues.apache.org/jira/browse/MYFACES-4126
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
> Cannot return null from a non-dependent producer method: Producer for 
> Producer Method [Map] with qualifiers [@FlowMap @Any] 
> declared as [[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped 
> public 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
> declared on Managed Bean [class 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
> [@Any @Default]
>   at 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap(ApplicationScopeObjectProducer.java:73)
>   StackTrace:
>   at 
> org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
>   at [internal classes]
>   at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>   at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>   at [internal classes]
>   at java.lang.String.valueOf(String.java:2994)
>   at java.lang.StringBuilder.append(StringBuilder.java:131)
>   at 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)
> On Mojarra 2.3, we get a different exception which looks more appropriate.
> org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active 
> contexts for scope type javax.faces.flow.FlowScoped
>   
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:623)
>   
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
>   
> org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
>   
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
>   
> org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
>   
> org.jboss.weld.util.Map$1302817811$Proxy$_$$_WeldClientProxy.toString(Unknown 
> Source)
>   java.lang.String.valueOf(String.java:2994)
>   java.lang.StringBuilder.append(StringBuilder.java:131)
>   
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4126) Implicit objects flowScope and view cannot be injected using CDI

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098290#comment-16098290
 ] 

Dora Rajappan commented on MYFACES-4126:


True. I referred to 2.2 set up in my eclipse. Its in current 2.3.x. Why was 
this moved form codi to core? 

> Implicit objects flowScope and view cannot be injected using CDI
> 
>
> Key: MYFACES-4126
> URL: https://issues.apache.org/jira/browse/MYFACES-4126
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Assignee: Eduardo Breijo
> Attachments: MYFACES-4126.patch
>
>
> The implicit objects {code:java}#{flowScope}{code} annotated @FlowMap and 
> {code:java}#{view}{code} which results in UIViewRoot cannot be injected using 
> CDI.
> For example:
> @Inject
> private UIViewRoot viewRoot;
> @Inject
> @FlowMap
> private Map flowMap;
> The above results in the following errors respectively:
> An exception occurred while starting the application ELImplicitObjectsViaCDI. 
> The exception message was: 
> com.ibm.ws.container.service.state.StateChangeException: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
> dependencies for type UIViewRoot with qualifiers @Default
>   at injection point [BackedAnnotatedField] @Inject private 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.viewRoot
> An exception occurred while starting the application ELImplicitObjectsViaCDI. 
> The exception message was: 
> com.ibm.ws.container.service.state.StateChangeException: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
> dependencies for type Map with qualifiers @FlowMap
>   at injection point [BackedAnnotatedField] @Inject @FlowMap private 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.flowMap
> A patch is provided.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4126) Implicit objects flowScope and view cannot be injected using CDI

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098215#comment-16098215
 ] 

Dora Rajappan commented on MYFACES-4126:


This bug should be opened in extensions codi? I cannot find both 
ApplicationScopeObjectProducer.java, FacesScopeObjectProducer.java in myfaces 
core.

> Implicit objects flowScope and view cannot be injected using CDI
> 
>
> Key: MYFACES-4126
> URL: https://issues.apache.org/jira/browse/MYFACES-4126
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Assignee: Eduardo Breijo
> Attachments: MYFACES-4126.patch
>
>
> The implicit objects {code:java}#{flowScope}{code} annotated @FlowMap and 
> {code:java}#{view}{code} which results in UIViewRoot cannot be injected using 
> CDI.
> For example:
> @Inject
> private UIViewRoot viewRoot;
> @Inject
> @FlowMap
> private Map flowMap;
> The above results in the following errors respectively:
> An exception occurred while starting the application ELImplicitObjectsViaCDI. 
> The exception message was: 
> com.ibm.ws.container.service.state.StateChangeException: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
> dependencies for type UIViewRoot with qualifiers @Default
>   at injection point [BackedAnnotatedField] @Inject private 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.viewRoot
> An exception occurred while starting the application ELImplicitObjectsViaCDI. 
> The exception message was: 
> com.ibm.ws.container.service.state.StateChangeException: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
> dependencies for type Map with qualifiers @FlowMap
>   at injection point [BackedAnnotatedField] @Inject @FlowMap private 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.flowMap
> A patch is provided.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4127) Unexpected exception thrown when FlowMap is injected on a RequestScoped bean

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098220#comment-16098220
 ] 

Dora Rajappan commented on MYFACES-4127:


This bug also should be opened in in myfaces extensions codi? Cant find 
ApplicationScopeObjectProducer.java in myfaces core.

> Unexpected exception thrown when FlowMap is injected on a RequestScoped bean
> 
>
> Key: MYFACES-4127
> URL: https://issues.apache.org/jira/browse/MYFACES-4127
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Priority: Minor
>
> When @FlowMap is injected on a RequestScoped bean, and you try to use that 
> object (which should be null since we are not inside of a flow), an 
> unexpected exception is thrown. This was noted after JIRA issue: 
> https://issues.apache.org/jira/browse/MYFACES-4126
> Caused by: org.jboss.weld.exceptions.IllegalProductException: WELD-52: 
> Cannot return null from a non-dependent producer method: Producer for 
> Producer Method [Map] with qualifiers [@FlowMap @Any] 
> declared as [[UnbackedAnnotatedMethod] @Produces @FlowMap @ApplicationScoped 
> public 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap()] 
> declared on Managed Bean [class 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer] with qualifiers 
> [@Any @Default]
>   at 
> org.apache.myfaces.cdi.faces.ApplicationScopeObjectProducer.getFlowMap(ApplicationScopeObjectProducer.java:73)
>   StackTrace:
>   at 
> org.jboss.weld.bean.AbstractProducerBean.checkReturnValue(AbstractProducerBean.java:136)
>   at [internal classes]
>   at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
>   at 
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
>   at [internal classes]
>   at java.lang.String.valueOf(String.java:2994)
>   at java.lang.StringBuilder.append(StringBuilder.java:131)
>   at 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)
> On Mojarra 2.3, we get a different exception which looks more appropriate.
> org.jboss.weld.contexts.ContextNotActiveException: WELD-001303: No active 
> contexts for scope type javax.faces.flow.FlowScoped
>   
> org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:623)
>   
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:89)
>   
> org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63)
>   
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:87)
>   
> org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
>   
> org.jboss.weld.util.Map$1302817811$Proxy$_$$_WeldClientProxy.toString(Unknown 
> Source)
>   java.lang.String.valueOf(String.java:2994)
>   java.lang.StringBuilder.append(StringBuilder.java:131)
>   
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.execute(ELImplicitObjectBean.java:163)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4126) Implicit objects flowScope and view cannot be injected using CDI

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098402#comment-16098402
 ] 

Dora Rajappan commented on MYFACES-4126:


Thats great then. It might some interfacing classes in core to cdi. I applied 
this patch to 2.3.x and built it and all tests passed.

> Implicit objects flowScope and view cannot be injected using CDI
> 
>
> Key: MYFACES-4126
> URL: https://issues.apache.org/jira/browse/MYFACES-4126
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Eduardo Breijo
>Assignee: Eduardo Breijo
> Attachments: MYFACES-4126.patch
>
>
> The implicit objects {code:java}#{flowScope}{code} annotated @FlowMap and 
> {code:java}#{view}{code} which results in UIViewRoot cannot be injected using 
> CDI.
> For example:
> @Inject
> private UIViewRoot viewRoot;
> @Inject
> @FlowMap
> private Map flowMap;
> The above results in the following errors respectively:
> An exception occurred while starting the application ELImplicitObjectsViaCDI. 
> The exception message was: 
> com.ibm.ws.container.service.state.StateChangeException: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
> dependencies for type UIViewRoot with qualifiers @Default
>   at injection point [BackedAnnotatedField] @Inject private 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.viewRoot
> An exception occurred while starting the application ELImplicitObjectsViaCDI. 
> The exception message was: 
> com.ibm.ws.container.service.state.StateChangeException: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied 
> dependencies for type Map with qualifiers @FlowMap
>   at injection point [BackedAnnotatedField] @Inject @FlowMap private 
> com.ibm.ws.jsf23.fat.beans.ELImplicitObjectBean.flowMap
> A patch is provided.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4131) begin and end do not look to be implemented / working

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116456#comment-16116456
 ] 

Dora Rajappan commented on MYFACES-4131:


If no one has objection I like to commit this patch.

>  begin and end do not look to be implemented / working
> --
>
> Key: MYFACES-4131
> URL: https://issues.apache.org/jira/browse/MYFACES-4131
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-372
>Affects Versions: 2.3.0-beta
>Reporter: Paul Nicolucci
> Attachments: MYFACES-4131.patch, MYFACES-4131-WITH-TEST.patch
>
>
> I started to test the  constraint feature of JSF 2.3 and it does 
> not look to function on MyFaces. 
> The changes required are for the following JSF 2.3 spec issue : 
> https://github.com/javaee/javaserverfaces-spec/issues/1102
> According to the spec the  tag will now have begin and end 
> attributes. For instance:
> 
> #{x}
> 
> In the above example if testList had 10 items in it each entry containing a 
> number 0-9 then we would expect the following output:
> 0123456789
> If we changed it to:
> 
> #{x}
> 
> We would expect the following output:
> 56789



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4131) begin and end do not look to be implemented / working

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116162#comment-16116162
 ] 

Dora Rajappan commented on MYFACES-4131:


One difference I notice while implemeting this is if offset + size is used with 
UI repeat it.(offset 0, size 10). It will print 0..9. While begin + end is used 
with UIRepeat (begin 0, end 9 )It will print 0..9. (According to Paul). So 
begin end prints including begin and  end. 

>  begin and end do not look to be implemented / working
> --
>
> Key: MYFACES-4131
> URL: https://issues.apache.org/jira/browse/MYFACES-4131
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-372
>Affects Versions: 2.3.0-beta
>Reporter: Paul Nicolucci
> Attachments: MYFACES-4131.patch
>
>
> I started to test the  constraint feature of JSF 2.3 and it does 
> not look to function on MyFaces. 
> The changes required are for the following JSF 2.3 spec issue : 
> https://github.com/javaee/javaserverfaces-spec/issues/1102
> According to the spec the  tag will now have begin and end 
> attributes. For instance:
> 
> #{x}
> 
> In the above example if testList had 10 items in it each entry containing a 
> number 0-9 then we would expect the following output:
> 0123456789
> If we changed it to:
> 
> #{x}
> 
> We would expect the following output:
> 56789



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4131) begin and end do not look to be implemented / working

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116156#comment-16116156
 ] 

Dora Rajappan commented on MYFACES-4131:


Please read this .https://github.com/javaee/javaserverfaces-spec/issues/1102.  
Here it mentions the offset is just an overriding alias for begin. 
They are same but begin is more meaningfully matching end attribute..

>  begin and end do not look to be implemented / working
> --
>
> Key: MYFACES-4131
> URL: https://issues.apache.org/jira/browse/MYFACES-4131
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: JSR-372
>Affects Versions: 2.3.0-beta
>Reporter: Paul Nicolucci
> Attachments: MYFACES-4131.patch
>
>
> I started to test the  constraint feature of JSF 2.3 and it does 
> not look to function on MyFaces. 
> The changes required are for the following JSF 2.3 spec issue : 
> https://github.com/javaee/javaserverfaces-spec/issues/1102
> According to the spec the  tag will now have begin and end 
> attributes. For instance:
> 
> #{x}
> 
> In the above example if testList had 10 items in it each entry containing a 
> number 0-9 then we would expect the following output:
> 0123456789
> If we changed it to:
> 
> #{x}
> 
> We would expect the following output:
> 56789



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly

[Dora Rajappan (JIRA)]

Dora Rajappan created MYFACES-4154:
--

 Summary: The browser (chrome) always show the previous page name 
while its on the current page rendered properly
 Key: MYFACES-4154
 URL: https://issues.apache.org/jira/browse/MYFACES-4154
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.3.0-beta
Reporter: Dora Rajappan
Priority: Minor


The browser (chrome) always show the previous page name while its on the 
current page rendered properly . This bug is already logged in jira not sure of 
the bug id. Not sure its browser problem  or jsf. Not checked this with mojarra 
also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MYFACES-4153) h:selectOneRadio when rendered inside h:panelGroup which is right aligned stands out from the group

[Dora Rajappan (JIRA)]

Dora Rajappan created MYFACES-4153:
--

 Summary: h:selectOneRadio when rendered inside h:panelGroup which 
is right aligned stands out from the group
 Key: MYFACES-4153
 URL: https://issues.apache.org/jira/browse/MYFACES-4153
 Project: MyFaces Core
  Issue Type: Bug
  Components: General
Affects Versions: 2.3.0-beta
Reporter: Dora Rajappan
Priority: Minor


h:selectOneRadio when rendered inside h:panelGroup which is right aligned 
stands out from the group towards the left since it gets rendered as html 
table. This is same behaviour for mojarra 2.2 also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4154) The browser (chrome) always show the previous page name while its on the current page rendered properly

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169963#comment-16169963
 ] 

Dora Rajappan commented on MYFACES-4154:


Mojarra also has same behaviour . Chrome shows  the previous page name while 
its at a  current page.

> The browser (chrome) always show the previous page name while its on the 
> current page rendered properly
> ---
>
> Key: MYFACES-4154
> URL: https://issues.apache.org/jira/browse/MYFACES-4154
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>Priority: Minor
>
> The browser (chrome) always show the previous page name while its on the 
> current page rendered properly . This bug is already logged in jira not sure 
> of the bug id. Not sure its browser problem  or jsf. Not checked this with 
> mojarra also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4153) h:selectOneRadio when rendered inside h:panelGroup which is right aligned stands out from the group

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170015#comment-16170015
 ] 

Dora Rajappan commented on MYFACES-4153:


I will provide the application. Its huge with ejbs etc.. So I have to find out 
how i can give that to you.
I am new to  rendering to quickly tweak a solution.

> h:selectOneRadio when rendered inside h:panelGroup which is right aligned 
> stands out from the group
> ---
>
> Key: MYFACES-4153
> URL: https://issues.apache.org/jira/browse/MYFACES-4153
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: General
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>Priority: Minor
>
> h:selectOneRadio when rendered inside h:panelGroup which is right aligned 
> stands out from the group towards the left since it gets rendered as html 
> table. This is same behaviour for mojarra 2.2 also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MYFACES-4155) For inputFile upload when multipart form is submitted the actionListener is not able to get the file.getSubmittedFileName()

[Dora Rajappan (JIRA)]

Dora Rajappan created MYFACES-4155:
--

 Summary: For inputFile upload when multipart form is submitted the 
actionListener is not able to get the file.getSubmittedFileName() 
 Key: MYFACES-4155
 URL: https://issues.apache.org/jira/browse/MYFACES-4155
 Project: MyFaces Core
  Issue Type: Bug
Reporter: Dora Rajappan


For inputFile upload when multipart form is submitted the actionListener is not 
able to get the file.getSubmittedFileName() . It throws below exception with 
myfaces while its passed with mojarra.
Class org.apache.myfaces.shared.renderkit.html.util.HttpPartWrapper can not 
access a member of class org.apache.catalina.fileupload.PartItem with modifiers 
"public"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:102)
at 
java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:296)
at 
java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:288)
at java.lang.reflect.Method.invoke(Method.java:491)
at 
org.apache.myfaces.shared.renderkit.html.util.HttpPartWrapper.getSubmittedFileName(HttpPartWrapper.java:96)
at UserBean.save(UserBean.java:595)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4153) h:selectOneRadio when rendered inside h:panelGroup which is right aligned stands out from the group

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170015#comment-16170015
 ] 

Dora Rajappan edited comment on MYFACES-4153 at 9/18/17 2:03 PM:
-

I will provide the application. Its huge with ejbs etc.. So I have to find out 
how i can give that to you.
I am new to  rendering to quickly tweak a solution.:)


was (Author: dorarajappan):
I will provide the application. Its huge with ejbs etc.. So I have to find out 
how i can give that to you.
I am new to  rendering to quickly tweak a solution.

> h:selectOneRadio when rendered inside h:panelGroup which is right aligned 
> stands out from the group
> ---
>
> Key: MYFACES-4153
> URL: https://issues.apache.org/jira/browse/MYFACES-4153
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: General
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>Priority: Minor
>
> h:selectOneRadio when rendered inside h:panelGroup which is right aligned 
> stands out from the group towards the left since it gets rendered as html 
> table. This is same behaviour for mojarra 2.2 also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

Dora Rajappan created MYFACES-4156:
--

 Summary: Myface is not showing the FacesMessage after validation 
when ValidatorException is thown.
 Key: MYFACES-4156
 URL: https://issues.apache.org/jira/browse/MYFACES-4156
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.3.0-beta
Reporter: Dora Rajappan


Myfaces 2.3 is not showing the FacesMessage after validation when 
ValidatorException is thrown. Same works with mojarra 2.2.

if (param.length() > 32) {
  FacesMessage msg = new FacesMessage("Username should 
not exceed 32");
  
  throw new ValidatorException(msg);
  }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4157) Myfaces parses commented code from xhtml and throws property not found exception

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176377#comment-16176377
 ] 

Dora Rajappan commented on MYFACES-4157:


thank you very much. I will close this then?

> Myfaces parses commented code from xhtml and throws property not found 
> exception
> 
>
> Key: MYFACES-4157
> URL: https://issues.apache.org/jira/browse/MYFACES-4157
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>Priority: Minor
>
> Myfaces parses commented code from xhtml and throws property not found 
> exception.
> Myfaces should ignore commented code.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MYFACES-4157) Myfaces parses commented code from xhtml and throws property not found exception

[Dora Rajappan (JIRA)]

Dora Rajappan created MYFACES-4157:
--

 Summary: Myfaces parses commented code from xhtml and throws 
property not found exception
 Key: MYFACES-4157
 URL: https://issues.apache.org/jira/browse/MYFACES-4157
 Project: MyFaces Core
  Issue Type: Bug
Affects Versions: 2.3.0-beta
Reporter: Dora Rajappan
Priority: Minor


Myfaces parses commented code from xhtml and throws property not found 
exception.
Myfaces should ignore commented code.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197067#comment-16197067
 ] 

Dora Rajappan commented on MYFACES-4162:


Works fine with IE and not with chrome!

> bug in the response handling if a full page is sent via ajax
> 
>
> Key: MYFACES-4162
> URL: https://issues.apache.org/jira/browse/MYFACES-4162
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Werner Punz
>Assignee: Werner Punz
>
> The example in https://issues.apache.org/jira/browse/MYFACES-4154 sends back 
> an entire page due to a page navigation triggered from an ajax call, and 
> apparently the page is inserted but the viewstate is lost along the way. I 
> need to investigate what happens for such a corner case, since triggering a 
> page change navigation from Ajax is rather seldom but needs to be addressed.
> I will need a handful of days to fix this, due to my limited time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198540#comment-16198540
 ] 

Dora Rajappan commented on MYFACES-4162:


I just checked below two are related and cause by repeated ajax calls. Only 
first ajax call one was succeeding. Subsequent calls whether to show another 
error message or navigate to a different page wasnt working. With the latest 
fix they both work very well. 
.https://issues.apache.org/jira/projects/MYFACES/issues/MYFACES-4160 
https://issues.apache.org/jira/browse/MYFACES-4162 .
4154 is purely a navigation and page name error not related to ajax. Ie after 
login page (very first page) when navigated to a new page it shows in browser 
name of the previous page while its at a current page rendered properly). 4154 
is not fixed. 4160, 4162 are fixed and works both with IE and chrome!!! Thanks 
to Werner!


> bug in the response handling if a full page is sent via ajax
> 
>
> Key: MYFACES-4162
> URL: https://issues.apache.org/jira/browse/MYFACES-4162
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Werner Punz
>Assignee: Werner Punz
>
> The example in https://issues.apache.org/jira/browse/MYFACES-4154 sends back 
> an entire page due to a page navigation triggered from an ajax call, and 
> apparently the page is inserted but the viewstate is lost along the way. I 
> need to investigate what happens for such a corner case, since triggering a 
> page change navigation from Ajax is rather seldom but needs to be addressed.
> I will need a handful of days to fix this, due to my limited time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198723#comment-16198723
 ] 

Dora Rajappan commented on MYFACES-4162:


I got the redirect flag fundamental from the mkyong example. After all its just 
a display error of browser and cant we ignore it!!! at the cost of a redirect 
for all non ajaxed navigations!!!

> bug in the response handling if a full page is sent via ajax
> 
>
> Key: MYFACES-4162
> URL: https://issues.apache.org/jira/browse/MYFACES-4162
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Werner Punz
>Assignee: Werner Punz
>
> The example in https://issues.apache.org/jira/browse/MYFACES-4154 sends back 
> an entire page due to a page navigation triggered from an ajax call, and 
> apparently the page is inserted but the viewstate is lost along the way. I 
> need to investigate what happens for such a corner case, since triggering a 
> page change navigation from Ajax is rather seldom but needs to be addressed.
> I will need a handful of days to fix this, due to my limited time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198540#comment-16198540
 ] 

Dora Rajappan edited comment on MYFACES-4162 at 10/10/17 12:01 PM:
---

I just checked below two are related and cause by repeated ajax calls. Only 
first ajax call one was succeeding. Subsequent calls whether to show another 
error message or navigate to a different page wasnt working. With the latest 
fix they both work very well. 
.https://issues.apache.org/jira/projects/MYFACES/issues/MYFACES-4160 
https://issues.apache.org/jira/browse/MYFACES-4162 .
4154 is purely a navigation and page name error not related to ajax. Ie after 
login page (very first page) when navigated to a new page it shows in browser, 
name of the previous page while its at a current page rendered properly). 4154 
is not fixed. 4160, 4162 are fixed and works both with IE and chrome!!! Thanks 
to Werner!



was (Author: dorarajappan):
I just checked below two are related and cause by repeated ajax calls. Only 
first ajax call one was succeeding. Subsequent calls whether to show another 
error message or navigate to a different page wasnt working. With the latest 
fix they both work very well. 
.https://issues.apache.org/jira/projects/MYFACES/issues/MYFACES-4160 
https://issues.apache.org/jira/browse/MYFACES-4162 .
4154 is purely a navigation and page name error not related to ajax. Ie after 
login page (very first page) when navigated to a new page it shows in browser 
name of the previous page while its at a current page rendered properly). 4154 
is not fixed. 4160, 4162 are fixed and works both with IE and chrome!!! Thanks 
to Werner!


> bug in the response handling if a full page is sent via ajax
> 
>
> Key: MYFACES-4162
> URL: https://issues.apache.org/jira/browse/MYFACES-4162
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Werner Punz
>Assignee: Werner Punz
>
> The example in https://issues.apache.org/jira/browse/MYFACES-4154 sends back 
> an entire page due to a page navigation triggered from an ajax call, and 
> apparently the page is inserted but the viewstate is lost along the way. I 
> need to investigate what happens for such a corner case, since triggering a 
> page change navigation from Ajax is rather seldom but needs to be addressed.
> I will need a handful of days to fix this, due to my limited time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4162) bug in the response handling if a full page is sent via ajax

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16198563#comment-16198563
 ] 

Dora Rajappan commented on MYFACES-4162:


Its true that both mojarra and myfaces behave same way displaying previous page 
names in browser. Yes its the urls. Guess its how things work. And 4154 can be 
closed then.

> bug in the response handling if a full page is sent via ajax
> 
>
> Key: MYFACES-4162
> URL: https://issues.apache.org/jira/browse/MYFACES-4162
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Werner Punz
>Assignee: Werner Punz
>
> The example in https://issues.apache.org/jira/browse/MYFACES-4154 sends back 
> an entire page due to a page navigation triggered from an ajax call, and 
> apparently the page is inserted but the viewstate is lost along the way. I 
> need to investigate what happens for such a corner case, since triggering a 
> page change navigation from Ajax is rather seldom but needs to be addressed.
> I will need a handful of days to fix this, due to my limited time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4153) h:selectOneRadio when rendered inside h:panelGroup which is right aligned stands out from the group

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194450#comment-16194450
 ] 

Dora Rajappan edited comment on MYFACES-4153 at 10/6/17 10:58 AM:
--

Thomas you can run this pom as it is and you will get the login page where you 
can find the alignment of selectOneRadio.


was (Author: dorarajappan):
Thomas you can run this pom as it it and you will get the login page where you 
can find the alignment of selectOneRadio.

> h:selectOneRadio when rendered inside h:panelGroup which is right aligned 
> stands out from the group
> ---
>
> Key: MYFACES-4153
> URL: https://issues.apache.org/jira/browse/MYFACES-4153
> Project: MyFaces Core
>  Issue Type: Bug
>  Components: General
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>Priority: Minor
> Attachments: login.xhtml, mf23test.zip
>
>
> h:selectOneRadio when rendered inside h:panelGroup which is right aligned 
> stands out from the group towards the left since it gets rendered as html 
> table. This is same behaviour for mojarra 2.2 also.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178819#comment-16178819
 ] 

Dora Rajappan edited comment on MYFACES-4156 at 9/25/17 12:57 PM:
--

{color:#f6c342}I used a method of the backing bean to validate the input Text 
submitted form via ajax. 
I followed your custom validator example also with ajax submit.

I got no message at client side. I got below response of view state. I have two 
forms in a page and hence submitting via ajax.



 


 
   
  
  
  

   
  
  
  
  
  
  
  {color}


was (Author: dorarajappan):
I used a method of the backing bean to validate the input Text submitted form 
via ajax. 
I followed your custom validator example also with ajax submit.

I got no message at client side. I got below response of view state. I have two 
forms in a page and hence submitting via ajax.



 


 
   
  
  
  

   
  
  
  
  
  
  
  

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MyValidator.java, UserBean.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178896#comment-16178896
 ] 

Dora Rajappan edited comment on MYFACES-4156 at 9/25/17 12:54 PM:
--

bq. 
bq.   
bq.   
bq. Still partial response not contain facesmessage!
bq. 


was (Author: dorarajappan):

  
  
Still partial response not contain facesmessage!


> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MyValidator.java, UserBean.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178896#comment-16178896
 ] 

Dora Rajappan edited comment on MYFACES-4156 at 9/25/17 12:58 PM:
--

{color:#f691b2}bq. 
bq.   
bq.   
bq. Still partial response not contain facesmessage!
bq. {color}


was (Author: dorarajappan):
bq. 
bq.   
bq.   
bq. Still partial response not contain facesmessage!
bq. 

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MyValidator.java, UserBean.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178907#comment-16178907
 ] 

Dora Rajappan edited comment on MYFACES-4156 at 9/25/17 12:56 PM:
--

{color:#59afe1} 
  
  
  
  
  
 
  
   
 
  

I missed to include it in this comment. I changed it to the way u got the 
message still for ajax its not displayed.{color}


was (Author: dorarajappan):
 
  
  
  
  
  
 
  
   
 
  

I missed to include it in this comment. I changed it to the way u got the 
message still for ajax its not displayed.

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MyValidator.java, UserBean.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178907#comment-16178907
 ] 

Dora Rajappan edited comment on MYFACES-4156 at 9/25/17 2:18 PM:
-

{color:#f691b2} 
  
  
  
  
  
 
  
   
 
  
{color}
I missed to include it in this comment. I changed it to the way u got the 
message still for ajax its not displayed.


was (Author: dorarajappan):
{color:#59afe1} 
  
  
  
  
  
 
  
   
 
  

I missed to include it in this comment. I changed it to the way u got the 
message still for ajax its not displayed.{color}

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178819#comment-16178819
 ] 

Dora Rajappan commented on MYFACES-4156:


I used a method of the backing bean to validate the input Text submitted form 
via ajax. 
I followed your custom validator example also with ajax submit.

I got no message at client side. I got below response of view state. I have two 
forms in a page and hence submitting via ajax.



 


 
   
  
  
  

   
  
  
  
  
  
  
  

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180465#comment-16180465
 ] 

Dora Rajappan commented on MYFACES-4156:


Yes now I got it. I ran your test for input and got the Facesmessage. 

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip, 
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180441#comment-16180441
 ] 

Dora Rajappan commented on MYFACES-4156:


I tried to run your example and its not getting a dependency from central.

[ERROR] Failed to execute goal 
org.eclipse.jetty:jetty-maven-plugin:9.3.17.RC0:run (default-cli) on project 
mf23test: Execution default-cli of goal 
org.eclipse.jetty:jetty-maven-plugin:9.3.17.RC0:run failed: Plugin 
org.eclipse.jetty:jetty-maven-plugin:9.3.17.RC0 or one of its dependencies 
could not be resolved: Could not transfer artifact 
org.eclipse.jdt.core.compiler:ecj:jar:4.4.2 from/to central 
(http://repo.maven.apache.org/maven2): GET request of: 
org/eclipse/jdt/core/compiler/ecj/4.4.2/ecj-4.4.2.jar from central failed: 
Premature end of Content-Length delimited message body (expected: 2310271; 
received: 101132 -> [Help 1]
[ERROR]

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip, 
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178896#comment-16178896
 ] 

Dora Rajappan commented on MYFACES-4156:



  
  
Still partial response not contain facesmessage!


> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178898#comment-16178898
 ] 

Dora Rajappan commented on MYFACES-4156:


without render works with mojarra

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178898#comment-16178898
 ] 

Dora Rajappan edited comment on MYFACES-4156 at 9/25/17 11:53 AM:
--

without render works with mojarra :)


was (Author: dorarajappan):
without render works with mojarra

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178907#comment-16178907
 ] 

Dora Rajappan commented on MYFACES-4156:


 
  
  
  
  
  
 
  
   
 
  

I missed to include it in this comment. I changed it to the way u got the 
message still for ajax its not displayed.

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4155) For inputFile upload when multipart form is submitted the actionListener is not able to get the file.getSubmittedFileName()

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178922#comment-16178922
 ] 

Dora Rajappan commented on MYFACES-4155:


Thank you very much. It works.

> For inputFile upload when multipart form is submitted the actionListener is 
> not able to get the file.getSubmittedFileName() 
> 
>
> Key: MYFACES-4155
> URL: https://issues.apache.org/jira/browse/MYFACES-4155
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
>Assignee: Thomas Andraschko
> Fix For: 2.3.0
>
>
> For inputFile upload when multipart form is submitted the actionListener is 
> not able to get the file.getSubmittedFileName() . It throws below exception 
> with myfaces while its passed with mojarra.
> Class org.apache.myfaces.shared.renderkit.html.util.HttpPartWrapper can not 
> access a member of class org.apache.catalina.fileupload.PartItem with 
> modifiers "public"
>   at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:102)
>   at 
> java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:296)
>   at 
> java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:288)
>   at java.lang.reflect.Method.invoke(Method.java:491)
>   at 
> org.apache.myfaces.shared.renderkit.html.util.HttpPartWrapper.getSubmittedFileName(HttpPartWrapper.java:96)
>   at UserBean.save(UserBean.java:595)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dora Rajappan reopened MYFACES-4156:


FacesMessage is not displayed for more than one wrong entries(eg password retry 
max 3 attempts). This scenario is replicated with the project you have provided 
as it is. FacesMessage is correctly displayed for the first wrong entry and not 
for the subsequent entries unless page is refreshed.

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip, 
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MYFACES-4156) Myface is not showing the FacesMessage after validation when ValidatorException is thown.

[Dora Rajappan (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182191#comment-16182191
 ] 

Dora Rajappan commented on MYFACES-4156:


Yes I will open another bug then. It works with mojarra. Yes partial response 
omits the h:messages.

> Myface is not showing the FacesMessage after validation when 
> ValidatorException is thown.
> -
>
> Key: MYFACES-4156
> URL: https://issues.apache.org/jira/browse/MYFACES-4156
> Project: MyFaces Core
>  Issue Type: Bug
>Affects Versions: 2.3.0-beta
>Reporter: Dora Rajappan
> Attachments: login.xhtml, MessageBean.java, mf23test.zip, 
> MyValidator.java
>
>
> Myfaces 2.3 is not showing the FacesMessage after validation when 
> ValidatorException is thrown. Same works with mojarra 2.2.
> if (param.length() > 32) {
> FacesMessage msg = new FacesMessage("Username should 
> not exceed 32");
> 
> throw new ValidatorException(msg);
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)