February 2012 - seam-issues - Jboss List Archives

[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] (JBSEAM-4856) AS7 Multi-war ear Seam 2.2.2.Final fails deployment (race condition?)

by Todd Sproule (Created) (JIRA)

AS7 Multi-war ear Seam 2.2.2.Final fails deployment (race condition?) --------------------------------------------------------------------- Key: JBSEAM-4856 URL: https://issues.jboss.org/browse/JBSEAM-4856 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.2.2.Final Environment: Ubuntu 11.10, Sun Java 1.6.0_26-b03, JBoss AS7 7.0.1.Final Reporter: Todd Sproule Deployment of a multi-war Seam ear into AS7 causes a deployment exception with duplicate component exception. This is easy to reproduce with any AS7 Seam ear and two wars. 16:19:13,605 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/seam-hello1]] (MSC service thread 1-3) Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml) at org.jboss.seam.core.Init.checkDuplicateFactoryExpressions(Init.java:227) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:220) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.core.Init.addFactoryValueExpression(Init.java:283) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.init.Initialization.installComponents(Initialization.java:1152) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.init.Initialization.init(Initialization.java:737) [jboss-seam-2.2.2.Final.jar:] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam-2.2.2.Final.jar:] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3821) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] -- 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

11 years, 9 months

5
22
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: (SEAMSECURITY-86) Scheme setting for pages in @ViewConfig

by Bill Elliot (JIRA)

Scheme setting for pages in @ViewConfig --------------------------------------- Key: SEAMSECURITY-86 URL: https://issues.jboss.org/browse/SEAMSECURITY-86 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Bill Elliot Is there a way in Seam 3 to do like in the Page definitions of Seam 2 to specify the Scheme (HTTP/HTTPS) to use for a specific page? I need to be able to place the login and password changing screens into HTTPS for increased security and best practices. This could likely be done in the Pages definition under a @ViewConfig. Possibly adding a new annotation @Scheme("HTTPS"). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

4
5
0 / 0

[JBoss JIRA] (SEAMINTL-70) Document usage of BundleTemplateMessage/TemplateMessage

by Gerald Turner (Created) (JIRA)

Document usage of BundleTemplateMessage/TemplateMessage ------------------------------------------------------- Key: SEAMINTL-70 URL: https://issues.jboss.org/browse/SEAMINTL-70 Project: Seam International Issue Type: Feature Request Components: Messages Affects Versions: 3.1.0.Beta3 Reporter: Gerald Turner Assignee: Ken Finnigan Priority: Optional As a user, the current documentation is sufficient for severity+text messages, however on closer inspection of the Message class, I see that detail and targets properties are available, much like FacesMessage. I dug around the seam-international source and experimented with a bean having fields/method like the following: @Inject private Messages messages; @Inject private transient TemplateMessage message; public void doSometing() { messages.add(message.level(Level.WARN).text("Text {0}, {1}, {2}").textParams('a', 'b', 'c').detail("Detail {0}, {1}, {2}").detailParams(1, 2, 3).targets("message").build()); messages.add(message.level(Level.FATAL).text("Fatality!").targets("message").build()); } This works. A few caveats: * TemplateMessage field has to be marked transient, otherwise get WELD error during deployment about Serializable bean having non-Serializable field. * Make sure to call add(Message) signature (invoke build()) instead of add(MessageBuilder), otherwise only the most recent message is added. * doSomething method is not reentrant/thread-safe because of the builder. I'd prefer to use Messages instead of the builders, perhaps have a methods like info(String text, String details, String targets, Object... args), however that gets ugly with the varargs, having to cast Object[], etc. Perhaps I should stick with FacesMessages. -- 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

11 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (SEAMINTL-58) XML Config of Supported Locales

by Ken Finnigan (JIRA)

XML Config of Supported Locales ------------------------------- Key: SEAMINTL-58 URL: https://issues.jboss.org/browse/SEAMINTL-58 Project: Seam International Issue Type: Task Components: Locales Affects Versions: 3.0.0.Final Reporter: Ken Finnigan Assignee: Ken Finnigan Priority: Minor Go through forum post -> http://seamframework.org/Community/DefaultLocaleWithSeamIntenational#comm... to see if the supported locales can be configured easier and cleaner -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-41) Messages cannot be used in TransactionPhase.AFTER_SUCCESS

by Jozef Hartinger (JIRA)

Messages cannot be used in TransactionPhase.AFTER_SUCCESS --------------------------------------------------------- Key: SEAMINTL-41 URL: https://issues.jboss.org/browse/SEAMINTL-41 Project: Seam International Issue Type: Bug Components: Messages Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Assignee: Ken Finnigan Fix For: 3.1.0.Alpha1 I am using the Seam Booking example (https://github.com/seam/examples/tree/3.0.0.Final) After a booking is made successfully, a message similar to "You're booked to stay at the Marriott Courtyard 5 days from now. " is supposed to be displayed on the web page. The message is set in an observer method. https://github.com/seam/examples/blob/3.0.0.Final/booking/src/main/java/o... Unfortunatelly, the message is never displayed. When the event is observed during TransactionPhase.IN_PROGRESS (i.e. public void onBookingComplete(@Observes @Confirmed final Booking booking)) , the message is displayed as expected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

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

[JBoss JIRA] Created: (SEAMINTL-65) Update Seam Config usage

by Ken Finnigan (JIRA)

Update Seam Config usage ------------------------ Key: SEAMINTL-65 URL: https://issues.jboss.org/browse/SEAMINTL-65 Project: Seam International Issue Type: Task Affects Versions: 3.0.0.Final Reporter: Ken Finnigan Assignee: Ken Finnigan Update the integration tests and documentation on how to use Seam Config for the module. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMINTL-61) Default Type Safe Messages to use App Locale

by Ken Finnigan (JIRA)

Default Type Safe Messages to use App Locale -------------------------------------------- Key: SEAMINTL-61 URL: https://issues.jboss.org/browse/SEAMINTL-61 Project: Seam International Issue Type: Enhancement Components: Locales, Messages Reporter: Ken Finnigan Assignee: Ken Finnigan Figure out way to auto set locale on messages to default to app locale to ensure correct message bundle is retrieved. Can't set jdk locale as that would impact other apps on server -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2012