0

The jBPM documentation specifies data objects should be in the same package as e.g. business rules, decision tables or business processes. As a result of this limitation, the following project structure becomes unusable because the contents of com.sample.data are invisible for items defined in com.sample.rulesetX

com.sample.data
- DataObject1
- DataObject2
com.sample.ruleset1
- RuleSet1
- ProcessDefinition1
- DecisionTable1
com.sample.ruleset2
- RuleSet1
- ProcessDefinition1
- DecisionTable1

What would you advise as a possible/recommended approach to organize projects using jBPM? We are currently working on a project where we expect hundreds of rules, processes, tables and data objects. Organising them all below a com.sample root package makes the project very difficult to manage... Thanks for all tips!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.