Joined: 05 Aug 2003 Posts: 59 Location: Sydney, Australia
Just encountered similar BIP4127E issue in Broker v8 where the deploy seemed to be referencing a module that no longer existed. Multiple cleans and redeploys were not a help but removing all deployed resources and deploying fresh fixed it up.
Just encountered similar BIP4127E issue in Broker v8 where the deploy seemed to be referencing a module that no longer existed. Multiple cleans and redeploys were not a help but removing all deployed resources and deploying fresh fixed it up.
This was deploying via toolkit.
Especially when using a JCN and changing the class name you seem to be hitting such a problem:
The deployment of the jar file removes the current class and as such breaks the flow...
in order for the changed flow to deploy correctly you need to deploy the jar first breaking the current flow... (catch 22)
Looks like the only decent solution is to stop the flow and remove it. Then deploy again...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum