[jBPM] New message: "Strategy for assigning subprocess execution ID"
by Sasa Mitrovic
User development,
A new message was posted in the thread "Strategy for assigning subprocess execution ID":
http://community.jboss.org/message/529931#529931
Author : Sasa Mitrovic
Profile : http://community.jboss.org/people/letstalk
Message:
--------------------------------------------------------------
When a subprocess is started from a main process using subprocess activity, is there a way to specifiy a strategy for assigning instance IDs to the subprocess? An example: I have a mainprocess called "MainFlow". Since I am starting this process manually, I am able to assign a process instance ID as "MainFlow.123" where 123 is my order ID. Now, when the main process starts a subprocess, it assigns an instance ID that is not derived from the main process instance ID, for instance "ContractCreate.82".
Is there a way to specifiy the strategy of assigning instance ID to subprocesses to get something like "ContractCreate.123.82" - a composite instance ID that would contain my order ID?
Thanks.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/529931#529931
16 years, 1 month
[JBoss Microcontainer Development] New message: "Re: ClassLoadingAdmin"
by Adrian Brock
User development,
A new message was posted in the thread "ClassLoadingAdmin":
http://community.jboss.org/message/529929#529929
Author : Adrian Brock
Profile : http://community.jboss.org/people/adrian@jboss.org
Message:
--------------------------------------------------------------
> emuckenhuber wrote:
>
>
> > mailto:adrian@jboss.org wrote:
> >
> > NOTE: It is still an unimplemented feature in the profile service to be able to "dry run" an install.
> > i.e. you can validate the metadata can be parsed and is complete and check all the dependencies
> > without creating the actual runtime objects.
> > Of course there might still be runtime errors thrown from the objects themselves, which this wouldn't catch.
> You mean doing mainDeployer.change(deployment, PRE_REAL) ?
No. I mean having a special copy of the kernel/deployers in the management client that doesn't do any of the callbacks for the real deployments.
So it will go through the dependency resolution, but won't invoke constructors, set properties, etc.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/529929#529929
16 years, 1 month
[JBoss Microcontainer Development] New message: "Re: ClassLoadingAdmin"
by Adrian Brock
User development,
A new message was posted in the thread "ClassLoadingAdmin":
http://community.jboss.org/message/529924#529924
Author : Adrian Brock
Profile : http://community.jboss.org/people/adrian@jboss.org
Message:
--------------------------------------------------------------
> mailto:thomas.diesler@jboss.com wrote:
>
> The use case is:
>
> From a gui select the application located at some repository to download/install into the framework.
> An application consists of potentially very many bundles.
> Try run the resolver using the application metadata.
> Only when the application can be resolved in the running framework, do the install.
>
> The worst case, which must be avoided is a partial install that fails and leaves the framework in a state where random bits are installed/resolved that cannot easily been uninstalled. Essentially, the resolve step for a set of bundles must be atomic.
You can already do that.
deploy/change(deploymentNames);
try
{
checkComplete(deploymentNames);
}
catch (IncompleteDeploymentException e)
{
undeploy/change[back](deploymentNames);
}
One of the features I added (different to what happens in 4.2.x) is that if a subdeployment ends
up in the error state then so does the rest of the application (i.e. top level deployment, subdeployments and components).
NOTE: It is still an unimplemented feature in the profile service to be able to "dry run" an install.
i.e. you can validate the metadata can be parsed and is complete and check all the dependencies
without creating the actual runtime objects.
Of course there might still be runtime errors thrown from the objects themselves, which this wouldn't catch.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/529924#529924
16 years, 1 month
[EJB 3.0] New message: "Re: Get ear name"
by Sverker Abrahamsson
User development,
A new message was posted in the thread "Get ear name":
http://community.jboss.org/message/529923#529923
Author : Sverker Abrahamsson
Profile : http://community.jboss.org/people/sverker
Message:
--------------------------------------------------------------
Unforturnatly I've seen that this method doesn't always work, e.g. from an JMX bean.
The reason why I need to get the ear name is that I have a set of modules that are used to build multiple ear files. Hence the jndi names gets different, and that is a feature, but when lookin up the jndi names from beans inside the jar I need to find out which ear is being used. I've searched for a solution but can't find anything.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/529923#529923
16 years, 1 month