[jBPM] - jBPM Designer Custom views/validations!
by Rama R Kaldindi
Rama R Kaldindi [https://community.jboss.org/people/imramaraju] created the discussion
"jBPM Designer Custom views/validations!"
To view the discussion, visit: https://community.jboss.org/message/776262#776262
--------------------------------------------------------------
Hi All,
Iam new to jbpm web based designer for BPMN modelling. And I have few questions:
- Is it possible to customize the designer in a way that allows only custom tasks/service nodes (just examples...could be other BPMN constructs as well) to be available/visible to business users? In general I want the business user to see only pre-defined process constructs that are available for use (and not the world!).
- Is it possible to introduce custom validations such that if the business user constructs process model that is not valid or possible in a particular business case (even though it may be a valid BPMN 2.0 model), then a error can be shown (similar to red X for invalid BPMN)? As example, there may be pre and post conditions on some service nodes that needs to be satisfied before a valid link can be established with other nodes. And such pre and post conditions can be based on input/output data or rule based.
So please advice if these things are possible out-of-box with the current designer or what is the best away to approach such need?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/776262#776262]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 4 months
[JBoss Web Services] - Re: missing <wsse:Security> tag in WS-Security
by NOE GUTIERREZ
NOE GUTIERREZ [https://community.jboss.org/people/noe_bartino1984] created the discussion
"Re: missing <wsse:Security> tag in WS-Security"
To view the discussion, visit: https://community.jboss.org/message/779166#779166
--------------------------------------------------------------
*Hi:*
*I have found the solution to this mistake *https://community.jboss.org/message/776941#776941 missing <wsse:Security> tag in WS-Security**
*the configuration client*
*jdk6 an jboss 5.1.0
*
* I used this VM options -Dsun.lang.ClassLoader.allowArraySyntax=true "-Djava.endorsed.dirs=D:\jboss-5.1.0.GA\lib\endorsed"*
*
*
*and added this jars to my classpath*
* *jaxb-impl.jar*
* *xmlsec-1.4.1.jar*
* *jboss-logging-spi.jar*
* *jbossws-spi.jar*
* *jbossws-spi.jar*
* *jbossws-native-jarxrpc.jar*
* *mail.jar*
* *jbossws-client.jar*
* *jboss-common-core.jar*
* *jbossws-common.jar*
* *wsdl4j.jar*
* *jboss-xml-binding.jar*
* *jaxb-xjc.jar*
* *xercesImpl.jar*
* *policy.jar*
* *commos-logging.jar*
* *javassist.jar*
* *concurrent.jar*
* *jboss-remoting.jar*
*my main Class Client*
*import org.jboss.logging.Logger;*
*import org.jboss.ws.core.StubExt;*
*import misservicios.insys.ws.*;*
*public class ClientSample {*
* private static Logger log = Logger.getLogger(ClientSample.class);*
* public static void main(String[] args) {*
* System.out.println("***********************");*
* System.out.println("Create Web Service Client...");*
* try {*
*log.info("Create Web Service Client...");*
* log.info("***********************");*
* OperacionService service1 = new OperacionService();*
* log.info("El Servicio consumido "+service1.getServiceName().getNamespaceURI());*
* log.info("El host:"+service1.getWSDLDocumentLocation().getHost());*
* log.info("El path:"+service1.getWSDLDocumentLocation().getPath());*
* log.info("El Protocolo:"+service1.getWSDLDocumentLocation().getProtocol());*
* Operacion port1 = service1.getOperacionPort();*
* ((StubExt) port1).setConfigName("Standard WSSecurity Client");// add this line*
* System.setProperty("org.jboss.ws.wsse.keyStore", "D:\\MY_WEBSERVICES\\WEB_SERVICE_CLIENT\\src\\META-INF\\client-keystore.jks");*
* System.setProperty("org.jboss.ws.wsse.keyStorePassword", "changeit");*
* System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks");*
* System.setProperty("org.jboss.ws.wsse.trustStore", "D:\\MY_WEBSERVICES\\WEB_SERVICE_CLIENT\\src\\META-INF\\client-truststore.jks");*
* System.setProperty("org.jboss.ws.wsse.trustStorePassword", "changeit");*
* System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks");*
* log.info("Call Web Service Operation...");*
* log.info("Server said: " + port1.multiplica(Integer.parseInt(args[0]),Integer.parseInt(args[1])));*
* log.info("***********************");*
* log.info("Call Over!");*
* } catch (Exception e) {*
* log.error("ocurrio un Error ",e);*
* }*
* }*
*}*
*
*
*
*
*
*
*
*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/779166#779166]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 4 months
[jBPM] - Terminate end event in subprocess must not terminate parent process?
by Ted Pan
Ted Pan [https://community.jboss.org/people/ted.pan] created the discussion
"Terminate end event in subprocess must not terminate parent process?"
To view the discussion, visit: https://community.jboss.org/message/779138#779138
--------------------------------------------------------------
hi,
from the issue
https://issues.jboss.org/browse/JBPM-3371 https://issues.jboss.org/browse/JBPM-3371
it says that *Terminate end event in subprocess must not terminate parent process.*
the following is copied from the issue, in case someone could not access the issue tracker.
* According to the spec a terminate node in the subprocess aborts the execution in the subprocess. "Then the process continues on the normal flow" out of the subprocess [Bruce Silver, BPMN Method & Style, p. 82]*
*The spec says:*
*Sub-process level end events*
*For a "terminate" End Event, the Sub-Process is abnormally terminated. In case of a multi-instance Sub-Process, only the affected instance is terminated—no other ongoing Sub-Process instances or higher-level Sub-Process or Process instances are affected.*
but from document http://docs.jboss.org/jbpm/v5.4/userguide/ch.core-basics.html#d0e1529 http://docs.jboss.org/jbpm/v5.4/userguide/ch.core-basics.html#d0e1529
* Note that, if you use a terminating event node inside a sub-process, you are terminating the top-level process instance, not just that sub-process.*
in my case, a subprocess will signal an event to parent process, then goes to a terminating node. in parent process, there is a Catching Signal Event to catch the event, then go to other node.
when running same code in different machines,
one faster machine always works as what I want. the process go to the Catching Signal Event.
On the other slower machine, there is always an exception thrown out in the backend log
Gateway:104] -- XOR split could not find at least one valid outgoing connection for split Gateway
( the content of this exception is not important, as my understanding, the process is still going on after the subprocess).
So my question is that *which one is correct*? and why the behavior is different?
Thanks
(I'm using jPBM5.4)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/779138#779138]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 4 months
[jBPM] - is it possible to add a subprocess to a workitem dynamically?
by Ted Pan
Ted Pan [https://community.jboss.org/people/ted.pan] created the discussion
"is it possible to add a subprocess to a workitem dynamically?"
To view the discussion, visit: https://community.jboss.org/message/779125#779125
--------------------------------------------------------------
hi,
by using
DynamicNodeInstance dynamicNodeInstance = (DynamicNodeInstance)processInstance.getNodeInstances().iterator().next();
DynamicUtils.addDynamicSubProcess(dynamicNodeInstance, session, subProcessId , parameters);
in the executeWorkItem() of WorkItemHandler, I was able to execute a subprocess on-the-fly when the process instance enters this workitem.
But it requires that this workitem is inside a dynamic node, in my case, it is ad-hoc subprocess.
My question is, without using the ad-hoc subprocess, how could I add the dynamic subprocess to current workitem?
Thanks
Ted
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/779125#779125]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 4 months
[Beginner's Corner] - JBoss AS 7 with OSGi and JMS
by marquies
marquies [https://community.jboss.org/people/marquies] created the discussion
"JBoss AS 7 with OSGi and JMS"
To view the discussion, visit: https://community.jboss.org/message/747886#747886
--------------------------------------------------------------
Hi all!
What I want to do: I would like to build an OSGi bundle whichs connects to a JMS queue, all in JBoss AS.
What I have done: I tried and compiled the quickstarts helloworld-osgi and helloworld-jms, both successfull. Then I mixed them, I copied the JMS code to the OSGi bundle changed the pom. It compiles, the bundle is build, but the installation in jboss failed: missing requirement [Module[jboss-as-helloworld-osgi:7.1.1.Final]] package; (package=javax.jms)
I guessed that JBoss AS provides javax.jms, doesn't it?
01:57:08,777 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS018562: Redeployed "jboss-as-helloworld-osgi-7.1.1.Final.jar"
01:57:08,778 INFO [org.jboss.as.server] (management-handler-thread - 14) JBAS018565: Replaced deployment "jboss-as-helloworld-osgi-7.1.1.Final.jar" with deployment "jboss-as-helloworld-osgi-7.1.1.Final.jar"
01:57:08,777 ERROR [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011900: Cannot start bundle: jboss-as-helloworld-osgi:7.1.1.Final: org.osgi.framework.BundleException: Cannot resolve bundle: jboss-as-helloworld-osgi:7.1.1.Final
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:212) [jbosgi-framework-core-1.1.8.Final.jar:1.1.8.Final]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.1.8.Final.jar:1.1.8.Final]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
01:57:08,779 ERROR [jboss-as-helloworld-osgi] (Thread-79) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jboss-as-helloworld-osgi:7.1.1.Final]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119)
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1416)
at org.jboss.msc.service.ServiceControllerImpl.access$2700(ServiceControllerImpl.java:49)
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1954)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]
Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jboss-as-helloworld-osgi:7.1.1.Final]: missing requirement [Module[jboss-as-helloworld-osgi:7.1.1.Final]] package; (package=javax.jms)
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:149)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
... 11 more
Generated MANIFEST.MF
Manifest-Version: 1.0
Built-By: breucking
Build-Jdk: 1.6.0_33
Bundle-Version: 7.1.1.Final
Tool: Bnd-1.15.0
Bundle-Name: jboss-as-helloworld-osgi
Bnd-LastModified: 1342140094712
Bundle-Activator: org.jboss.as.quickstarts.helloworld.osgi.Activator
Created-By: Apache Maven Bundle Plugin
Bundle-ManifestVersion: 2
Bundle-SymbolicName: jboss-as-helloworld-osgi
Import-Package: javax.jms,javax.naming,org.osgi.framework;version="[1.
5,2)"
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/747886#747886]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 4 months