|
|
Re: Help for creating stardust standalone engine [message #1602975 is a reply to message #1590987] |
Thu, 05 February 2015 23:12 |
|
Hi Manu,
Stardust 2.1.0 also contains a first version of what is supposed to become an official framework for bootstrapping a Stardust engine as port of your functional tests. The artifact is called "stardust-engine-test" and it allows you to include the bootstrapping of an IPP Spring context in your JUnit tests via rule annotations, for example:
@ClassRule
public static final TestClassSetup testClassSetup = new TestClassSetup(new UsernamePasswordPair("motu", "motu"), ForkingServiceMode.JMS, "MyModel");
As I said, Stardust 2.1.0 contains a very early version of this and we're going to add documentation and more functionality in the next Stardust release, but if you're interested, this is the dependency:
<dependency>
<groupId>org.eclipse.stardust.engine</groupId>
<artifactId>stardust-engine-test</artifactId>
</dependency>
|
|
|
|
|
|
Re: Help for creating stardust standalone engine [message #1607889 is a reply to message #1607883] |
Mon, 09 February 2015 06:05 |
|
Hi,
OK. So we're not talking about the use case inside a test case anymore. You're looking for a way to start a process instance ... but I'm still not sure about the exact requirements.
When you say "custom task listener in activity", what do you mean? When you have a task / activity instance then a process instance must already exist.
Do you intend to start another process instance while the user is working on a task? Or do you need to correlate an external event to complete an activity and then drive the process forward?
Jan
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04929 seconds