Gabriel,
In the authoring perspective, you would create and save your processes,
and once you believe you have a version that can be released, you should
open the project editor for that project and click build & deploy. This
will build the kjar and deploy it so it can be picked up by the
runtime. What you will see is that it will also create an entry in the
deploy view (meaning that this jar should be deployed to the runtime).
So in theory, if everything works correctly, you don't have to use the
deploy view (as it should auto-deploy if you click the build & deploy
button in the project editor), but you can use that to add/remove
specific kjars from runtime deployment.
Note that this is very similar to how Guvnor used to work in the 5.x
version, you don't want changes to be picked up in the runtimes as soon
as you save a file, only once you've correctly built and deployed the
kjar, it will be picked up.
Hope this helps!
Kris
On 06/07/2013 07:49 AM, Gabriel Bechara wrote:
Hello all
Using jbpm 6 last build I have a tab labeled 'deploy'. This tab is not available
in beta2 but seems to be a mandatory step to access processes at runtime.
Tried to use it for the HR project without success, can you give us some guidance?
Regards
Gab
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev