[jBPM Development] - BPMN2 Tools for jBPM 5
by Koen Aers
Koen Aers [http://community.jboss.org/people/koen.aers%40jboss.com] modified the document:
"BPMN2 Tools for jBPM 5"
To view the document, visit: http://community.jboss.org/docs/DOC-15922
--------------------------------------------------------------
As most of you are aware we are working on jBPM 5 wich will be an engine capable of consuming process definitions specified in BPMN 2 format. So quickly the need arises for tools to create those process definitions. This page is currently a placeholder where you can download an archive containing a number of tools that are meant to help doing this. The archive is installable using the well known Eclipse installation mechanism.
*UPDATE:* The BPMN 2.0 diagram editor is now functionally complete and it should be possible to create most (if not all) of the BPMN 2.0 examples that are available in the jBPM repository. We are interested in feedback about possible problems. The updated editor is in the attached archive file bpmn2.zip. The archive is installable as usual.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15922]
Create a new document in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 10 months
[IronJacamar Development] - Reauthentication
by Jesper Pedersen
Jesper Pedersen [http://community.jboss.org/people/jesper.pedersen] modified the document:
"Reauthentication"
To view the document, visit: http://community.jboss.org/docs/DOC-16434
--------------------------------------------------------------
h2. Description
A resource adapter can re-authenticate a physical connection (that is, one that already exists in the connection pool under a different security context) to the underlying EIS. A resource adapter performs reauthentication when an application server calls the getConnection method with a security context, passed as a Subject instance, different from the context previously associated with the physical connection.
h2. Requirements
* Reauthentication support: The resource adapter provider must specify whether a resource adapter supports reauthentication of an existing physical connection.
* The matchManagedConnections method in ManagedConnectionFactory may return a matched ManagedConnection instance with the assumption that the ManagedConnection.getConnection method will later switch the security context through reauthentication.
* If reauthentication is successful, the resource adapter has changed the security context of the underlying ManagedConnection instance to that associated with the passed Subject instance.
Detailed description of the reauthentication process is described in section 9.1.9.
h2. Design
h2. Implementation
h2. Test suite
h3. Test client
1. Lookup connection factory / connection
2. Invoke connection with credential #1
3. Invoke connection with credential #2
should lead to success
h3. Resource adapter
* Reauthentication enabled
* Expose simple connection interface
* Configuration: Initially <min-pool-size> and <max-pool-size> should be set to 1
* Maybe do two resource adapters* #1 using Subject
* #2 using CRI
h3. Target system
* Allow a configured number of connections (java.net.Socket)* Binary protocol
* Command
* Payload
* Support Subject based security through raw data
* Support CRI based security through raw data
* Support reauthentication on existing connection
* Be able to run in-VM* All communication has to go over the Sockets for clean separation between RA and EIS
h4. Code
The EIS is located under
org.jboss.jca.core.security.reauth.eis
And test cases under
org.jboss.jca.core.security.reauth.eis.unit
h4. Protocol
Each command is identified with a byte followed by the payload for the command.
|| *Command
* || *Input
* || *Output
* ||
| CONNECT | <nothing> | Boolean (True if granted access) (OBJECT) |
| CLOSE | <nothing> | <nothing> |
| ECHO | Serializable (OBJECT) | Serializable (Echo service) (OBJECT) |
| AUTH | UserName (UTF)
Password (UTF) | String (User name) (OBJECT) |
| UNAUTH | <nothing> | Boolean (True if successful) (OBJECT) |
| GETAUTH | <nothing> | String (User name) (OBJECT) |
Option #C and #A described in section 9.1.9 should be tested in that order.
Ideally the entire test suite setup can be included as an example in the user guide.
h2. JDBC
Some databases support reauthentication, so we need to provide a way to enable support in our JDBC resource adapter.
We can also provide plugins for the Open Source databases that supports this.
h2. Links
* http://jcp.org/en/jsr/detail?id=322 Java EE Connector Architecture 1.6
* https://issues.jboss.org/browse/JBJCA-94 JBJCA-94
* http://community.jboss.org/en/picketbox PicketBox user forum
* http://community.jboss.org/en/picketbox/dev PicketBox developer forum
* http://community.jboss.org/docs/DOC-10430 Old JCA pooling mechanims
* http://community.jboss.org/message/230163#230163 User thread
* https://issues.jboss.org/browse/JBAS-1429 JBAS-1429
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16434]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 10 months
[IronJacamar Development] - Reauthentication
by Jesper Pedersen
Jesper Pedersen [http://community.jboss.org/people/jesper.pedersen] modified the document:
"Reauthentication"
To view the document, visit: http://community.jboss.org/docs/DOC-16434
--------------------------------------------------------------
h2. Description
A resource adapter can re-authenticate a physical connection (that is, one that already exists in the connection pool under a different security context) to the underlying EIS. A resource adapter performs reauthentication when an application server calls the getConnection method with a security context, passed as a Subject instance, different from the context previously associated with the physical connection.
h2. Requirements
* Reauthentication support: The resource adapter provider must specify whether a resource adapter supports reauthentication of an existing physical connection.
* The matchManagedConnections method in ManagedConnectionFactory may return a matched ManagedConnection instance with the assumption that the ManagedConnection.getConnection method will later switch the security context through reauthentication.
* If reauthentication is successful, the resource adapter has changed the security context of the underlying ManagedConnection instance to that associated with the passed Subject instance.
Detailed description of the reauthentication process is described in section 9.1.9.
h2. Design
h2. Implementation
h2. Test suite
h3. Test client
1. Lookup connection factory / connection
2. Invoke connection with credential #1
3. Invoke connection with credential #2
should lead to success
h3. Resource adapter
* Reauthentication enabled
* Expose simple connection interface
* Configuration: Initially <min-pool-size> and <max-pool-size> should be set to 1
* Maybe do two resource adapters* #1 using Subject
* #2 using CRI
h3. Target system
* Allow a configured number of connections (java.net.Socket)* Binary protocol
* Command
* Payload
* Support Subject based security through raw data
* Support CRI based security through raw data
* Support reauthentication on existing connection
* Be able to run in-VM* All communication has to go over the Sockets for clean separation between RA and EIS
h4. Code
The EIS is located under
org.jboss.jca.core.security.reauth.eis
And test cases under
org.jboss.jca.core.security.reauth.eis.unit
h4. Protocol
Each command is identified with a byte followed by the payload for the command.
|| *Command
* || *Input
* || *Output
* ||
| CONNECT | <nothing> | Boolean (True if granted access) (OBJECT) |
| CLOSE | <nothing> | <nothing> |
| ECHO | Serializable (OBJECT) | Serializable (Echo service) (OBJECT) |
| AUTH | UserName (UTF)
Password (UTF) | String (User name) (OBJECT) |
| UNAUTH | <nothing> | Boolean (True if successful) (OBJECT) |
Option #C and #A described in section 9.1.9 should be tested in that order.
Ideally the entire test suite setup can be included as an example in the user guide.
h2. JDBC
Some databases support reauthentication, so we need to provide a way to enable support in our JDBC resource adapter.
We can also provide plugins for the Open Source databases that supports this.
h2. Links
* http://jcp.org/en/jsr/detail?id=322 Java EE Connector Architecture 1.6
* https://issues.jboss.org/browse/JBJCA-94 JBJCA-94
* http://community.jboss.org/en/picketbox PicketBox user forum
* http://community.jboss.org/en/picketbox/dev PicketBox developer forum
* http://community.jboss.org/docs/DOC-10430 Old JCA pooling mechanims
* http://community.jboss.org/message/230163#230163 User thread
* https://issues.jboss.org/browse/JBAS-1429 JBAS-1429
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16434]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 10 months
[IronJacamar Development] - Reauthentication
by Jesper Pedersen
Jesper Pedersen [http://community.jboss.org/people/jesper.pedersen] modified the document:
"Reauthentication"
To view the document, visit: http://community.jboss.org/docs/DOC-16434
--------------------------------------------------------------
h2. Description
A resource adapter can re-authenticate a physical connection (that is, one that already exists in the connection pool under a different security context) to the underlying EIS. A resource adapter performs reauthentication when an application server calls the getConnection method with a security context, passed as a Subject instance, different from the context previously associated with the physical connection.
h2. Requirements
* Reauthentication support: The resource adapter provider must specify whether a resource adapter supports reauthentication of an existing physical connection.
* The matchManagedConnections method in ManagedConnectionFactory may return a matched ManagedConnection instance with the assumption that the ManagedConnection.getConnection method will later switch the security context through reauthentication.
* If reauthentication is successful, the resource adapter has changed the security context of the underlying ManagedConnection instance to that associated with the passed Subject instance.
Detailed description of the reauthentication process is described in section 9.1.9.
h2. Design
h2. Implementation
h2. Test suite
h3. Test client
1. Lookup connection factory / connection
2. Invoke connection with credential #1
3. Invoke connection with credential #2
should lead to success
h3. Resource adapter
* Reauthentication enabled
* Expose simple connection interface
* Configuration: Initially <min-pool-size> and <max-pool-size> should be set to 1
* Maybe do two resource adapters* #1 using Subject
* #2 using CRI
h3. Target system
* Allow a configured number of connections (java.net.Socket)* Binary protocol
* Command
* Payload
* Support Subject based security through raw data
* Support CRI based security through raw data
* Support reauthentication on existing connection
* Be able to run in-VM* All communication has to go over the Sockets for clean separation between RA and EIS
h4. Code
The EIS is located under
org.jboss.jca.core.security.reauth.eis
And test cases under
org.jboss.jca.core.security.reauth.eis.unit
h4. Protocol
Each command is identified with a byte followed by the payload for the command.
|| *Command
* || *Input
* || *Output
* ||
| CONNECT | <nothing> | Boolean (True if granted access) (OBJECT) |
| CLOSE | <nothing> | <nothing> |
| ECHO | OBJECT | Serializable (Echo service) (OBJECT) |
| AUTH | UserName (UTF)
Password (UTF) | String (User name) (OBJECT) |
Option #C and #A described in section 9.1.9 should be tested in that order.
Ideally the entire test suite setup can be included as an example in the user guide.
h2. JDBC
Some databases support reauthentication, so we need to provide a way to enable support in our JDBC resource adapter.
We can also provide plugins for the Open Source databases that supports this.
h2. Links
* http://jcp.org/en/jsr/detail?id=322 Java EE Connector Architecture 1.6
* https://issues.jboss.org/browse/JBJCA-94 JBJCA-94
* http://community.jboss.org/en/picketbox PicketBox user forum
* http://community.jboss.org/en/picketbox/dev PicketBox developer forum
* http://community.jboss.org/docs/DOC-10430 Old JCA pooling mechanims
* http://community.jboss.org/message/230163#230163 User thread
* https://issues.jboss.org/browse/JBAS-1429 JBAS-1429
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-16434]
Create a new document in IronJacamar Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 10 months
[JBoss ESB Development] - Jboss ESB JBPM - No EPR present in process instance
by keljboss
keljboss [http://community.jboss.org/people/keljboss] created the discussion
"Jboss ESB JBPM - No EPR present in process instance"
To view the discussion, visit: http://community.jboss.org/message/586500#586500
--------------------------------------------------------------
Hi,
I am a new in jboss ESB, I am triyng to make JBPM and JBOSS ESB exchange().
my example is that jbpm calls ESB and get the response, when i test the esb using soapUI the process work fine, but using JBPM i have the exception below
org.jboss.soa.esb.ConfigurationException: *No EPR present in process instance*
at org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler.execute(EsbActionHandler.java:137)
my jboss-esb.xml
<?xml version="1.0"?><jbossesb parameterReloadSecs="5"xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."><providers> <jbr-provider name="ibaSommeHttpGateway" protocol="http"> <jbr-bus busid="ibaSommeHttpGateway" port="9999"/> </jbr-provider> <jbr-provider name="ibaMultiplicationHttpGateway" protocol="http"> <jbr-bus busid="ibaMultiplicationHttpGateway" port="7777"/> </jbr-provider></providers><services><service category="Calcule" description="calcule la somme de deux valeurs" invmScope="GLOBAL" name="somme"> <listeners> <jbr-listener busidref="ibaSommeHttpGateway" is-gateway="true" name="ibaHttpSommeGatewayListener"/> </listeners> <actions mep="RequestResponse"> <action class="org.jboss.soa.esb.actions.routing.http.HttpRouter" name="ibaSommeHttpRouter"> <property name="method" value="POST"/> <property name="endpointUrl" value="http://localhost:8080/somme/SommeService?wsdl"/> <property name="endpointAdresse" value="http://localhost:8080/somme/SommeService?wsdl"/> <property name="reply-to-originator" value="true"/> </action> <action class="org.jboss.soa.esb.actions.SystemPrintln" name="message"> <property name="message" value="in the somme yoooou pi ESB"/> </action> </actions> </service> <service category="Calcule" description="calcule la multiplication de deux valeurs" invmScope="GLOBAL" name="multiplication"> <listeners> <jbr-listener busidref="ibaMultiplicationHttpGateway" is-gateway="true" name="ibaHttpMultiGatewayListener"/> </listeners> <actions mep="RequestResponse"> <action class="org.jboss.soa.esb.actions.routing.http.HttpRouter" name="ibaMultiplicationHttpRouter"> <property name="method" value="POST"/> <property name="endpointUrl" value="http://localhost:8080/multiplication/MultiplicationService?wsdl"/> <property name="reply-to-originator" value="true"/> </action> <action class="org.jboss.soa.esb.actions.SystemPrintln" name="message"> <property name="message" value="in the multiplication ESB"/> </action> </actions> </service></services></jbossesb>
and the precessdefinition.xml
<?xml version="1.0" encoding="utf-8"?><process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="calcule">
<start-state name="start">
<transition to="somme" name="callSomme">
<action name="action">
<message>Going to the SOe</message>
</action>
</transition>
</start-state>
<node name="somme">
<action class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler">
<replyToOriginator>true</replyToOriginator>
<esbServiceName>somme</esbServiceName>
<esbCategoryName>Calcule</esbCategoryName>
<replyToOriginator>reply</replyToOriginator>
<bpmToEsbVars> <mapping bpm="a" esb="a"></mapping> <mapping bpm="b" esb="b"></mapping> </bpmToEsbVars> <esbToBpmVars> <mapping bpm="somme" esb="somme"></mapping> </esbToBpmVars> </action> <transition to="fin" name="tofin"> </transition> </node> <end-state name="fin"></end-state></process-definition>
the java code :
JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance();
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
GraphSession graphSession = jbpmContext.getGraphSession();
ProcessDefinition processDefinition =
graphSession.findLatestProcessDefinition("calcule");
String a = request.getParameter("a");
String b = request.getParameter("b");
ProcessInstance processInstance = *new* ProcessInstance(processDefinition);
Token token = processInstance.getRootToken();
System.out.println(token.getNode().getName());
ContextInstance contextInstance = processInstance.getContextInstance();
contextInstance.setVariable("a", *new* Float(500));
contextInstance.setVariable("b", *new* Float(500));
processInstance.getRootToken().signal();
is there anything that i messed ?
for information i am using jboss-esb4.9, jbpm 3.2 and jbossAS 5.1.0GA
thank you for your help
Cheers
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/586500#586500]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 10 months
