May 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2993) Document wicket support

by Pete Muir (JIRA)

Document wicket support ----------------------- Key: JBSEAM-2993 URL: http://jira.jboss.com/jira/browse/JBSEAM-2993 Project: Seam Issue Type: Task Components: Documentation Issues, Wicket Affects Versions: 2.1.0.A1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Critical Fix For: 2.1.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1896) Documentation for pages.xml

by Pete Muir (JIRA)

Documentation for pages.xml --------------------------- Key: JBSEAM-1896 URL: http://jira.jboss.com/jira/browse/JBSEAM-1896 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.1.GA Documentation for pages.xml is missing in places (e.g no mention of begin-conversation element). Also, it's still (including navigation!) under the heading Events -> Page Actions which is odd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

9
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4110) Ability to use jbpm jta mode with seam

by Pete Muir (JIRA)

Ability to use jbpm jta mode with seam -------------------------------------- Key: JBSEAM-4110 URL: https://jira.jboss.org/jira/browse/JBSEAM-4110 Project: Seam Issue Type: Bug Components: BPM Reporter: Pete Muir Assignee: Pete Muir Priority: Critical Fix For: 2.1.2.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3415) Put ExceptionFilter around ContextFilter, not the other way

by Sasha Kazachonak (JIRA)

Put ExceptionFilter around ContextFilter, not the other way ----------------------------------------------------------- Key: JBSEAM-3415 URL: https://jira.jboss.org/jira/browse/JBSEAM-3415 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Reporter: Sasha Kazachonak Shouldn't ContextFilter be defined within ExceptionFilter? Now, if some non-faces servlet throws an Exception, ExceptionFilter catches it and ends all Seam contexts. And then ContextFilter tries to finish the request and throws "No application context active" type of exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2678) improve docs for conversation propagation

by Martin Trummer (JIRA)

improve docs for conversation propagation ----------------------------------------- Key: JBSEAM-2678 URL: http://jira.jboss.com/jira/browse/JBSEAM-2678 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Issues Environment: n.A. Reporter: Martin Trummer following points should be emphasized in the docs: * the fact, that ending a conversation demotes the long-running conversation to a temporary conversation should be emphasized in the docs or explained in more detail * the difference between ending a conversation and ending a conversation before-redirect should also be explained in more detail * the docs should mention, that any facesMessages are lost, when you end the conversation and use before-redirect=true (and maybe how to work around this) discussion can be found in the forum I will attach a text file with a draft, of what these improvements could be (hope this helps) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3630) Calling Renderer.render twice throws NPE in testing

by Abram Thielke (JIRA)

Calling Renderer.render twice throws NPE in testing --------------------------------------------------- Key: JBSEAM-3630 URL: https://jira.jboss.org/jira/browse/JBSEAM-3630 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.GA Environment: JDK 1.5 Reporter: Abram Thielke Assignee: Pete Muir Attachments: modified-mail-example.zip Methods in Seam 2.1.0.GA that call Renderer.render( ... ) multiple times inside the same method throws an NPE. This works fine when I deploy the app, however in testing I get the NullPointerException. I modified the mail example packaged with Seam 2.1 to call render twice from the MailExample.send method and I get the same thing: [testng] ERROR [org.jboss.seam.example.mail.MailExample] Error sending mail [testng] java.lang.NullPointerException [testng] at org.jboss.seam.ui.facelet.RendererRequest.init(RendererRequest.java:49) [testng] at org.jboss.seam.ui.facelet.RendererRequest.run(RendererRequest.java:72) [testng] at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:43) [testng] at org.jboss.seam.example.mail.MailExample.send(MailExample.java:41) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [testng] at java.lang.reflect.Method.invoke(Method.java:585) [testng] at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [testng] at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) [testng] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) [testng] at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) [testng] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [testng] at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77) [testng] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [testng] at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) [testng] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [testng] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [testng] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) [testng] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) [testng] at org.jboss.seam.example.mail.MailExample_$$_javassist_5.send(MailExample_$$_javassist_5.java) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [testng] at java.lang.reflect.Method.invoke(Method.java:585) [testng] at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329) [testng] at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:342) [testng] at org.jboss.el.parser.AstPropertySuffix.invoke(AstPropertySuffix.java:58) [testng] at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) [testng] at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [testng] at org.jboss.seam.mock.AbstractSeamTest$Request.invokeMethod(AbstractSeamTest.java:464) [testng] at org.jboss.seam.mock.AbstractSeamTest$Request.invokeAction(AbstractSeamTest.java:473) [testng] at org.jboss.seam.example.mail.test.MailTest$12.invokeApplication(MailTest.java:647) [testng] at org.jboss.seam.mock.AbstractSeamTest$Request.invokeApplicationPhase(AbstractSeamTest.java:647) [testng] at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:596) [testng] at org.jboss.seam.mock.AbstractSeamTest$Request.access$300(AbstractSeamTest.java:178) [testng] at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:498) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [testng] at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:51) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [testng] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [testng] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [testng] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [testng] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [testng] at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) [testng] at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) [testng] at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) [testng] at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) [testng] at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [testng] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) [testng] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [testng] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [testng] at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:492) [testng] at org.jboss.seam.example.mail.test.MailTest.testDoubleRender(MailTest.java:633) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [testng] at java.lang.reflect.Method.invoke(Method.java:585) [testng] at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604) [testng] at org.testng.internal.Invoker.invokeMethod(Invoker.java:470) [testng] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:564) [testng] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:830) [testng] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) [testng] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) [testng] at org.testng.TestRunner.runWorkers(TestRunner.java:678) [testng] at org.testng.TestRunner.privateRun(TestRunner.java:624) [testng] at org.testng.TestRunner.run(TestRunner.java:495) [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:300) [testng] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295) [testng] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275) [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:190) [testng] at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792) [testng] at org.testng.TestNG.runSuitesLocally(TestNG.java:765) [testng] at org.testng.TestNG.run(TestNG.java:699) [testng] at org.testng.TestNG.privateMain(TestNG.java:824) [testng] at org.testng.TestNG.main(TestNG.java:802) I'll attach the modified mail example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2717) Tomcat Integration reference guide chapter

