-
1. Re: Strange Exception
rebody May 7, 2010 6:26 AM (in response to newbeewan2)Hi C. Mourad Jaber,
Could you create a testcase for this problem? If you could provide a testcase to reproduce it. It will be much easier for us to find out what caused the problem. Thank you.
-
2. Re: Strange Exception
newbeewan2 May 7, 2010 7:59 AM (in response to rebody)Ok,
It happen for every single process i deploy...
My configuration is JBPM4.3, Spring 3.0.2 using the SpringHelper.
Here I put an archive with a simple deployement test using HSQLDB.
Perhaps I'm doing something wrong
Regards
-
simpletest.zip 11.1 KB
-
-
3. Re: Strange Exception
rebody May 7, 2010 11:50 PM (in response to newbeewan2)Hi C. Mourad Jaber,
If you want to deploy process definition from inputStream. You have to set a name for this InputStream. And this name must end with ".jpdl.xml". So jBPM 4 could know how to deploy it.
Your problem is the name did not end with '.jpdl.xml'. So jBPM 4 did not know how to deploy it. And just store inputStream as a plain blob.
But the error information of jBPM4 is strange. We should review it and let it report the correct information.
PS: I change spring from 3.0.2.RELEASE to 2.5.6.SEC01. Then the error information change to
org.jbpm.api.JbpmException: no process definition with key 'simple'
It seems that spring 3 make different behaviours. Is it the bug of spring 3?
-
-
5. Re: Strange Exception
newbeewan2 May 8, 2010 6:55 AM (in response to rebody)Thanks for th jira report !
Changing simplejpdl to simple.jpdl.xml solve partially the issue !
Search by key works but search by ID, but as the deployement id is "simple-1" and not "SuperSimple" (my fault !).
I've got the previous described exception in place of an explicit exception tell that this ID doesn't exist !
Regards