October 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3759) Quartz example intermittent test suite failures

by Jay Balunas (JIRA)

Quartz example intermittent test suite failures ----------------------------------------------- Key: JBSEAM-3759 URL: https://jira.jboss.org/jira/browse/JBSEAM-3759 Project: Seam Issue Type: Bug Components: Examples, Test Harness Affects Versions: 2.1.1.CR1 Reporter: Jay Balunas Priority: Minor Fix For: 2.1.1.GA The quartz example unit tests fail intermittently. Since this is a timing test I am assuming there are times when the events are not fired as expected do to various system reasons. I have seen this in both hudson runs, and on my machine. Other users have also seen this. Usually just rerunning the tests solve the issue. Here is a sample build where the error has occurred: http://hudson.qa.jboss.com/hudson/job/Seam-trunk-JDK6/552/testReport/(roo... -- 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

11 years, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (JBSEAM-4703) Migrate Seam DVDStore to the new Hibernate Search 3.2 APIs

by Emmanuel Bernard (JIRA)

Migrate Seam DVDStore to the new Hibernate Search 3.2 APIs ---------------------------------------------------------- Key: JBSEAM-4703 URL: https://jira.jboss.org/browse/JBSEAM-4703 Project: Seam Issue Type: Feature Request Reporter: Emmanuel Bernard Fix For: 3.0.0.BETA1 IndexerAction could use the massive indexer -- 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

11 years, 9 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4391) Need to add transaction propagation types to @Transactional

by asookazian (JIRA)

Need to add transaction propagation types to @Transactional ----------------------------------------------------------- Key: JBSEAM-4391 URL: https://jira.jboss.org/jira/browse/JBSEAM-4391 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.2.0.GA Environment: N/A Reporter: asookazian The current tx propagation types for use with @Transactional are the following: REQUIRED, MANDATORY, SUPPORTS, NEVER; Here is a comment from the TransactionalPropagationType enum class: * Transaction propagation strategies for Seam JavaBean components. Note that unlike EJB3 components, there are no strategies for suspending transactions. Please add REQUIRES_NEW and NOT_SUPPORTED. I am unable to solve my functional requirement of calling a webservice which inserts into remote db (which does not require a tx) and inserting into multiple local db tables (requires tx) using JavaBean components and Seam @Transactional. The requirement is that even if the webservice call fails, the local db inserts should continue and succeed (i.e. no atomicity, no rollback). There is an action method in my JavaBean Seam component that is invoked from a commandButton in JSF page. Then there are two private methods that are invoked from that public method. One requires tx support, the other does not. With EJB3, I would simply use NOT_SUPPORTED for one and REQUIRES_NEW for the other. Now using JavaBeans and @Transactional, I cannot solve my problem in terms of tx support requirements. @Transactional only works on public methods. I tried recalling the component's private method (now refactored to public with @Transactional) using Component.getInstance("foo"); but that did not work. Spring has robust tx support like EJB 3. Seam needs to be ramped up in terms of tx support for JavaBean components. References: http://www.seamframework.org/Community/TransactionalPropagationTypes http://www.seamframework.org/Community/TransactionalOnPrivateMethod -- 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

11 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4512) BPM task does not rollback

by Jason E (JIRA)

BPM task does not rollback -------------------------- Key: JBSEAM-4512 URL: https://jira.jboss.org/jira/browse/JBSEAM-4512 Project: Seam Issue Type: Bug Components: BPM Affects Versions: 2.2.0.GA Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2 Reporter: Jason E I have made a simple change to the ShipAction.java class in the dvdstore example that ships with Seam. Here is the change //@EndTask public String ship() { order.ship(track); TaskInstance ti = ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId()); taskInstance.end(); if(true) throw new RuntimeException("TESTING"); return "admin"; } I commented out the end task annotation and I am ending the task via the TaskInstance API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e. updating the tracking number) rolls back. The problem is that the task instance change (i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in another db transaction. This seems like a bug since I would expect the ending of my task to also rollback. This seems like the desired behavior. This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so it should be easy to reproduce. Thanks! Jason -- 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

11 years, 9 months

7
18
0 / 0

[JBoss JIRA] Created: (SEAMINTL-7) Rewrite Messages API along the lines of JBoss Logging 3

by Ken Finnigan (JIRA)

Rewrite Messages API along the lines of JBoss Logging 3 ------------------------------------------------------- Key: SEAMINTL-7 URL: https://jira.jboss.org/browse/SEAMINTL-7 Project: Seam i18n Issue Type: Feature Request Components: Messages Affects Versions: 3.0.0.Alpha1 Reporter: Ken Finnigan Fix For: 3.0.0.Alpha2 Rewrite messages API along the lines of JBoss Logging 3 to be consistent with the logging approach once the switch from slf4j is made to JBoss Logging 3. -- 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

11 years, 10 months

7
37
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2764) Factory method does not create objects properly