by Jay Balunas (JIRA)

Tomcat Integration reference guide chapter ------------------------------------------ Key: JBSEAM-2717 URL: http://jira.jboss.com/jira/browse/JBSEAM-2717 Project: JBoss Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor Following the existing interop reference guide chapters create a tomcat integration chapter. This chapter will cover deployments and limitations with and without JBoss embedded. There is already some information on tomcat deployment in the reference guide but it needs to be cleaned up with this single chapter. Likely version: tomcat 6.X References: http://tomcat.apache.org/ http://techieexchange.wordpress.com/2007/11/11/rad-seam-development-with-... http://www.jroller.com/wesleyhales/entry/running_seam_2_0_on http://www.michaelyuan.com/blog/2007/07/24/seam-20-and-tomcat/ http://jira.nuxeo.org/browse/NXP-1160 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3406) Back button in nested conversations

by Pablo Caballero (JIRA)

Back button in nested conversations ----------------------------------- Key: JBSEAM-3406 URL: https://jira.jboss.org/jira/browse/JBSEAM-3406 Project: Seam Issue Type: Bug Affects Versions: 2.0.3.CR1 Environment: Linux, jboss-4.2.2.GA Reporter: Pablo Caballero Pressing the back button after closing a nested conversation does not propagate to the parent conversation and creates a new conversation. For Example (see attached example files) Start parent conversation view id first.xhtml (let say conversation Id is 2) Start nested conversation view id second.xhtml (conversation Id is 3) Close nested conversation and redirect to first.xhtml (conversation id 2) Press the back button to try to view second.xhtml. Since the nested conversation is closed and no-conversation-view-id="/first.xhtml", the view stays in first.xhtml. However, a new conversation has been created with id 5. Conversation 2 is still active but in the background. (I Tried using natural conversations, but I believe nested and natural are not supported at this time) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4060) back button in pageflow should work after a redirect

by Dan Allen (JIRA)

back button in pageflow should work after a redirect ---------------------------------------------------- Key: JBSEAM-4060 URL: https://jira.jboss.org/jira/browse/JBSEAM-4060 Project: Seam Issue Type: Feature Request Components: BPM Affects Versions: 2.1.1.GA Reporter: Dan Allen Fix For: 2.2.0.CR1 When the current page in a pageflow is validated, Seam is reference the page-scoped FacesPage. This component is only available on a faces request. Therefore, if a redirect is used in the pageflow, then it is no possible to use the back button, even if it is enabled in the pageflow definition, since the page-scope won't be available in that case. The validation should be changed to rely on information in the conversation rather than the page-scope. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4105) NullPointer exception configuring a component using a qualified XML element

by Dan Allen (JIRA)

NullPointer exception configuring a component using a qualified XML element --------------------------------------------------------------------------- Key: JBSEAM-4105 URL: https://jira.jboss.org/jira/browse/JBSEAM-4105 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.CR1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.2.GA Consider the case where there is an existing component defined with the @Name annotation. Now, you want to be able to configure that component in XML. If the class name for the component cannot be derived from the name of the component, then Seam throws a NullPointerException. Case in point. Assume the following component package com.mydomain.project; @Name("com.mydomain.project.init") public class ProjectInit { ... } Now assume I am configuring it with: <project:init stage="test"/> Because the class of the component, com.mydomain.project.ProjectInit, cannot be derived form the component name, com.mydomain.project.init, Seam tries to do something with the class object that leads to a NullPointerException. What should happen is that Seam should recognize it is configuring an existing component and ignore that fact that it cannot resolve the class. That is the intended behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2009