January 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (SEAMFACES-233) WebXmlProjectStageDetector should use Solder's WebResourceLocator

by Christian Kaltepoth (Created) (JIRA)

WebXmlProjectStageDetector should use Solder's WebResourceLocator ----------------------------------------------------------------- Key: SEAMFACES-233 URL: https://issues.jboss.org/browse/SEAMFACES-233 Project: Seam Faces Issue Type: Enhancement Affects Versions: 3.1.0.Final Reporter: Christian Kaltepoth Priority: Minor WebXmlProjectStageDetector use some code that is able to find the location of web.xml without using the ServletContext. In the meantime this code has been moved to Solder. Therefore the old Seam Faces implementation should be removed and the WebXmlProjectStageDetector should use the new WebResourceLocator provided by Solder. I just started to work on this. I'll open a pull request soon. -- 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

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] (SEAMFACES-232) Faces initiated transaction does not rollback on RuntimeException

by Cody Lerum (Created) (JIRA)

Faces initiated transaction does not rollback on RuntimeException ----------------------------------------------------------------- Key: SEAMFACES-232 URL: https://issues.jboss.org/browse/SEAMFACES-232 Project: Seam Faces Issue Type: Bug Components: Transactions & Persistence Affects Versions: 3.1.0.Final Reporter: Cody Lerum Fix For: 3.1.0.Tracking Currently a runtime exception thrown in the Seam Faces started tx around Invoke Application will not trigger a rollback. -- 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

13 years, 2 months

4
8
0 / 0

[JBoss JIRA] (SEAMFACES-225) messages.error should prevent page navigation

by hantsy bai (Created) (JIRA)

messages.error should prevent page navigation --------------------------------------------- Key: SEAMFACES-225 URL: https://issues.jboss.org/browse/SEAMFACES-225 Project: Seam Faces Issue Type: Bug Environment: JBoss 7.0.2.Final, JBoss Seam 3.1.0.CR1 Reporter: hantsy bai Please check out my demo application and browse /tags.xhtml. 1. click the Button to create a Tag, 2. input something 3. press Create 5 I used Messages.error in the create5 method, it SHOULD prevent the page navigiation to tags.xhtml page, but it returned to the tags.xhtml page. -- 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

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] (SEAMFACES-226) Jsf VilidatorException caused a EJBRollbackException

by hantsy bai (Created) (JIRA)

Jsf VilidatorException caused a EJBRollbackException ---------------------------------------------------- Key: SEAMFACES-226 URL: https://issues.jboss.org/browse/SEAMFACES-226 Project: Seam Faces Issue Type: Bug Reporter: hantsy bai Please check out my demo application and browse /tags.xhtml. 1. click the Button to create a Tag, 2. input something 3. press Create 6 I used new ViliadtorException to throw a custom validation error in the create6 method, it SHOULD display the message in the current page, but I got EJBRollbackException in the background JBAS console, and the conversation data was discarded. -- 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

13 years, 2 months

5
13
0 / 0

[JBoss JIRA] (SEAMSPRING-10) Seam Spring Snapshot documentation

by Marek Schmidt (Created) (JIRA)

Seam Spring Snapshot documentation ---------------------------------- Key: SEAMSPRING-10 URL: https://issues.jboss.org/browse/SEAMSPRING-10 Project: Seam Spring Issue Type: Feature Request Affects Versions: 3.1.0.Final Reporter: Marek Schmidt Assignee: Shane Bryzak Fix For: 3.2.0.Alpha1 Please create the spring/snapshot/reference directory on filemgmt.jboss.org for the snapshot documentation Jenkins job. See http://hudson.qa.jboss.com/hudson/job/Seam-3.X-spring-documentation/9/con... {noformat} + rsync -r --delete --protocol=28 docs/target/docbook/publish/ seam@filemgmt.jboss.org:docs_htdocs/seam/3/spring/snapshot/reference rsync: mkdir "/docs_htdocs/seam/3/spring/snapshot/reference" failed: No such file or directory (2) rsync error: error in file IO (code 11) at main.c(509) [receiver=2.6.8] rsync: connection unexpectedly closed (8 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6] {noformat} -- 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

13 years, 2 months

1
0
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, 2 months

7
20
0 / 0

[JBoss JIRA] Created: (SEAMFACES-191) PrettyFaces cannot find ApplicationFactory

by xylocore (JIRA)