by Bogdan Minciu (JIRA)

Factory method does not create objects properly ----------------------------------------------- Key: JBSEAM-2764 URL: http://jira.jboss.com/jira/browse/JBSEAM-2764 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.0.1.GA Reporter: Bogdan Minciu Hello, It seems that my @Factory method is recognizing the created objects only in its command block. I have this class: @Stateful @Name("xtw") @Scope(ScopeType.SESSION) @AutoCreate public class XTextSessionWrapper implements LocalXTextSessionWrapper { ... @In(required=false, create=true) @Out private XLanguage activeLanguage; public String getText(String identifier) { log.info("getText(1): identifier= #0, activeLanguage= #1", identifier, getActiveLanguage()); XTextEntry xte = xTextEntryDAO.findXTextEntry(identifier, getActiveLanguage()); log.info("getText(2): identifier= #0, activeLanguage= #1", identifier, getActiveLanguage()); xte.getXtext(); } @Factory(value="activeLanguage", autoCreate=true) public void initActiveLanguage() { XLanguage xl = xLanguageDAO.findXLanguageByIdentifier("ro"); log.info("initActiveLanguage(1): activeLanguage initialized to #0", xl.getIdentifier()); setActiveLanguage(xl); log.info("initActiveLanguage(1): activeLanguage initialized to #0", getActiveLanguage().getIdentifier()); } public XLanguage getActiveLanguage() { return activeLanguage; } public void setActiveLanguage(XLanguage activeLanguage) { this.activeLanguage = activeLanguage; } ... } And i am calling the getText() method. The method calling is as expected: 1. the injected activeLanguage is detecting that it has a null value, 2. the initActiveLanguage() factory method is called 3. then the getText() method is continuing its execution. But, the problem is that when the application exists the @Factory method block, the created objects: activeLanguage is lost and reported again as null. Here is the output: 12:43:48,203 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,203 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,703 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,703 INFO [XTextSessionWrapper] initActiveLanguage(1): activeLanguage initialized to ro 12:43:48,703 INFO [XTextSessionWrapper] getText(1): identifier= com.brit.xcms.cms.Category.12.name, activeLanguage= null 12:43:49,234 INFO [XTextSessionWrapper] getText(2): identifier= com.brit.xcms.cms.Category.12.name, activeLanguage= null Where did I went wrong? Why is the activeLanguage factoried value lost when i leave the initActiveLanguage() method? -- 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

11 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMREST-1) Support validating @FormParams, @QueryParams, @Headers, etc

by Jozef Hartinger (JIRA)

Support validating @FormParams, @QueryParams, @Headers, etc ----------------------------------------------------------- Key: SEAMREST-1 URL: https://jira.jboss.org/browse/SEAMREST-1 Project: Seam RESTEasy Issue Type: Feature Request Components: Bean Validation Reporter: Jozef Hartinger Currently, only message body parameters and @Form objects are validated. Provide support for validating @*Param parameters as well. -- 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

11 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (SEAMXML-19) Seam XML tests should be more fine grained

by Stuart Douglas (JIRA)

Seam XML tests should be more fine grained ------------------------------------------ Key: SEAMXML-19 URL: https://jira.jboss.org/browse/SEAMXML-19 Project: Seam XML Bean Config Issue Type: Bug Affects Versions: 3.0.0.Alpha2 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 3.0.0.Beta1 -- 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

11 years, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4070) Remove restriction that seam-debug.jar must be loaded by the same classloader as jsf-facelets.jar

by Stuart Douglas (JIRA)

Remove restriction that seam-debug.jar must be loaded by the same classloader as jsf-facelets.jar ------------------------------------------------------------------------------------------------- Key: JBSEAM-4070 URL: https://jira.jboss.org/jira/browse/JBSEAM-4070 Project: Seam Issue Type: Patch Reporter: Stuart Douglas Attachments: statewriter-patch.diff If seam-debug.jar and jsf-facelets.jar are not in the same classloader a redirect loop occurs when the debug page is displayed. I have changed the StateWriterControl class to use reflection to access StateWriter. This also mean the StateWriterControl can be moved out of com.sun.facelets and into an org.jboss.seam package. -- 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

11 years, 11 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4185) ViewExpiredException is printed in the log even if i set log="false"

by Adrian Mitev (JIRA)

ViewExpiredException is printed in the log even if i set log="false" -------------------------------------------------------------------- Key: JBSEAM-4185 URL: https://jira.jboss.org/jira/browse/JBSEAM-4185 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.2.CR1 Reporter: Adrian Mitev Attachments: exception.txt See exception.txt for the stacktrace. This is what i have in pages.xml <exception class="javax.faces.application.ViewExpiredException" log="false"> <redirect view-id="/common/error.xhtml"> <message>#{messages.sessionTimeout}</message> </redirect> </exception> and the redirect is performed but i still see the exception in the log -- 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

11 years, 12 months

5
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2010