Skip to content


Sneak peak at Spring Activities

Calling Spring beans from a process is a minimum requirement for any Spring – jBPM4 integration. Starting from RC1, changes have been made by Tom which enables following activity definition:



The expr resolves the Spring bean. Furthermore, it’s possible to provide parameters, as following:


	
		
	

I’m waiting for the release of RC1 before I’ll update the demo application.

Posted in Spring, jbpm.


3 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. sv says

    When is the RC1 expected to ship? From what I last read about it, it was some time this week?

    Thanks,

  2. Andries Inzé says

    Today I believe

  3. Robert Moskal says

    Thanks for all your work on this. I’m just begining a JBPM project and decided to go with version 4. For the most part I am able to get the spring integration to work when using the main trunk version of JBPM4. There are only two issues so far.

    The first thing is that if I use the IdentityService to create a user I get a hibernate mapping error on:

    Unknown entity: org.jbpm.pvm.internal.identity.impl.UserImpl

    I’m not to worried about that, maybe I need to added the mapping files manually (instead of using the annotated factory).

    I’m more curious about how to pass information about the current Execution into the spring beans specified in the construct. Your EchoService has the sayHelloWithExecution method. Yet when I debug your test, the org.jbpm.pvm.internal.history.HistorySession has no properties that I can see. Sorry to be a pest, but how do I get a useful Execution object to be pased to that method?

    Thankd and regards,

    Robert



Some HTML is OK

or, reply to this post via trackback.