If you want a certain type, specify it when you create it, ie.:
script
| expressionLong myNumber = new Long(123456);/expression
| variable name='accountId' access='write' mapped-name='myNumber' /
| /script
This should result in your value being stored as a Long.
View the original post :
Yes, the TimerServiceBean is in there. Yes, I'm in an ejb container: as
mentioned, I'm using the JBoss 4.0.4 server that is distributed with 3.2.GA.
I've simply removed the existing jbpm-console.war from the server's jbpm/deploy
directory and replaced it with the prebuilt jbpm-enterprise.ear
I'm seeing this:
10:46:39,984 DEBUG [EjbSchedulerService] creating timer
timer(myTimeout,10:46:39,983)
| ...
| 10:46:40,166 DEBUG [Services] executing default save operations
| 10:46:40,166 DEBUG [HibernateSaveOperation] saving process instance
| 10:46:40,166 DEBUG [SaveLogsOperation]
The third transition will never be taken because it has no condition to
verify--that's just how the system works (if there are no conditions that
evaluate to true, the default (first) transition will be taken).
Try removing the CDATA tags and using a character representation for '' and
''.
I don't have an answer, but simply for comparison, I don't seem to be having
those kinds of issues with 3.2.GA.
I'm running on Oracle against an existing 3.1.2 database on which I ran the
(slightly modified) update scripts.
-Britt
View the original post :
I'm feeling a bit stupid here. I'm running the 3.2 ear out of
jbpm-jpdl-suite-3.2.GA under the example server, but the scheduler isn't
running. And well, I don't know how to make it run.
Yes, the example server comes with the WAR configured to run independently--and
the servlet starts the
I've posted several examples in the wiki recently (JbpmContributions).
Solutions are presented with complete jpdl examples and any supporting
ActionHandlers that only needs your own package name to run. These solutions
target jBPM 3.1:
# Example: a JSP for viewing process instance history
