[
https://issues.jboss.org/browse/DROOLS-441?page=com.atlassian.jira.plugin...
]
Davide Sottara commented on DROOLS-441:
---------------------------------------
I haven't had the time to reproduce it, but I suspect that when the package is
reloaded, the (re)declaration of the beans is prohibited. There were some issues with
redeclarations that have been fixed in later versions. If this was the case, the second
build of the package would fail and the new process would not be loaded.
Can you try to declare the beans in a separate package and see what happens?
Thanks
drools-guvnor 5.5, declarative model, create more than one fact type,
BPMN process does not load
------------------------------------------------------------------------------------------------
Key: DROOLS-441
URL:
https://issues.jboss.org/browse/DROOLS-441
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.5.0.Final
Environment: Tomcat 6.0.35, jBPM 5.5.Final
Reporter: niraj gupta
Assignee: Mark Proctor
Labels: drools-guvnor
I am using ‘drools-guvnor 5.5.0.Final’ open source tool for designing the business
process (BPMN2). I end up in an issue and looking for help. Following is the scenario
I created a package then process then after build, deploy execute successfully. Now I
came back to guvnor and made few changes in the process. Then after same build, deploy
execute successfully. But now this time I am creating a declarative model having 2 facts,
also modifying business process. Then after same build, deploy execute successfully. This
time modified/latest business process doesn’t load into console. This is my problem.
However I trouble shoot and google following are my observations:
• I am running this application in tomcat 6.0.35
• It works perfectly with POJO Model Jar approach.
• It works perfectly with declarative model but having single fact.
• I am not seeing any exceptions either in UI or console logs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira