September 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMREST-49) String response not rendered by @ResponseTemplate

by Jozef Hartinger (JIRA)

String response not rendered by @ResponseTemplate ------------------------------------------------- Key: SEAMREST-49 URL: https://issues.jboss.org/browse/SEAMREST-49 Project: Seam REST Issue Type: Bug Components: Templating Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger {code:JAVA} @Path("string") @GET @Produces("text/plain") @ResponseTemplate("/string.ftl") public String string() { return "Jozef"; } {code} won't be rendered. "Jozef" is returned instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[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

12 years, 11 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

12 years, 11 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

12 years, 11 months

3
3
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

12 years, 12 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

12 years, 12 months

7
10
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

12 years, 12 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing

by Arsen Torbarina (JIRA)

HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing -------------------------------------------------------------------------------- Key: JBSEAM-4454 URL: https://jira.jboss.org/jira/browse/JBSEAM-4454 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1 Reporter: Arsen Torbarina Fix For: 2.2.1.CR1 Method org.jboss.seam.persistence.PersistenceProvider.init() (including its subclass' method HibernatePersistenceProvider.init()) never gets executed, because it is annotated with @org.jboss.seam.annotations.intercept.PostConstruct instead of @javax.ejb.PostConstruct. -- 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

12 years, 12 months

5
11
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-18) @Transactional not inherited in larger hierarchies

by Stephan Pabinger (JIRA)

@Transactional not inherited in larger hierarchies -------------------------------------------------- Key: SEAMPERSIST-18 URL: https://issues.jboss.org/browse/SEAMPERSIST-18 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.Beta2 Environment: JBoss 6.0.0.Final, Seam Persistence 3.0.0.Beta2 Reporter: Stephan Pabinger I am using the following hierarchy: ClassA (abstract) inherited by ClassB (abstract) inherited by ClassC ClassA - injects a Seam-Managed Persistence Context as described in (http://docs.jboss.org/seam/3/persistence/latest/reference/en-US/html/pers...) - performs em.joinTransaction() in a method that is annotated with @Transactional ClassB - just extends ClassA (nothing added) ClassC - extends ClassB - is annotated with @Named When I call #{classC.joinTransaction} I get the following exception: [1]. When inheriting ClassC directly from ClassA the method is called just fine. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-185) Add support for activating beans based on the JSF project stage

by Christian Kaltepoth (JIRA)

Add support for activating beans based on the JSF project stage --------------------------------------------------------------- Key: SEAMFACES-185 URL: https://issues.jboss.org/browse/SEAMFACES-185 Project: Seam Faces Issue Type: Feature Request Affects Versions: 3.0.2 Reporter: Christian Kaltepoth Hey all, I think it would be a great enhancement if Seam Faces could support activation of beans only in specific JSF project stages. MyFaces CODI supports a similar feature with the {{@ProjectStageActivated}} annotation. Examples: {code} @ProductionStage @ApplicationScoped public class ProductionEntityManagerProducer { ... } @DevelopmentStage @ApplicationScoped public class DevelopmentEntityManagerProducer { ... } {code} Another very interesting usecase would be to enable specific interceptors/decorators only in development stage. This could be used for debugging stuff that is only interesting during development. I think this could be easily implenented using an CDI extension that vetos beans that do not match the active project stage. The only problem I'm seeing is that we will need the JSF project stage in an very early stage during application startup (actually before JSF started up). This means that we would have to determine the project stage JSF will use ourselves. The JSF spec describes that the project stage can either be set with a servlet context parameter or using JNDI. If the latter one is uses, we could simply do a JNDI lookup in the extension. No problem here. If the developer uses a servlet context parameter the situation will become more problematic, because we will need a reference to the ServletContext in the extension. What do you think of this feature? Would it be useful? Any further ideas for the implementation? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

7
20
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2011