[JBoss jBPM] - Cange swimlane at runtime
by pgros
Is it possible to change the swimlane or asignment of a task in a ProcessInstance, when the tasknode is not reached yet?
apparently the asignment is appointed when the process leaves the start-state and can not be changed later
even if i use a process variable:
| <task name="Execute">
| <assignment actor-id="#{SWIMLANE}"></assignment>
| </task>
|
the processvariable seems to be read when the process leaves the start-state so it doeasn't matter if i change it later, the asignment will be to the actor which was set when leaving the start state
any ideas ? the problem is that the point when i want to change the asigned-actor before reaching the task-node so there isn't a taskinstance yet
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193730#4193730
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193730
17 years, 1 month
[JBoss Tools (users)] - Re: a deployment problem
by gufiya
I'm using JBoss 4.2.3GA, Eclipse 3.3.2 (for J2EE).
I have also added to eclipse JBoss Tools 2.1.2.
When I deploy the EAR, everything is fine, and error log stays clean.
When I remove the EAR from the server, the client JAR remains on the server, I cannot delete it (until I shutdown JBoss), and I receive the following error log entry:
eclipse.buildId=M20080221-1800
| java.version=1.5.0_16
| java.vendor=Sun Microsystems Inc.
| BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=iw_IL
| Command-line arguments: -os win32 -ws win32 -arch x86
|
| Warning
| Tue Dec 02 14:14:15 IST 2008
| Publishing completed with a warning
|
It has two children entries:
eclipse.buildId=M20080221-1800
| java.version=1.5.0_16
| java.vendor=Sun Microsystems Inc.
| BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=iw_IL
| Command-line arguments: -os win32 -ws win32 -arch x86
|
| Warning
| Tue Dec 02 14:14:15 IST 2008
| Unable to delete module from server. (TitanEAR/TitanEJBClient)
|
| java.lang.Exception: Some files were not removed from the server
| at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.unpublish(JstPublisher.java:183)
| at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:106)
| at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:132)
| at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749)
| at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:835)
| at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669)
| at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
| at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
| at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
| at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
|
|
and eclipse.buildId=M20080221-1800
| java.version=1.5.0_16
| java.vendor=Sun Microsystems Inc.
| BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=iw_IL
| Command-line arguments: -os win32 -ws win32 -arch x86
|
| Warning
| Tue Dec 02 14:14:15 IST 2008
| Unable to delete module from server. (TitanEAR)
|
| java.lang.Exception: Some files were not removed from the server
| at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.unpublish(JstPublisher.java:183)
| at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:106)
| at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:132)
| at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749)
| at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:835)
| at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669)
| at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
| at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
| at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
| at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
|
|
Another important lead:
I have found a workaround.
1) Go to the EJB project preferences -> j2ee module dependencies.
2) Remove the dependency with the Client JAR project.
3) close the preferences window (otherwise step 5 will not work).
4) Go to the EJB project preferences -> Java build path.
5) Add a dependency with the Client JAR project.
Now everything works with no problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193716#4193716
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193716
17 years, 1 month