July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3689) No active conversation context - Exception

by Arron Ferguson (JIRA)

No active conversation context - Exception ------------------------------------------ Key: JBSEAM-3689 URL: https://jira.jboss.org/jira/browse/JBSEAM-3689 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.SP1 Environment: Ubuntu/Linux 7.10, Tomcat 6.0.16 Reporter: Arron Ferguson Bug 3369 from: https://jira.jboss.org/jira/browse/JBSEAM-3369 I don't believe this was ever fixed . Clicking on a page that requires HTTPS (e.g., http://localhost:8443/register.html) and that also requires a natural conversation results in a "javax.servlet.ServletException: No active conversation context" (HTTP Status 500) exception which is displayed to the web browser despite having exception rules in the pages.xml file (including restrict element for the page requiring restriction). Example is attached and uses HTTP to HTTPS and back again, natural conversations, facelets, and conversation scoped beans. File attached with all files (minus JAR files) required to run the example. This example has only two pages: index and register. All files (except jboss-archive-browsing.jar) are from JBoss Seam 2.1SP1 -- 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, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3641) Built-in async mechanism always returns null for Future.get()

by toto titi (JIRA)

Built-in async mechanism always returns null for Future.get() ------------------------------------------------------------- Key: JBSEAM-3641 URL: https://jira.jboss.org/jira/browse/JBSEAM-3641 Project: Seam Issue Type: Bug Components: Async Affects Versions: 2.1.0.GA, 2.0.2.SP1 Environment: Linux, JBoss 4.2.2 GA Reporter: toto titi When trying to use the built-in async mechanism, I'm unable to obtain the result of the asynchronous task using Future.get(). This always returns null. TimerServiceDispatcher seems to be installed , the asynchronous task runs perfectly. No error or misconfiguration has been seen even running in DEBUG or TRACE logging mode. Code, observations and bug are detailed here: http://www.seamframework.org/Community/AsynchronousFuturegetNull -- 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, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3458) UI control for in-page real-time viewing debug info on conversations, context contents, credentials etc

by Nicklas Karlsson (JIRA)

UI control for in-page real-time viewing debug info on conversations, context contents, credentials etc ------------------------------------------------------------------------------------------------------- Key: JBSEAM-3458 URL: https://jira.jboss.org/jira/browse/JBSEAM-3458 Project: Seam Issue Type: Feature Request Components: JSF Controls Reporter: Nicklas Karlsson Assignee: Nicklas Karlsson As discussed on the dev-list, it would be nice to have a s:debug control that would give summarized information on the state of the application -- 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, 11 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3445) s:defaultAction doesn't work for h:commandLink

by Pete Muir (JIRA)

s:defaultAction doesn't work for h:commandLink ---------------------------------------------- Key: JBSEAM-3445 URL: https://jira.jboss.org/jira/browse/JBSEAM-3445 Project: Seam Issue Type: Bug Components: JSF Controls Reporter: Pete Muir Fix For: 2.1.1.CR1 -- 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, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2519) SeamTest class does not support dependent testing

by Olivier Thierry (JIRA)

SeamTest class does not support dependent testing ------------------------------------------------- Key: JBSEAM-2519 URL: http://jira.jboss.com/jira/browse/JBSEAM-2519 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.0.1.CR1, 2.0.0.GA Environment: Seam 2.0.0.GA + TestNG 5.1 + Maven Surefire plugin Reporter: Olivier Thierry When you use dependent testing in a test class extending SeamTest, either with dependsOnGroups or dependsOnMethods, the test crash on begin phase with the following stack trace : begin(fr.myCompany.test.ServiceOrganisationTest) Time elapsed: 0.126 sec <<< FAILURE! java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:169) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:124) at org.jboss.seam.mock.BaseSeamTest.begin(BaseSeamTest.java:920) at org.jboss.seam.mock.SeamTest.begin(SeamTest.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:552) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:322) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:156) at org.testng.internal.Invoker.invokeMethod(Invoker.java:365) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:785) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:114) at org.testng.TestRunner.privateRun(TestRunner.java:693) at org.testng.TestRunner.run(TestRunner.java:574) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:241) at org.testng.SuiteRunner.run(SuiteRunner.java:145) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:901) at org.testng.TestNG.runSuitesLocally(TestNG.java:863) at org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:69) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:78) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) -- 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, 11 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2346) s:selectItems - noSelectionLabel is not hidden after first selection of a value

by Wolfgang Schwendt (JIRA)

