[jBPM] New message: "Re: Problem Signaling a Waiting Execution"
by Andy Barreras
User development,
A new message was posted in the thread "Problem Signaling a Waiting Execution":
http://community.jboss.org/message/521530#521530
Author : Andy Barreras
Profile : http://community.jboss.org/people/FlyNavy
Message:
--------------------------------------------------------------
Santanu, -- Thank you for all of your advice. I finally got it working! Looks like the advice you gave me worked out. I created a simple Java app that:
1. Created an instance of the ProcessEngine
2. Deployed the ProcessDefinition
3. Performed external work
4. Signalled the execution to advance to the next node when the external work was done.
So here's another question. Is there any way to deploy this app programatically to the jBPM console app so that I can demo the workflow utilizing the built-in functionality of the jBPM console app?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521530#521530
16 years, 3 months
[jBPM] New message: "Re: Problem Signaling a Waiting Execution"
by Andy Barreras
User development,
A new message was posted in the thread "Problem Signaling a Waiting Execution":
http://community.jboss.org/message/521529#521529
Author : Andy Barreras
Profile : http://community.jboss.org/people/FlyNavy
Message:
--------------------------------------------------------------
Ronald, -- Thank you for all of your advice. I finally got it working! Looks like the advice you gave me worked out. I created a simple Java app that:
1. Created an instance of the ProcessEngine
2. Deployed the ProcessDefinition
3. Performed external work
4. Signalled the execution to advance to the next node when the external work was done.
So here's another question. Is there any way to deploy this app programatically to the jBPM console app so that I can demo the workflow utilizing the built-in functionality of the jBPM console app?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521529#521529
16 years, 3 months
[JNDI and Naming] New message: "Name lookup fails, reason unknown"
by Timothy Mowlem
User development,
A new message was posted in the thread "Name lookup fails, reason unknown":
http://community.jboss.org/message/521522#521522
Author : Timothy Mowlem
Profile : http://community.jboss.org/people/jvm
Message:
--------------------------------------------------------------
Hello,
I am a beginner with JBoss and J2EE. I am trying to get an app running from our source tree. I have JBoss 4.0.5 running okay. I have built and deployed the EAR successfully (I can see console and log messages to that effect and it appears in the JMX console).
The app uses EJB3 annotations and has no ejb-jar.xml
According to the JBoss docs (for v4.4 - don't know if things were different for 4.0.5) a remote client looks up a bean using the name:
"myapp/MyBean/remote"
where:
"myapp.ear" is the name of the deployed EAR file
"MyBean" is the name of the bean class as deployed in the EAR
"remote" is added for a remote call from a client
I am seeing:
javax.naming.NameNotFoundException: myapp not bound
I am feeding in the jndi properties via my own properties file which contains the following naming related parameters:
# Naming service parameters
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=jnp://localhost:1099
Please can anyone deduce the problem in this case?
Thank you.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521522#521522
16 years, 3 months
[JBoss Microcontainer] New message: "Re: Undemanding Dependencies"
by Adrian Brock
User development,
A new message was posted in the thread "Undemanding Dependencies":
http://community.jboss.org/message/521519#521519
Author : Adrian Brock
Profile : http://community.jboss.org/people/adrian@jboss.org
Message:
--------------------------------------------------------------
I would say it should just be like any other circular dependency:
<bean name="A" mode="On Demand">
<property name="b"><inject bean="B" /></property>
<bean>
<bean name="B" mode="On Demand">
<demand targetState="Instantiated">A</demand>
</bean>
i.e. starting B triggers starting A which then gets injected with B.
However, the AbstractDemandMetaData$DemandDependencyItem
overrides resolve(Controller) and doesn't include the
enableOnDemand() processing.
So it won't work, although I think it should?
This alternative should work although it looks a bit funny/backwards. ;-)
<bean name="A" mode="On Demand"/>
<bean name="B" mode="On Demand">
<install bean="A" method="setB">
<parameter><this/></parameter>
</install>
</bean>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/521519#521519
16 years, 3 months