Hi Tim, great that you are using the jbpm console ng!
Excellent news if you are planning to collaborate with some UIs to support work item handlers we can coordinate the work and get that done.
Hot deploy of work item handlers is not even supported when you deploy the application jboss for several reasons that were already discussed in another thread. The project needs to be broken into different jars in order to be modular and not a single big project. We need to look at the GWT Development Mode configuration to see if it allows to include other source code paths that will be automatically picked up.
Can you please elaborate a little bit more about what are you trying to achieve?
I phrased my question poorly - my question is do you think it is plausible to use mvn to create eclipse projects and import the project into eclipse and run the GWT/jetty environment inside eclipse so that when changes are made you will use them with a page refresh? I was not referring to runtime deploy to a production environment - it is no problem for us work items cannot hot deploy to JBoss.
I think the UI screens I was referring to are probably too domain specific to contribute back however we are looking to implement an HTML template capability that allows users to design documents (specifically business contracts) externally and then fill them out and sign them as part of workflow - at the end the docs are stored in our legacy document management repository. We are looking to tie this capability to the form capability you currently have however we do not feel the current form modeler is sophisticated enough to support our document building requirements and do not feel it would be worthwhile to do so since there are so many third party tools available to design HTML and CSS - not something we need to concentrate on.
I think the HTML template capability may have value in the core product.
Yeah, if you want we can discuss how to implement the HTML template capability. It will be really nice to have a simple component to diagram documents as you mention, so I think that it will be a really good community contribution. Most of the times, these components can be generic enough to be shared.
About GWT and the class path for dev mode + eclipse.. I don't know if it's possible but it's more related with the GWT Dev Mode than with the project itself. It sounds technically possible. remember that in Dev Mode you can only change Client side code not the services backend.. when you change that you will need to restart the session again.