I am using jBPM4. I haven't found anything in the javadoc api that will allow
me to place an execution in a specific node.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257094#4257094
Reply to the post :
I am working on a project to refactor a custom built workflow process (simple
POJO design with state design pattern) to use jbpm. The one issue that I am
concerned with is how to handle current processes that are not in a final state
and that will need to be integrated into jbpm. I want to
I'm using seam 1.2.1. The ManagedEntityIdentityInterceptor does not appear to
work when a SFSB maintains a list of managed entities.
After, the SFSB is passivated and activated, each entity in my list is no
longer managed.
View the original post :
It seems to me that the benefits of a extended persistence context with a
stateful session bean are lost when having to deal with the issue of a sfsb
being passivated by the container. If a sfsb has a reference to a managed
entity, the sfsb is passivated, and then the sfsb is activated, you may
I have a stateful session bean that uses an extended persistent context and is
annotated with @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED).
In a transactional action method annotated with
@TransactionAttribute(TransactionAttributeType.REQUIRED), I perform business
level
Yes, I want to prevent flushing of the persistence context. I will give
Seam-managed PC a try.
But this raises another question. I am leaning towards keeping all entities
objects contained in sfsbs rather than outjecting them into the conversation
scope. If the sfsb is passivated, will the
I am experiencing a similar problem. I am using the same environment except for
facelets. I am testing a JSP page.
This code is causing an exception when the action is fired
a4j:support event=onclick action=#{myaction.execute}
reRender=mylist /
Caused
This is against 2.0.0.BETA.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062769#4062769
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4062769
___
jboss-user mailing list
I am trying to decide on the best way to use an extended persistent context
with seam.
Does anyone know if an entity will remain attached to an extended persistence
context in a stateful session bean when the session bean has been passivated
and later activated?
Also, if a sfsb outjects a
Does anyone know if an entity will remain attached to an extended persistence
context in a stateful session bean when the session bean has been passivated
and later activated?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4060917#4060917
Reply to the post
I am testing the seam remoting feature on JBOSS 4.2 with seam 1.2.1 ga. I have
a bean with bijection annotations that use el expressions to inject the proper
object. I get the following error when a remote method is called.:
Caused by:
11 matches
Mail list logo