PrettyFaces cannot find ApplicationFactory ------------------------------------------ Key: SEAMFACES-191 URL: https://issues.jboss.org/browse/SEAMFACES-191 Project: Seam Faces Issue Type: Bug Components: URL Rewriting Affects Versions: 3.0.2 Environment: Windows 7, JBoss AS Head, prettyfaces-jsf2 3.3.0 Reporter: xylocore After deploying a webapp, the first access to a page throws the following exception: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804) javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306) com.ocpsoft.pretty.faces.util.FacesFactory.getApplication(FacesFactory.java:30) com.ocpsoft.pretty.faces.config.PrettyConfigListener.requestInitialized(PrettyConfigListener.java:47) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) java.lang.Thread.run(Thread.java:662) This exception is not consistent. If I restart the server, the exception may or may not occur again. I created a stripped down webapp and tested with that. The problem occurs there too. pom.xml: <?xml version="1.0" encoding="UTF-8"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <modelVersion>4.0.0</modelVersion> <groupId>a1</groupId> <artifactId>a1</artifactId> <version>1.0.0-SNAPSHOT</version> <packaging>war</packaging> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <maven.test.failure.ignore>true</maven.test.failure.ignore> <seam.faces.version>3.0.2.Final</seam.faces.version> <seam.catch.version>3.0.0.Final</seam.catch.version> </properties> <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0</artifactId> <version>1.0.0.Final</version> <type>pom</type> <scope>provided</scope> </dependency> <dependency> <groupId>org.jboss.seam.persistence</groupId> <artifactId>seam-persistence</artifactId> <version>3.0.0.Final</version> </dependency> <dependency> <groupId>org.jboss.seam.faces</groupId> <artifactId>seam-faces-api</artifactId> <version>${seam.faces.version}</version> <scope>compile</scope> </dependency> <dependency> <groupId>org.jboss.seam.faces</groupId> <artifactId>seam-faces-impl</artifactId> <version>${seam.faces.version}</version> <scope>runtime</scope> </dependency> <dependency> <groupId>org.jboss.seam.catch</groupId> <artifactId>seam-catch-api</artifactId> <version>${seam.catch.version}</version> </dependency> <dependency> <groupId>org.jboss.seam.catch</groupId> <artifactId>seam-catch-impl</artifactId> <version>${seam.catch.version}</version> <scope>runtime</scope> </dependency> <dependency> <groupId>joda-time</groupId> <artifactId>joda-time</artifactId> <version>1.6.2</version> <scope>runtime</scope> </dependency> <dependency> <groupId>com.ocpsoft</groupId> <artifactId>prettyfaces-jsf2</artifactId> <version>3.3.0</version> <scope>runtime</scope> </dependency> </dependencies> <repositories> <repository> <id>JBOSS_NEXUS</id> <url>http://repository.jboss.org/nexus/content/groups/public</url> </repository> </repositories> <build> <finalName>a1</finalName> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>2.3.2</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> </plugins> </build> </project> ViewPersonalityBean.java: package com.xylocore.ebco.web.model; import java.io.Serializable; import java.util.UUID; import javax.enterprise.context.RequestScoped; import javax.inject.Inject; import javax.inject.Named; @Named( "viewPersonality" ) @RequestScoped public class ViewPersonalityBean implements Serializable { private static final long serialVersionUID = 2493114173508560424L; private String personalityUuid; public String getPersonalityUuid() { return personalityUuid; } public void setPersonalityUuid( String aPersonalityUuid ) { personalityUuid = aPersonalityUuid; } public String getFullName() { return "Bob Johnson"; } public void loadPersonality() { } } viewPersonality: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns ="http://www.w3.org/1999/xhtml" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:s="http://jboss.org/seam/faces"> <f:view> <f:metadata> <f:viewParam name="id" value="#{viewPersonality.personalityUuid}"/> <s:viewAction action="#{viewPersonality.loadPersonality}"/> </f:metadata> <h:head> <title>Welcome</title> </h:head> <h:body> <h:form> <h3>#{viewPersonality.fullName}!</h3> </h:form> </h:body> </f:view> </html> beans.xml: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/beans_1_0.xsd"> <interceptors> <class>org.jboss.seam.transaction.TransactionInterceptor</class> </interceptors> </beans> faces-config.xml: <?xml version="1.0" encoding="UTF-8"?> <faces-config xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd" version="2.0"> </faces-config> web.xml: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="3.0" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"> <display-name>a1</display-name> <session-config> <session-timeout>30</session-timeout> </session-config> <welcome-file-list> <welcome-file>/index.html</welcome-file> </welcome-file-list> <context-param> <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name> <param-value>false</param-value> </context-param> </web-app> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMFACES-199) Transacation exception threw some time

by hantsy bai (JIRA)

Transacation exception threw some time -------------------------------------- Key: SEAMFACES-199 URL: https://issues.jboss.org/browse/SEAMFACES-199 Project: Seam Faces Issue Type: Bug Environment: java 6 update 27, Windows 7 32bit, Jboss 7.0.1.Final Reporter: hantsy bai A transaction exception threw sometime, when I browsed my homepage of my application... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFACES-45) Allow fine grained control of seam managed transactions

by Stuart Douglas (JIRA)

Allow fine grained control of seam managed transactions ------------------------------------------------------- Key: SEAMFACES-45 URL: https://jira.jboss.org/browse/SEAMFACES-45 Project: Seam Faces Issue Type: Feature Request Components: Transactions & Persistence Reporter: Stuart Douglas Seam managed transactions should be controllable on a per view basis, e.g. you should be able to turn them on for /app/crud/* and off for /app/complexpages/* Also we should look at the possibility of having a 'partially on' mode where seam only manages the transaction in the render response phase, and leaves the app to manage its own transaction for the rest of the lifecycle. -- 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

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMFACES-29) Support Seam Managed Transactions over Multiple Requests

by Lincoln Baxter III (JIRA)

Support Seam Managed Transactions over Multiple Requests -------------------------------------------------------- Key: SEAMFACES-29 URL: https://jira.jboss.org/browse/SEAMFACES-29 Project: Seam Faces Issue Type: Feature Request Components: Transactions & Persistence Reporter: Lincoln Baxter III Seam should support Managed Transactions (Java EE EntityManager, or HibernateSession) via an abstraction provided in the new persistence module. Goals: -- Allow declarative enabling/disabling of managed transactions. -- Multi-transactional JSF lifecycle, use transaction from Before Restore View to before Render Response, then another from before Render Response to after Render Response. http://docs.jboss.com/seam/2.2.0.GA/en-US/html_single/#persistence.seam-m... -- 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

13 years, 2 months

5
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2012