Description of problem: We have a couple of customers using Kie Spring and so far we have created document [1] and we have also using the examples from [2]. But they are broken in some aspects. For example, the XSD is not available anymore: http://drools.org/schema/kie-spring.xsd We must have a supported example to share with customers.
I forgot the links references, see [1] and [2]. [1] https://access.redhat.com/solutions/1412263 [2] https://github.com/droolsjbpm/droolsjbpm-integration/tree/master/kie-spring/src/test
Alessandro, William, could you please specify in a bit more detail what should such quickstart contain? Do we want to show just the integration points between KIE and Spring? Or some should the quickstart contain some end-to-end simple use case with web content as well (which would call that kie-spring integration)? Or maybe both? Any more details would be great. Thanks!
*** Bug 1215447 has been marked as a duplicate of this bug. ***
Same request was also created by Josh West as BZ 1215447. He provided some useful info to start with: " Maceij has created a great sample spring application using the embedded execution server with the Spring API. Many large firms/customers use lots of Spring and a quickstart for those users would drive faster adoption. This BZ is to request that the sample application [2] is converted to the enterprise product dependencies, and with a configuration for JBoss EAP, Tomcat, WAS, and WebLogic. Even better would be a Maven archetype for a Spring / JBPM service. [1] Blog Post: http://mswiderski.blogspot.com/2014/11/cross-framework-services-in-jbpm-62.html [2] Spring JBPM Code: https://github.com/mswiderski/spring-jbpm-app/ "
Petr, anything will be welcome. I would say the best is both. Simple standalone project is better to hide all web interference and also any complex Spring setup and so focus in the API using plain Spring xml. However an webapp is closer to the real world and this bring advantages related to how to build correctly an web application. I ado agree that mvn achrtypes can help a lot, but not sure if it ca nbe in the scope of this BZ
Hello, IMO the quickstart should be something like this Maciej example: https://github.com/mswiderski/spring-jbpm-app But using all the best practices. Please notice that Spring may bring a lot of confusion. Customer may use a non Kie Spring class in the configuration and some issues may only appear in production (like transaction problems).