July 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: persist() / remove() at end of long running conversation

by fjalvingh

Ok; and part 2: AbstractSaveEventListener calls saveWithGeneratedId() with requiresImmediateIdAccess == false (which is good). It then generates an identifier which in my case comes from a sequence; it generates a Long. After that it defaults into a call to: | return performSave( entity, generatedId, persister, false, anything, source, true ); | which causes requiresImmediateIdAccess in the lower calls to be true. I think the code should replace true with requiresImmediateIdAccess as the key *was* generated OK without an insert needed.. I tested that and it fixed the problem. Sadly enough it broke my patch for HHH-2588 so I'll have to look into that some more. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064390#4064390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064390

19 years

1
0
0 / 0

[JBoss jBPM] - Re: JBPM - concurrent process execution fails

by estaub

"kukeltje" wrote : Ed, | | Will putting an async=true on the node realy force a commit? That has to be documented well then (rollback | 's further on in the process a rollback will not be possible then) This is not a problem if the process has to wait for the return value of the async message node. | Ronald, Take a look at Node.enter(): anonymous wrote : // execute the node | if (isAsync) { | ExecuteNodeJob job = createAsyncContinuationJob(token); | MessageService messageService = (MessageService) Services.getCurrentService(Services.SERVICENAME_MESSAGE); | messageService.send(job); | token.lock(job.toString()); | } else { | execute(executionContext); | } | | So yeah, I think it leads to a commit. Unfortunately, as efip10 found out, there's a race condition between the commit and the new job. -Ed Staub View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064389#4064389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064389

19 years

1
0
0 / 0

[JBoss Seam] - Re: persist() / remove() at end of long running conversation

by fjalvingh

I seem to have the same problem. I'm running seam 2.0.0b1 with hibernate 3.2.3, hbem 3.3.1 in JPA mode without EJB (Tomcat native). I have a method as follows: | @Transactional(TransactionPropagationType.REQUIRED) | @Begin(flushMode=FlushModeType.MANUAL) | public String createNewTarget() { | System.out.println("method entered (fm=manual we hope)"); | m_target = new Target(); | m_target.setTargetSourceList(new ArrayList<TargetSourceModule>()); | | m_target.setKey("akey"); | m_target.setName("Name"); | System.out.println("method before persist()"); | m_daoBuilder.save(m_target); | System.out.println("method after persist()"); | return "newtarget"; | } | and when this gets called Hibernate immediately inserts the record: | 01:26:41,964 DEBUG [SeamPhaseListener] before phase: INVOKE_APPLICATION 5 | method entered (fm=manual we hope) | method before persist() | Hibernate: select nextval ('ab_target_sq') | *** fix: shouldDelayetc=false, fm=AUTO, ria=true | Hibernate: insert into ab_target (tgt_autoDiscover, tgt_key, tgt_name, tgt_repository_version, tgtid) values (?, ?, ?, ?, ?) | method after persist() | 01:27:03,786 DEBUG [Manager] Beginning long-running conversation | The ***fix line is displayed around the fix you proposed. As you can see flushmode is manual and requireimmediateresult is true. I have debugged thru Seam and found one very odd thing though- the @Begin annotation seems to set the flushmode etc after the method is invoked, not before! It is done in ConversationInterceptor.aroundInvoke; the pertinent code is: | Object result = invocation.proceed(); | beginConversationIfNecessary(method, result); | endConversationIfNecessary(method, result); | return result; | The call to "beginConversation" sets the flush mode, but after the deed has been done. I don't yet know if this is the cause of the problem but having the annotation "start" after the method call seems weird to me to say the least. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064388#4064388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064388

19 years

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: display application instead mamagement server

by jaikiran

Add a jboss-web.xml file, in the WEB-INF folder of your application, containing the following: jboss-web.xml: | <?xml version="1.0" encoding="UTF-8"?> | <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.2//EN" "http://www.jboss.org/j2ee/dtd/jboss-web.dtd"> | | <jboss-web> | <context-root>/</context-root> | </jboss-web> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064386#4064386 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064386

19 years

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - display application instead mamagement server

by huseyin

Hi, how can i display the application i deployed, instead the management console at web page http://localhost:8080 Tomcat used to have appbase option. Does Jboss have anything to support this feature? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064382#4064382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064382

19 years

1
0
0 / 0

[JBoss Seam] - Re: @DataModel(scope=CONVERSATION) banned, why?

by dan.j.allen

I believe it has to do with the fact that a DataModel is either attached to the scope of the owning component or it is placed in PAGE context when used on a stateless component. The restriction has to do with how Seam maintains the row selection. It isn't meant to be tossed out into the great wide open. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064381#4064381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064381

19 years

1
0
0 / 0

[JBoss Seam] - Re: support for multiple scopes in @In, who's with me?

by dan.j.allen

The semantics of how it searches a given scope would remain the same as it is today. Meaning, if you put scope = ScopeType.CONVERSATION, then it will just do Component.getInstance("value", ScopeType.CONVERSATION). This patch just let's you work multiple scopes, but the lookup is still the same. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064380#4064380 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064380

19 years

1
0
0 / 0

[JBoss Seam] - Re: support for multiple scopes in @In, who's with me?

by ellenzhao

sorry, i meant "Thanks!" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064379#4064379 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064379

19 years

1
0
0 / 0

[JBoss Seam] - Re: support for multiple scopes in @In, who's with me?

by ellenzhao

How about the nested conversation? Does it search from the innerst conversation? Thanks? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064378#4064378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064378

19 years

1
0
0 / 0

[JBoss Seam] - Re: support for multiple scopes in @In, who's with me?

by dan.j.allen

I now have a patch if anyone is interested. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064377#4064377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064377

19 years

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 July 2007