June 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Transaction won't commit from MDB Seam2 component

by jazir1979

http://jira.jboss.com/jira/browse/JBSEAM-1580 thank you! Daniel. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058982#4058982 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058982

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Transaction won't commit from MDB Seam2 component

by gavin.king＠jboss.com

Please report this in JIRA, it should be an easy fix. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058980#4058980 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058980

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Transaction won't commit from MDB Seam2 component

by jazir1979

Hi, I have an MDB annotated with @Name, which worked fine in 1.2.1.GA. But now, when the app server attemps to commit following a successful message, I get this... | 10:12:29,703 INFO [DownloadManager] Finished processing file: c:\download\received\2AZ3MQ_20060627134443 | 10:12:29,703 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] TwoPhaseCoordinator.beforeCompletion - failed for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@f66eac | java.lang.IllegalStateException: No application context active | at org.jboss.seam.Component.forName(Component.java:1690) | at org.jboss.seam.Component.getInstance(Component.java:1740) | at org.jboss.seam.Component.getInstance(Component.java:1735) | at org.jboss.seam.Component.getInstance(Component.java:1712) | at org.jboss.seam.Component.getInstance(Component.java:1707) | at org.jboss.seam.core.Events.instance(Events.java:154) | at org.jboss.seam.transaction.SynchronizationRegistry.beforeTransactionCompletion(SynchronizationRegistry.java:51) | at org.jboss.seam.transaction.EjbTransaction.beforeCompletion(EjbTransaction.java:43) | at org.jboss.ejb3.stateful.SessionSynchronizationInterceptor$SFSBSessionSynchronization.beforeCompletion(SessionSynchronizationInterceptor.java:71) | at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114) | at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:249) | at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88) | at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177) | at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1256) | at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) | at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) | at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.end(JmsServerSession.java:494) | at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:248) | at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) | at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743) | at java.lang.Thread.run(Thread.java:595) | The MDB is using CMT (obviously), and was using a standard @PersistenceContext. I tried changing it to inject my seam-managed PC, but the error was still the same. any ideas? Daniel. PS: sorry for all the posts, I feel I may have jumped to Seam2 Beta a bit too early, but hopefully the error reports do help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058979#4058979 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058979

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - "It is currently not recommended that this feature is used w

by fjzuser

The reference "Seam Remoting provides experimental support for JMS Messaging. This section describes the JMS support that is currently implemented, but please note that this may change in the future. It is currently not recommended that this feature is used within a production environment.",WHY? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058978#4058978 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058978

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Component with @WebRemote methods can no longer use @Req

by jazir1979

http://jira.jboss.com/jira/browse/JBSEAM-1579 Done, thanks Gavin. The workaround of splitting the component into two worked fine, and probably not many people use a combination of @WebRemote and @RequestParameter like this. We're only using it in a lookup component that's dojo-based on the client side and we'll probably retire it into something using RichFaces if we ever get the time. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058977#4058977 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058977

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Multiple WARs ind one EAR... SSO?

by gavin.king＠jboss.com

Seriously, I have not even looked at JBoss SSO. If you want to investigate this, please let us know what you learn :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058976#4058976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058976

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Understanding the difference between conversation and wo

by gavin.king＠jboss.com

A workspace is a conversation with a description :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058975#4058975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058975

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: When and where to use jBPM in Seam app ?

by gavin.king＠jboss.com

anonymous wrote : When we expose stateful bean as Seam component with scope = business process, it's persistence may be longer than session and continue across sessions/users , right ? If we don't need this object when process ends, then we don't need it to be entity bean and stay in database afterwards. We don't care how Seam/jBPM saves state in context (maybe using the same database), maps table names, fields, etc. Is it good practice to use process-wide stateful bean in such manner, or Entity bean is still recommended ? I would really strongly recommend against the use of serialized blobs in databases. For the same reason I cited above: how will this work across a system updgrade? However, with a jBPM Converter, you can sometimes persist some kind of state into jBPMs tables without the need for a binary representation, or a separate entity. Still, IMO, things that need to persist beyond a user session should usually be entities mapped to welldefined database schemas. You app will be legacy one day. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058974#4058974 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058974

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Seam2 LocaleSelector - no longer shows default-locale

by jazir1979

PS: the obvious fix worked... | <locale-config> | <default-locale>en-AU</default-locale> | <supported-locale>en-AU</supported-locale> | <supported-locale>zh-CN</supported-locale> | <supported-locale>es-BO</supported-locale> | </locale-config> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058973#4058973 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058973

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Seam2 LocaleSelector - no longer shows default-locale

by gavin.king＠jboss.com

I guess it is just a diff in the RI. I suppose you should add it to the list of supported locales. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058972#4058972 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058972

18 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2007