This should work, as there is a StructureMD check before you demand VFSDeployment:
AbstractStructuralDeployers.java
| Attachments attachments = deployment.getPredeterminedManagedObjects();
| StructureMetaData structureMetaData = attachments.getAttachment(StructureMetaData.class);
| if (structureMetaData == null)
| {
| structureMetaData = StructureMetaDataFactory.createStructureMetaData();
| try
| {
| determineStructure(deployment, structureMetaData);
|
where determineStructure() is only impled for VFS based deployments.
But since you already have StructureMD,
you should be by-passing that VFSD check.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205465#4205465
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205465
Hi
I am using jBPM 3.2.2. In processdefinition.
[img]file:///home/mansingh/LatestEclipse/workspace/websale/src/main/jpdl/processimage.jpg[/img]
I am having two transition going from one task node, named
First transition is: More info needed
Second transition is: OK
In jBPM console when i m clicking on More Info needed button then this More info needed transition is not going, instead it is choosing another transition ie OK.
So why this flow is not executing properly? is their any problem while going two transitions from one node itself? guide me
Thanks
--MAS
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205440#4205440
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205440
Yes, and I believe we got it to work in AS42. The WS Endpoint API never worked in AS50 AFAIK.
Perhaps we can revisit this now and cut through it for AS50
Here is how I currently try to do this
| AbstractDeployment deployment = new AbstractDeployment(alias);
| factory.addContext(deployment, "");
|
| ClassLoader classLoader = servlet.getClass().getClassLoader();
|
| MutableAttachments mutableAttachments = (MutableAttachments)deployment.getPredeterminedManagedObjects();
| mutableAttachments.addAttachment(ClassLoaderFactory.class, new ContextClassLoaderFactory(classLoader));
| mutableAttachments.addAttachment(JBossWebMetaData.class, jbwmd);
| mainDeployer.deploy(deployment);
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205438#4205438
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205438
"bstansberry(a)jboss.com" wrote : You're right; I think it's fine. I'd misunderstood what the validate(ControllerContext) call was really doing. I got sucked into a unrelated debugging fest today so haven't proved it yet, but it should be fine.
Just an update: as expected, this works fine. :-) I included a JMS queue in deploy-hasingleton, which got activated before the JBM server. Worked fine; when JBM got deployed the queue went through create and start.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205432#4205432
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205432