December 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4667) Using JSF 2 And Seam - conversation Id

by varun shaji (JIRA)

Using JSF 2 And Seam - conversation Id -------------------------------------- Key: JBSEAM-4667 URL: https://jira.jboss.org/browse/JBSEAM-4667 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR1 Environment: JBoss-6.0 M2 , Seam 2.2.0 & Seam 2.2.1 CR1, JSF 2(Mojarro - 2.0.2) Reporter: varun shaji During Postback from a JSF page , the conversation id cannot be retored. The debug logs that i obtained for JSF 1.2 and JSF 2.0 are as shown for the same postback in a pageflow are as shown JSF 1.2 ******************************************************************************************************************** 06-15@23:18:50 (JbpmContextInfo.java:145) DEBUG - creating jbpm context with service factories '[]' 06-15@23:18:50 (JbpmContext.java:124) DEBUG - creating org.jbpm.JbpmContext@7b3555 06-15@23:18:50 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello 06-15@23:18:50 (GraphElement.java:170) DEBUG - event 'process-start' on 'ProcessDefinition(hello)' for 'Token(/)' 06-15@23:18:50 (JbpmContext.java:133) DEBUG - closing jbpmContext org.jbpm.JbpmContext@7b3555 ******************************************************************************************************* JSF 2.0 ********************************************************************************************** 06-15@22:38:27 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello ********************************************************************************************** I debuged and found the FacesPage from which the conversation Id is returning..Is returning null in JSF2 ..ConversationId is returning null in FacesPage returned by Seam when Using JSF2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3020) Links to seam and gsg of jbosstools

by Svetlana mukhina (JIRA)

Links to seam and gsg of jbosstools ----------------------------------- Key: JBSEAM-3020 URL: http://jira.jboss.com/jira/browse/JBSEAM-3020 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Svetlana mukhina Assigned To: Michael Yuan Priority: Optional Looking through the guide http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/index.html I've found a chapter http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/gettingstartedwi... that overlapping with some of our guides - http://docs.jboss.org/tools/2.1.0.CR1/en/seam/publish/en-US/html/index.html and http://docs.jboss.org/tools/2.1.0.CR1/en/GettingStartedGuide/publish/en-U..., maybe it will be good to add links in the chapter referring to these 2 guides where a user could find more information on the topic? -- 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, 2 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3971) Documentation to run under Websphere should contain information about Websphere 6.1 and Websphere 7.0

by Julien Kronegg (JIRA)

Documentation to run under Websphere should contain information about Websphere 6.1 and Websphere 7.0 ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3971 URL: https://jira.jboss.org/jira/browse/JBSEAM-3971 Project: Seam Issue Type: Feature Request Components: Documentation Issues Environment: Trunk documentation http://fisheye.jboss.org/browse/Seam/trunk/doc/Seam_Reference_Guide/en-US... Reporter: Julien Kronegg Priority: Minor Until Seam 2.1.1.GA, the documentation gives information about running examples under Websphere 6.1: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/websphere.html In the latest version (future 2.1.2.GA?), the documentation gives information about running examples under Websphere 7.0. The (valuable) documentation about running under WAS 6.1 is gone. It would be cool to add a sentence such as: "Information about other Websphere version can be found in previous Seam release documentation: - [Websphere 6.1=>http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/websphere.html]" This has the advantage to give useful information to Websphere users without having to much documentation content to add/rewrite. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] (SEAMJCR-22) Seam JCR Documentation issues and comments

by Marek Schmidt (Created) (JIRA)

Seam JCR Documentation issues and comments ------------------------------------------ Key: SEAMJCR-22 URL: https://issues.jboss.org/browse/SEAMJCR-22 Project: Seam JCR Issue Type: Bug Affects Versions: 3.1.0.Beta3 Reporter: Marek Schmidt Fix For: 3.1.0.Final JCR 1.2. Maven dependency configuration * "Maven user-defined property" bad link, (href instead of url attribute in docbook?) 2.1. ModeShape Integration Installation * "Please consult the ModeShape getting stated guide for exact versions. " should link to the ModeShape guide or some place to get it. 3.1. JackRabbit Integration Installation * "Please review JackRabbit documentation to determine any additional dependencies. " should link to the JackRabbit documentation. 4. Seam JCR - Event Mapping * sections 4.1. event-mapping-intro and 4.2. event-mapping-activation are empty * Description of any of the events missing 5. Seam JCR - Object Content Mapping * It is not clear to me why the API to convert nodes to objects and vice versa is using CDI events instead of an ordinary interface, it feels a bit hacky, is there any use case for having more observers? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] (SEAMSOCIAL-28) Enhance decoupling with Scribe by better controlling API class