s:selectItems - noSelectionLabel is not hidden after first selection of a value ------------------------------------------------------------------------------- Key: JBSEAM-2346 URL: http://jira.jboss.com/jira/browse/JBSEAM-2346 Project: JBoss Seam Issue Type: Bug Environment: CVS-based Seam 2.0.1 Reporter: Wolfgang Schwendt Priority: Minor <s:selectItems> offers that the user can specify an (optional) "noSelectionLabel" to be placed at the top of the selection list. It further provides a hideNoSelectionLabel option -- if this property is true, the noSelectionLabel will be hidden when a value is selected. And exactly the latter functionality has a bug, but only as far as the user's FIRST selection is concerned. When the users makes his _first_ selection and submits the form, then the noSelectionLabel is still displayed when the page is redisplayed by the server, no matter whether or not hideNoSelection was set to "true". However, when the users makes additional requests, the hideNoSelectionLabel functionality works correctly. Reason for the bug: caching behavior of org.jboss.seam.ui.component.UISelectItems.getValue() Too understand why there is a bug, consider the following scenario: A page with <h:selectOneMenu> and <s:selectItems var="myVar" label="#{myVar.name}" value="#{resultList}" noSelectionLabel="* Your choice please *" hideNoSelectionLabel="true"/> as its child component. When the user makes a selection and submits the form, the UISelectOne components checks during the "Process validations" JSF phase whether the submitted input value matches one of the available options (SelectItems). Consequently, the UISelectOne component calls the getValue() method of its org.jboss.seam.ui.component.UISelectItems child component in order to retrieve a list of SelectItem s. Then, if if validation was successful because a matching value was found, the user's selection is either written to the model (during JSF Update model phase) or if we don't make it to the Update model phase, because some other component had a validation error, the user's selection is stored in the value property of the UISelectOne component. When we finally reach the "Render response" phase and the same page should be redisplayed, the UISelectOne component gets rendered again. In order to render the selection list items, org.jboss.seam.ui.component.UISelectItems.getValue() gets called another time. But now it doesn't re-calculate its list of SelectItems. Take a look at the code: org.jboss.seam.ui.component.UISelectItems.getValue() @Override public Object getValue() { if (value == null || originalValue == null || !originalValue.equals(super.getValue())) { ... } return value; } Note that "value" is not null, because during "Process validations" org.jboss.seam.ui.component.UISelectItems.getValue() was already called which lead to value being set. Therefore, getValue() returns the OLD cached list of SelectItem s, which was calculated during Process Validations and therefore still includes the noSelectionLabel! And therefore getValue() doesn't take into account that the user made a selection and that the noSelectionLabel should now be hidden. -- 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, 11 months

9
26
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3906) Attachements are not shown in outlook

by Milos Zikic (JIRA)

Attachements are not shown in outlook ------------------------------------- Key: JBSEAM-3906 URL: https://jira.jboss.org/jira/browse/JBSEAM-3906 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1 Environment: Any Reporter: Milos Zikic Assignee: Pete Muir When sending mail with attachements, attachments are not shown in Outlook 2007. -- 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, 11 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2578) Provide support for creating bookmarks in pdf

by Terry (JIRA)

Provide support for creating bookmarks in pdf --------------------------------------------- Key: JBSEAM-2578 URL: http://jira.jboss.com/jira/browse/JBSEAM-2578 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.1.CR2 Environment: n/a Reporter: Terry Priority: Minor Fix For: 2.1.0.GA Provide support to add bookmarks in pdf generated by seam. bookmark appears as an index which when clicked jump to certain section of the page. -- 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, 11 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3776) Update release-process with cluster testing steps

by Jay Balunas (JIRA)

Update release-process with cluster testing steps ------------------------------------------------- Key: JBSEAM-3776 URL: https://jira.jboss.org/jira/browse/JBSEAM-3776 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.1.GA Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.1.2.GA We need to add some basic cluster testing steps to the release process. This is closely related to JBSEAM-3397. -- 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, 11 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3989) Map conversations to URI spaces for REST integration

by Christian Bauer (JIRA)

Map conversations to URI spaces for REST integration ---------------------------------------------------- Key: JBSEAM-3989 URL: https://jira.jboss.org/jira/browse/JBSEAM-3989 Project: Seam Issue Type: Feature Request Components: WS Reporter: Christian Bauer Some old feature idea: We'll probably have a mechanism for transporting conversation identifiers in HTTP headers. However, I'm thinking that the way this should be implemented is with explicit automatically created resources that identify a particular conversation "workspace". See Bill's blog about JMS integration and how you'd model a transaction resource RESTfully. This is the same approach just for Seam conversations. -- 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, 11 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009