[jira] [Created] (MYFACES-3244) ContentTypeList does not contain a supported content type: text/css
ContentTypeList does not contain a supported content type: text/css --- Key: MYFACES-3244 URL: https://issues.apache.org/jira/browse/MYFACES-3244 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.7 Reporter: Gurkan Erdogdu Priority: Blocker I have switched from 2.0.6 to 2.0.7 and I get the following exception when I clicked action button, Jul 27, 2011 12:30:10 PM org.apache.catalina.core.StandardWrapperValve invoke java.lang.IllegalArgumentException: ContentTypeList does not contain a supported content type: text/css at org.apache.myfaces.shared_impl.renderkit.html.HtmlRendererUtils.selectContentType(HtmlRendererUtils.java:1928) at org.apache.myfaces.renderkit.html.HtmlRenderKitImpl.createResponseWriter(HtmlRenderKitImpl.java:223) at org.ajax4jsf.resource.TemplateCSSRenderer.send(TemplateCSSRenderer.java:85) at org.ajax4jsf.resource.InternetResourceBase.send(InternetResourceBase.java:374) at org.ajax4jsf.resource.ResourceLifecycle.sendResource(ResourceLifecycle.java:221) at org.ajax4jsf.resource.ResourceLifecycle.send(ResourceLifecycle.java:148) at org.ajax4jsf.resource.InternetResourceService.load(InternetResourceService.java:335) at org.ajax4jsf.cache.LRUMapCache.load(LRUMapCache.java:116) at org.ajax4jsf.cache.LRUMapCache.get(LRUMapCache.java:87) at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:195) at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at siwpas.mechsoft.com.tr.integration.EJBSecurityValve.invoke(EJBSecurityValve.java:75) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:851) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:278) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:300) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) This problem has not seen in MyFaces 2.0.6 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-3006) FacesContext current instance is null in managed bean action method for Tomcat 7
[
https://issues.apache.org/jira/browse/MYFACES-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997680#comment-12997680
]
Gurkan Erdogdu commented on MYFACES-3006:
-
OK, you can close the issue. 7.0.8 has no problem.
FacesContext current instance is null in managed bean action method for
Tomcat 7
Key: MYFACES-3006
URL: https://issues.apache.org/jira/browse/MYFACES-3006
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Gurkan Erdogdu
Assignee: Leonardo Uribe
Hello,
Actually I am not sure that this is an error related with MyFaces.
In a managed bean action method, I have stopped an application Tomcat
Context(not same with the current JSF application).
public String stopContext(){
FacesContext.getCurrentInsatnce() -- It is ok, faces context is not null
Context context = get Tomcat application context;
//Stop tomcat context
context.stop(); -- This is any application on Tomcat, not same with
current JSF application
FacesContext.getCurrentInstance() -- Problem, it is NULL
}
I think that Tomcat clear current JSF application thread locals. But I ask to
stop other application context, therefore it must not destroy current
application thread locals.
What do you think?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-3035) PostConstruct method is called before properties are injected on Tomcat 7
[ https://issues.apache.org/jira/browse/MYFACES-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996540#comment-12996540 ] Gurkan Erdogdu commented on MYFACES-3035: - Tomcat7AnnotationLifecycleProvider calls Tomcat 7 Instancemanager for creation of MB instance and injection of annotations. Because Tomcat7 InstanceManager does not understand to inject @ManagedProperty this field is null. You can write your own instance manager. PostConstruct method is called before properties are injected on Tomcat 7 -- Key: MYFACES-3035 URL: https://issues.apache.org/jira/browse/MYFACES-3035 Project: MyFaces Core Issue Type: Bug Environment: Tomcat 7.0.8, MyFaces 2.0.3 Reporter: Nick Belaevski Attachments: myfaces-3035.zip Deploy attached project (use 'myfaces' profile only) under Tomcat 7 and open index.jsf. Inspect console output, Bean.init() should print injected list contents, however on Tomcat 7 it prints null. Tomcat 6 works as expected -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MYFACES-3040) @PreDestroy Has Called 2 times
@PreDestroy Has Called 2 times -- Key: MYFACES-3040 URL: https://issues.apache.org/jira/browse/MYFACES-3040 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.3 Reporter: Gurkan Erdogdu When session is invalidated, session scoped bean @PreDestroy method has called two times - When StartupServletcontextListener # sessionDestroyed - When StartupServletcontextListener # attributeRemoved -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MYFACES-3040) @PreDestroy Has Called 2 times
[ https://issues.apache.org/jira/browse/MYFACES-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992452#comment-12992452 ] Gurkan Erdogdu commented on MYFACES-3040: - Yes. @PreDestroy Has Called 2 times -- Key: MYFACES-3040 URL: https://issues.apache.org/jira/browse/MYFACES-3040 Project: MyFaces Core Issue Type: Bug Components: JSR-314 Affects Versions: 2.0.3 Reporter: Gurkan Erdogdu When session is invalidated, session scoped bean @PreDestroy method has called two times - When StartupServletcontextListener # sessionDestroyed - When StartupServletcontextListener # attributeRemoved -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MYFACES-3006) FacesContext current instance is null in managed bean action method for Tomcat 7
[
https://issues.apache.org/jira/browse/MYFACES-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu reopened MYFACES-3006:
-
Indicated above.
FacesContext current instance is null in managed bean action method for
Tomcat 7
Key: MYFACES-3006
URL: https://issues.apache.org/jira/browse/MYFACES-3006
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Gurkan Erdogdu
Assignee: Leonardo Uribe
Hello,
Actually I am not sure that this is an error related with MyFaces.
In a managed bean action method, I have stopped an application Tomcat
Context(not same with the current JSF application).
public String stopContext(){
FacesContext.getCurrentInsatnce() -- It is ok, faces context is not null
Context context = get Tomcat application context;
//Stop tomcat context
context.stop(); -- This is any application on Tomcat, not same with
current JSF application
FacesContext.getCurrentInstance() -- Problem, it is NULL
}
I think that Tomcat clear current JSF application thread locals. But I ask to
stop other application context, therefore it must not destroy current
application thread locals.
What do you think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-3006) FacesContext current instance is null in managed bean action method for Tomcat 7
[
https://issues.apache.org/jira/browse/MYFACES-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980595#action_12980595
]
Gurkan Erdogdu commented on MYFACES-3006:
-
As I indicated in the code, I am closing another non-JSF application context,
not current running JSF application context. Therefore, your observation is not
correct
FacesContext current instance is null in managed bean action method for
Tomcat 7
Key: MYFACES-3006
URL: https://issues.apache.org/jira/browse/MYFACES-3006
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Gurkan Erdogdu
Assignee: Leonardo Uribe
Hello,
Actually I am not sure that this is an error related with MyFaces.
In a managed bean action method, I have stopped an application Tomcat
Context(not same with the current JSF application).
public String stopContext(){
FacesContext.getCurrentInsatnce() -- It is ok, faces context is not null
Context context = get Tomcat application context;
//Stop tomcat context
context.stop(); -- This is any application on Tomcat, not same with
current JSF application
FacesContext.getCurrentInstance() -- Problem, it is NULL
}
I think that Tomcat clear current JSF application thread locals. But I ask to
stop other application context, therefore it must not destroy current
application thread locals.
What do you think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-3006) FacesContext current instance is null in managed bean action method for Tomcat 7
[
https://issues.apache.org/jira/browse/MYFACES-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980598#action_12980598
]
Gurkan Erdogdu commented on MYFACES-3006:
-
Another observation is that, when I execute context.stop() in another thread,
there is no problem. Therefore, problem lies on ThreadLocal clearing within
Myfaces or probably on Tomcat side.
FacesContext current instance is null in managed bean action method for
Tomcat 7
Key: MYFACES-3006
URL: https://issues.apache.org/jira/browse/MYFACES-3006
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Gurkan Erdogdu
Assignee: Leonardo Uribe
Hello,
Actually I am not sure that this is an error related with MyFaces.
In a managed bean action method, I have stopped an application Tomcat
Context(not same with the current JSF application).
public String stopContext(){
FacesContext.getCurrentInsatnce() -- It is ok, faces context is not null
Context context = get Tomcat application context;
//Stop tomcat context
context.stop(); -- This is any application on Tomcat, not same with
current JSF application
FacesContext.getCurrentInstance() -- Problem, it is NULL
}
I think that Tomcat clear current JSF application thread locals. But I ask to
stop other application context, therefore it must not destroy current
application thread locals.
What do you think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-3006) FacesContext current instance is null in managed bean action method for Tomcat 7
FacesContext current instance is null in managed bean action method for Tomcat 7
Key: MYFACES-3006
URL: https://issues.apache.org/jira/browse/MYFACES-3006
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Gurkan Erdogdu
Hello,
Actually I am not sure that this is an error related with MyFaces.
In a managed bean action method, I have stopped an application Tomcat
Context(not same with the current JSF application).
public String stopContext(){
FacesContext.getCurrentInsatnce() -- It is ok, faces context is not null
Context context = get Tomcat application context;
//Stop tomcat context
context.stop(); -- This is any application on Tomcat, not same with
current JSF application
FacesContext.getCurrentInstance() -- Problem, it is NULL
}
I think that Tomcat clear current JSF application thread locals. But I ask to
stop other application context, therefore it must not destroy current
application thread locals.
What do you think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2999) Using XML Comment in HTML Panel Grid
Using XML Comment in HTML Panel Grid Key: MYFACES-2999 URL: https://issues.apache.org/jira/browse/MYFACES-2999 Project: MyFaces Core Issue Type: Bug Components: JSR-252 Affects Versions: 2.0.2 Reporter: Gurkan Erdogdu When using !-- Some comment -- in a panelGrid tag, panelGrid is not rendered correctly. For example, h:panelGrid columns=2 !-- Some comment -- h:outputText ./ h:outputText / /h:panelGrid Above code has not rendered correctly! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support
LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support -- Key: MYFACES-2919 URL: https://issues.apache.org/jira/browse/MYFACES-2919 Project: MyFaces Core Issue Type: Bug Reporter: Gurkan Erdogdu Patch content -- 1- ResourceAnnotationLifecycleProvider : It does not check super class for annotations. It must examine super classes. This is specificed in Java EE 6 specification, EE 5.2.5 Annotations and Injections. 2- TomcatAnnotationLifecycleProvider : isAvailable Method must catch Throwable and ignore them. Otherwise, it throws error/s that are not catched and calling code is not able to process other lifecycle providers. 3- StartupServletContextListener : Early initiliazation of lifecycle provider. Otherwise, it is not possible to use META-INF/services providers. 4- pom.xml : Adding Tomcat 7 libs. 5- Tomcat7AnnotationLifecycleProvider : Tomcat 7 based LifeCycleProvider implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support
[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gurkan Erdogdu updated MYFACES-2919: Status: Patch Available (was: Open) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support -- Key: MYFACES-2919 URL: https://issues.apache.org/jira/browse/MYFACES-2919 Project: MyFaces Core Issue Type: Bug Reporter: Gurkan Erdogdu Patch content -- 1- ResourceAnnotationLifecycleProvider : It does not check super class for annotations. It must examine super classes. This is specificed in Java EE 6 specification, EE 5.2.5 Annotations and Injections. 2- TomcatAnnotationLifecycleProvider : isAvailable Method must catch Throwable and ignore them. Otherwise, it throws error/s that are not catched and calling code is not able to process other lifecycle providers. 3- StartupServletContextListener : Early initiliazation of lifecycle provider. Otherwise, it is not possible to use META-INF/services providers. 4- pom.xml : Adding Tomcat 7 libs. 5- Tomcat7AnnotationLifecycleProvider : Tomcat 7 based LifeCycleProvider implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2919) LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support
[ https://issues.apache.org/jira/browse/MYFACES-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909401#action_12909401 ] Gurkan Erdogdu commented on MYFACES-2919: - Thanks Jakob, go for it, patch is looking good. LifecycleProvider Based Problems and Tomcat7 LifeCycleProvider Support -- Key: MYFACES-2919 URL: https://issues.apache.org/jira/browse/MYFACES-2919 Project: MyFaces Core Issue Type: Bug Reporter: Gurkan Erdogdu Assignee: Jakob Korherr Attachments: MYFACES-2919-2.patch, patch.txt Patch content -- 1- ResourceAnnotationLifecycleProvider : It does not check super class for annotations. It must examine super classes. This is specificed in Java EE 6 specification, EE 5.2.5 Annotations and Injections. 2- TomcatAnnotationLifecycleProvider : isAvailable Method must catch Throwable and ignore them. Otherwise, it throws error/s that are not catched and calling code is not able to process other lifecycle providers. 3- StartupServletContextListener : Early initiliazation of lifecycle provider. Otherwise, it is not possible to use META-INF/services providers. 4- pom.xml : Adding Tomcat 7 libs. 5- Tomcat7AnnotationLifecycleProvider : Tomcat 7 based LifeCycleProvider implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2912) Wrong JNDI Name for Method Resource Injections
Wrong JNDI Name for Method Resource Injections -- Key: MYFACES-2912 URL: https://issues.apache.org/jira/browse/MYFACES-2912 Project: MyFaces Core Issue Type: Bug Reporter: Gurkan Erdogdu Attachments: patch.txt Method based JNDI env. injections not worked correctly. Patch is attached. See Java EE 6 specification section, EE. 5.2.5 Annotations and Injections. Patch is provided that solves problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2884) Getting error after switching 2.0.0 to 2.0.1
Getting error after switching 2.0.0 to 2.0.1
Key: MYFACES-2884
URL: https://issues.apache.org/jira/browse/MYFACES-2884
Project: MyFaces Core
Issue Type: Bug
Reporter: Gurkan Erdogdu
After switching to 2.0.1, getting following exceptions while accessing JSF page
Aug 17, 2010 4:41:41 PM org.apache.myfaces.renderkit.ErrorPageWriter
handleThrowable
SEVERE: An exception occurred
javax.faces.application.ViewExpiredException: /counter.jsfNo saved view state
could be found for the view identifier: /counter.jsf
at
org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:128)
at
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
Code is
html xmlns=http://www.w3.org/1999/xhtml;
xmlns:h=http://java.sun.com/jsf/html;
h:head
titleJSF2 Ajax with OpenWebBeans Demo/title
/h:head
h:body
h3JSF2 Ajax Demo :: Click bCount/b button to inrease your
count/h3
h:form id=form
h:outputScript name=jsf.js library=javax.faces
target=body/h:outputScript
div
h:commandButton id=button1 value=Count...
actionListener=#{helloBean.processAction}
onclick=jsf.ajax.request(this,event,
{execute:'form:button1',render:'form:status'});return false;
/h:commandButton
/div
div
h:outputText value=Counter Number : /
h:outputText value=#{helloBean.count} id=status /
/div
/h:form
/h:body
/html
Full source code is here!
http://siwpas.googlecode.com/svn/trunk/samples/hellojsf2/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2884) Getting error after switching 2.0.0 to 2.0.1
[
https://issues.apache.org/jira/browse/MYFACES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899420#action_12899420
]
Gurkan Erdogdu commented on MYFACES-2884:
-
Problem is related with myfaces-ext val project modules. Using
myfaces-extval-bean-validation-1.2.3.jar
myfaces-extval-property-validation-1.2.3.jar
myfaces-extval-core-1.2.3.jar
with 2.0.1 throws aferomentioned exception.
Getting error after switching 2.0.0 to 2.0.1
Key: MYFACES-2884
URL: https://issues.apache.org/jira/browse/MYFACES-2884
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Gurkan Erdogdu
After switching to 2.0.1, getting following exceptions while accessing JSF
page
Aug 17, 2010 4:41:41 PM org.apache.myfaces.renderkit.ErrorPageWriter
handleThrowable
SEVERE: An exception occurred
javax.faces.application.ViewExpiredException: /counter.jsfNo saved view state
could be found for the view identifier: /counter.jsf
at
org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:128)
at
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
Code is
html xmlns=http://www.w3.org/1999/xhtml;
xmlns:h=http://java.sun.com/jsf/html;
h:head
titleJSF2 Ajax with OpenWebBeans Demo/title
/h:head
h:body
h3JSF2 Ajax Demo :: Click bCount/b button to inrease your
count/h3
h:form id=form
h:outputScript name=jsf.js library=javax.faces
target=body/h:outputScript
div
h:commandButton id=button1 value=Count...
actionListener=#{helloBean.processAction}
onclick=jsf.ajax.request(this,event,
{execute:'form:button1',render:'form:status'});return false;
/h:commandButton
/div
div
h:outputText value=Counter Number : /
h:outputText value=#{helloBean.count} id=status /
/div
/h:form
/h:body
/html
Full source code is here!
http://siwpas.googlecode.com/svn/trunk/samples/hellojsf2/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2884) Getting error after switching 2.0.0 to 2.0.1
[
https://issues.apache.org/jira/browse/MYFACES-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899735#action_12899735
]
Gurkan Erdogdu commented on MYFACES-2884:
-
Without ext-val components, it works with 2.0.1. Problem seems on ext-val
components.
Getting error after switching 2.0.0 to 2.0.1
Key: MYFACES-2884
URL: https://issues.apache.org/jira/browse/MYFACES-2884
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 2.0.1
Reporter: Gurkan Erdogdu
After switching to 2.0.1, getting following exceptions while accessing JSF
page
Aug 17, 2010 4:41:41 PM org.apache.myfaces.renderkit.ErrorPageWriter
handleThrowable
SEVERE: An exception occurred
javax.faces.application.ViewExpiredException: /counter.jsfNo saved view state
could be found for the view identifier: /counter.jsf
at
org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:128)
at
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171)
at
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:189)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
Code is
html xmlns=http://www.w3.org/1999/xhtml;
xmlns:h=http://java.sun.com/jsf/html;
h:head
titleJSF2 Ajax with OpenWebBeans Demo/title
/h:head
h:body
h3JSF2 Ajax Demo :: Click bCount/b button to inrease your
count/h3
h:form id=form
h:outputScript name=jsf.js library=javax.faces
target=body/h:outputScript
div
h:commandButton id=button1 value=Count...
actionListener=#{helloBean.processAction}
onclick=jsf.ajax.request(this,event,
{execute:'form:button1',render:'form:status'});return false;
/h:commandButton
/div
div
h:outputText value=Counter Number : /
h:outputText value=#{helloBean.count} id=status /
/div
/h:form
/h:body
/html
Full source code is here!
http://siwpas.googlecode.com/svn/trunk/samples/hellojsf2/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2791) render view params not working for EL expressions
render view params not working for EL expressions
-
Key: MYFACES-2791
URL: https://issues.apache.org/jira/browse/MYFACES-2791
Project: MyFaces Core
Issue Type: Bug
Reporter: Gurkan Erdogdu
navigation-case
from-action#{blog.addBlog}/from-action
if#{true}/if
to-view-id/view.xhtml/to-view-id
redirect
view-param
nameid/name
value#{blog.idm}/value
/view-param
/redirect
/navigation-case
@ManagedBean(name=blog)
@SessionScoped
public class Blog {
private String content;
private static AtomicInteger id = new AtomicInteger(0);
private String idm;
public static AtomicInteger getId() {
return id;
}
public static void setId(AtomicInteger id) {
Blog.id = id;
}
public String getIdm() {
return idm;
}
public void setIdm(String idm) {
this.idm = idm;
}
public String addBlog(){
this.idm = Integer.toString(id.incrementAndGet());
return null;
}
public String getContent() {
return content;
}
public void setContent(String content) {
this.content = content;
}
}
Produces http://localhost:8080/session_1_blog/view.jsf?id=%23{blog.idm}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACES-2792) Redirect with include-view-params in faces-config.xml
Redirect with include-view-params in faces-config.xml
-
Key: MYFACES-2792
URL: https://issues.apache.org/jira/browse/MYFACES-2792
Project: MyFaces Core
Issue Type: Bug
Reporter: Gurkan Erdogdu
I have a bean
@ManagedBean(name=blog)
@SessionScoped
public class Blog {
private String content;
private static AtomicInteger id = new AtomicInteger(0);
private String idm;
public String addBlog(){
this.idm = Integer.toString(id.incrementAndGet());
return view?faces-redirect=trueamp;includeViewParams=true;
}
}
This is result view
h:body
f:view
f:metadata
f:viewParam name=id
value=#{blog.idm}/f:viewParam
/f:metadata
/f:view
h:outputText value=#{blog.content}/h:outputText
/h:body
This works! Changed to following and adding faces-config.xml
public String addBlog(){
this.idm = Integer.toString(id.incrementAndGet());
return ok;
}
navigation-rule
navigation-case
from-action#{blog.addBlog}/from-action
from-outcomeok/from-outcome
to-view-id/view.xhtml/to-view-id
redirect include-view-params=true/
/navigation-case
/navigation-rule
Not working!
What can be the problem? (I think doing some wrong actions!)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (EXTCDI-4) transactional annotation
[ https://issues.apache.org/jira/browse/EXTCDI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847040#action_12847040 ] Gurkan Erdogdu commented on EXTCDI-4: - Problem is that EntityManagerProducer defines disposal method that has an InjectionPoint parameter. According to the spec, If a bean that declares any scope other than @Dependent has an injection point of type InjectionPoint and qualifier @Default, the container automatically detects the problem and treats it as a definition error. In our implementation, we treat disposal methods InjectionPoint#getBean as a Managed Bean i.ie EntityManagerProducer and it has not scoped as @Dependent. Therefore it throws Exception. transactional annotation Key: EXTCDI-4 URL: https://issues.apache.org/jira/browse/EXTCDI-4 Project: MyFaces CODI Issue Type: New Feature Reporter: Gerhard Petracek Attachments: EntityManagerProducer.java, PersistenceContext.java, Transactional.java, TransactionHandler.java @Transactional should act like the equivalent spring annotation and it should be compatible with every custom cdi-scope. @TransactionAttribute should be supported as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