by Antoine Sabot-Durand (Created) (JIRA)

Enhance decoupling with Scribe by better controlling API class -------------------------------------------------------------- Key: SEAMSOCIAL-28 URL: https://issues.jboss.org/browse/SEAMSOCIAL-28 Project: Seam Social Issue Type: Enhancement Components: OAuth Core Reporter: Antoine Sabot-Durand Assignee: Antoine Sabot-Durand Fix For: 3.1.0.Beta5 Scribe Library use a builder mechanism based on an API class. Today Seam Social build the name of the API class in the code. We should have a better decoupling. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMSOCIAL-4) Write tests for Seam Social

by Antoine Sabot-Durand (JIRA)

Write tests for Seam Social --------------------------- Key: SEAMSOCIAL-4 URL: https://issues.jboss.org/browse/SEAMSOCIAL-4 Project: Seam Social Issue Type: Task Affects Versions: 3.0.0.Alpha1 Reporter: Antoine Sabot-Durand Assignee: Antoine Sabot-Durand Fix For: 3.0.0.Alpha1 At the moment there are no unit test for the module, only Integration tests. We have to find a way to add unit test and mode integration test to the project -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (SEAM-30) Seam release should not depend on any SNAPSHOT artifacts

by Ondrej Skutka (JIRA)

Seam release should not depend on any SNAPSHOT artifacts -------------------------------------------------------- Key: SEAM-30 URL: https://issues.jboss.org/browse/SEAM-30 Project: Seam 3 Issue Type: Bug Components: Release tasks Affects Versions: 3.0.0.CR1 Reporter: Ondrej Skutka Tagged version of Seam 3 intended for a release should contain no -SNAPSHOT dependencies in order to have the release rebuildable in the future. Seam 3.0.0.CR1 modules contain following SNAPSHOT dependencies: solder/impl/pom.xml: org.jboss.arquillian.container:arquillian-glassfish-remote-3.1:1.0.0-SNAPSHOT catch/examples/basic-servlet/pom.xml: org.jboss.seam.catch:seam-catch-parent:3.0.0-SNAPSHOT rest/impl/pom.xml: org.jboss.arquillian.container:arquillian-glassfish-remote-3.1:1.0.0-SNAPSHOT config/docs/pom.xml: org.jboss.seam.config:seam-config-parent:3.0.0-SNAPSHOT org.jboss.seam.config:seam-config-reference-guide:3.0.0-SNAPSHOT config/dist/pom.xml: org.jboss.seam.config:seam-config-parent:3.0.0-SNAPSHOT config/examples/princess-rescue/pom.xml: org.jboss.seam.config:seam-config-parent:3.0.0-SNAPSHOT security/examples/pom.xml: org.jboss.seam.security:seam-security-parent:3.0.0-SNAPSHOT org.jboss.seam.security:seam-security-example-parent:3.0.0-SNAPSHOT -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
10
0 / 0

[JBoss JIRA] (SEAM-104) Consider adding missing examples to the distribution

by Jozef Hartinger (Created) (JIRA)

Consider adding missing examples to the distribution ---------------------------------------------------- Key: SEAM-104 URL: https://issues.jboss.org/browse/SEAM-104 Project: Seam 3 Distribution Issue Type: Task Affects Versions: 3.1.0.Beta3 Reporter: Jozef Hartinger Assignee: Shane Bryzak Fix For: 3.1.0.CR1 The following sample applications are developed as part of Seam modules but are not bundled within the Seam distribution. Please, go over them and reevaluate if the should be included or not. (I am not saying they should be, I am just making sure we do not miss anything unintentionally :-) ) * faces-viewaction * faces-viewconfig * jms-statuswatcher * mail-sendmail * security-openid-op * security-saml-idp * security-saml-sp * social-web-client * solder-princess-rescue * solder-quiz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
5
0 / 0

[JBoss JIRA] (SEAM-105) examples.txt outdated

by Jozef Hartinger (Created) (JIRA)

examples.txt outdated --------------------- Key: SEAM-105 URL: https://issues.jboss.org/browse/SEAM-105 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.1.0.Beta3 Reporter: Jozef Hartinger Assignee: Shane Bryzak Fix For: 3.1.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (SEAMREPORTS-22) Fire events in reports lifecycle

by George Gastaldi (JIRA)

Fire events in reports lifecycle ---------------------------------- Key: SEAMREPORTS-22 URL: https://issues.jboss.org/browse/SEAMREPORTS-22 Project: Seam Reports Issue Type: Feature Request Reporter: George Gastaldi Fire events when reports are - Loaded; - Filled; - Rendered. This could be useful when -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2011