[jBPM] - JBPM workflows with zero coding
by Arjun Arjun
Arjun Arjun [http://community.jboss.org/people/arjunp] created the discussion
"JBPM workflows with zero coding"
To view the discussion, visit: http://community.jboss.org/message/589376#589376
--------------------------------------------------------------
Hi,
I am in the process learning to create workflows without any coding in elipse or any other tools.
Because the workflows will be created by end users. They should be able to create workflows and assign the users and change the status of the workflow.
For example : posting a blog post. Initiater will create a workflow based on the blog post type.
Initiater -> ProofReader -> Approver -> Post
Lets say the post is very straight forward and does not require any ProofReader. So he will skip the ProofReader part and assing it to approver.
Like that he should be able to decide his own workflows and entities between workflows. I need to guide them to create all these things in JBPM.
Can you guys guide me to ramup on this. I tried the sample evaluation workflow. I could not understand how those UIs (ratings listbox checkbox messages) are created and users are created. If possible can anoyone explain how that evaluation work flow can be re-created without coding or eclipse. Also some inputs or steps to create my blog posting workflows. Thanks in advance.
Thanks
Arjun
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/589376#589376]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
[JBoss Web Services] - wsconsume Generates uncompilable stub
by John Ament
John Ament [http://community.jboss.org/people/meetoblivion] created the discussion
"wsconsume Generates uncompilable stub"
To view the discussion, visit: http://community.jboss.org/message/589359#589359
--------------------------------------------------------------
The following constructors do not compile when I import the generate sources from a wsconsume against java ee 6 apis via maven:
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>6.0</version>
<scope>provided</scope>
</dependency>
public ReportDataIntegratorBeanService(WebServiceFeature ... features) {
super(WSDL_LOCATION, SERVICE, features);
}
public ReportDataIntegratorBeanService(URL wsdlLocation, WebServiceFeature ... features) {
super(wsdlLocation, SERVICE, features);
}
public ReportDataIntegratorBeanService(URL wsdlLocation, QName serviceName, WebServiceFeature ... features) {
super(wsdlLocation, serviceName, features);
}
Any ideas?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/589359#589359]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
Re: [jboss-user] [JBoss Tools] - BPEL Editor - quick update
by Robert (Bob) Brodt
Robert (Bob) Brodt [http://community.jboss.org/people/bbrodt] commented on
"BPEL Editor - quick update"
To view all comments on this blog post, visit: http://community.jboss.org/community/tools/blog/2011/02/15/bpel-editor--q...
--------------------------------------------------
Hi Grid,
1 I disagree - for processes with lots of partner links I think this will be useful. And it follows the well established multiple views paradigm that users have come to expect.
2 yes you are correct, BPEL does not have the concept of subprocesses and the equivalent is a Scope.
3 I think the idea is to make the editor easier to use and understand for business analysts and people who are not familiar with BPEL. If this means hiding some of the details and making it look more like BPMN, then that's OK. These pages are meant to be used in addition to the current graphical Design page. We can also allow the user to show or hide any of these pages with Preferences. How about a "BPEL Classic" and "BPEL Lite" ;)
--------------------------------------------------
13 years, 9 months
[Beginner's Corner] - Re: Secure access to an EJB3.0
by Wolfgang Knauf
Wolfgang Knauf [http://community.jboss.org/people/WolfgangKnauf] created the discussion
"Re: Secure access to an EJB3.0"
To view the discussion, visit: http://community.jboss.org/message/589023#589023
--------------------------------------------------------------
Hi Pablo,
in AS 4.2, you might use something like this:
public class SecurityClientCallbackHandler implements CallbackHandler
{
public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException
{
//loop over parameter Callbacks
for (int intIndexCallback = 0; intIndexCallback < callbacks.length; intIndexCallback++)
{
//NameCallback: set Login
if (callbacks[intIndexCallback] instanceof NameCallback)
{
NameCallback nameCallback = (NameCallback) callbacks[intIndexCallback];
nameCallback.setName( "ADMIN" );
}
//PasswordCallback: set password.
else if (callbacks[intIndexCallback] instanceof PasswordCallback)
{
PasswordCallback passwordCallback = (PasswordCallback) callbacks[intIndexCallback];
passwordCallback.setPassword ("ADMIN".toCharArray() );
}
else
{
throw new UnsupportedCallbackException (callbacks[intIndexCallback], "Unsupported Callback!");
}
}
}
}
And in your client, perform this code to login in:
Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
props.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming.client");
props.setProperty(Context.PROVIDER_URL, "jnp://localhost:1099");
props.setProperty("j2ee.clientName", "SecurityClient");
InitialContext initialContext = new InitialContext(props);
//Initialize Login:
SecurityClientCallbackHandler callbackHandler = new SecurityClientCallbackHandler();
LoginContext loginContext = new LoginContext ("somename", callbackHandler);
loginContext.login();
Note the the "j2ee.clientName" must be declared in a file "jboss-client.xml":
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss-client PUBLIC "-//JBoss//DTD Application Client 4.2//EN" " http://www.jboss.org/j2ee/dtd/jboss-client_4_2.dtd http://www.jboss.org/j2ee/dtd/jboss-client_4_2.dtd" >
<jboss-client>
<jndi-name>SecurityClient</jndi-name>
...
</jboss-client>
And the "login context" name (here: "somename") must be declared in a file "auth.conf" in META-INF of your client JAR:
somename {
// jBoss LoginModule
org.jboss.security.ClientLoginModule required
;
};
And finally, start your client with a parameter pointing to "auth.conf": -Djava.security.auth.login.config=.../META-INF/auth.conf
Hope this helps
Wolfgang
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/589023#589023]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 9 months
