0 Replies Latest reply on Jun 3, 2008 10:59 AM by Thijs Eggen

    versioning external webservice client jars

    Thijs Eggen Newbie

      Hey,

      We are facing the following problem, maybe someone here has some thoughts or has faces the same problem before.

      We have implemented a business process as an jBPM flow and this is running without much trouble in live production. Untill now we have deployes 5 new versions of the flow without problems.

      In this flow calls to webservices are made. For these services we generated client api's (with wsconsume) which we include in the standard lib/ext dir from jBoss.
      A problem is the fact that we want to deploy a new version of the flow wherefore non backwardscompatible modifications are made in one of the webservice calls. So when deploying the new flow and replacing the client api jar with the new one causes problems to old still running processinstances from previous flow versions. These are compiled againt the old webservice call and will therefore result in a runtime error.

      We tried adding the client jars to the par but the jbpm classloader expects including all (dependencies of the client), for example jbossws jars. Adding all jars causes masive par files which have to be stored.

      I appreciate any thoughts,

      regards,

      Thijs