Date of First Response: 2008-01-19 05:33:18 project_key: SOA This may be related to the SOA-253 and SOA-249 issues that Jehudi logged, but then again maybe not. The issue is: what governs when a jBPM process image can be displayed in the jBPM console? What I'm seeing is that when a process is started via the quickstart (via the NewProcessInstanceCommand API call), it appears in the jBPM console, but if I try display its process image, this error is returned in the GUI: [Process Image Not Available] - I don't see an error in the server.log (attached) But - if I start the process through the jBPM console, the process image can be displayed.
Attachment: Added: Screenshot.png Attachment: Added: server.log.gz
Link: Added: This issue is related to SOA-295
Link: Removed: This issue is related to SOA-295
Link: Added: This issue is related to SOA-249
Link: Added: This issue is related to SOA-253
Link: Added: This issue related SOA-344
Link: Added: This issue related SOA-345
Len, are you looking at this?
we don't have anyone in the team that can have a look at this right now. priority for this issue is not high enough. the person that build the console left the team. so we are not better qualified then anyone else to fix this. the learning curve is not justified. especially since we are looking at a replacement of this console. my suggestion: document it as a limitation.
For users running the quickstarts - some confusion, but not a deadly problem as these are just examples - and, maybe not a serious user problem - how may users will want to manually interact with the console for apps that they deploy/start via API? Maybe few or none. But... What's the root of the problem? Will it cause problems that are not obvious now?
This is almost certainly a consequence of the fact that we have been using our own process deployment mechanism. This is being replaced by a standard jBPM deployment mechanism (through the upload servlet) and should fix this issue. This should be assigned to Kurt Stam and linked into JBESB-1401.
Link: Added: This issue depends JBESB-1401
The process definitions for the QuickStarts are now deployed using the DeployProcessToServer ant task, and we now include all the files in the processDefinition directory. Deploying the jpg along with the processdefinition.xml fixes the issue.
Link: Added: This issue related SOA-390
Steps to recreate the problem: cd bpm_orchestration1 ant deploy ant deployProcess Go to the jBPM process - view the process diagram - see the atatched screenshot
Attachment: Added: Screenshot_not_available.jpg
This is still a problem - Burr seeing in CR2 too.
I'm seeing this issue on both the standalone and embedded servers in CR2.
The problem of the missing image "[Process Image Not Available]" shows up when I use the IDE to generate the .par and the jbpm admin console to upload the .par. Plus it also happens when I deploy directly from the IDE. I have verified that the .par file contains the .jpg so the bug is somewhere in the jbpm admin console configuration/code for CR2.
YES - this is working from: /labs/jbossesb/branches/JBESB_4_2_1_GA_CP See attachment.
Attachment: Added: Screenshot_cp.png
Changed this JIRA to a bug - and marked it as fond in CR2 build.
Just to retate - with the CP bits - the process diagram is displayed with these steps: cd bpm_orchestration1 ant deploy ant deployProcess Go to the jBPM process - view the process diagram
The image is being deployed correctly but the fault lies with some changes that appear to have been made as part of the platform build process. The jBPM console is normally deployed with the jsf files (and servlets) located under /sa/ but, for some reason, this has been changed in the platform to be /app/. What is happening is that the page is being loading as .../jbpm-console/app/procdef.jsf?id=1&view=img and it contains an image tag with an alt message of "[Process Image Not Available]" and a src of "pi/1.jpg". This image tag expects to find the image at .../jbpm-console/app/pi/1.jpg but this does not exist (hence the alt message being displayed). The reason the image does not exist is that the link is supposed to refer to a servlet defined in the web.xml but this servlet is still defined with a pattern of /sa/pi. The fix is to modify the console web.xml so that the faces servlet maps to the URL of /app/pi or revert the decision to move the application from /sa/ to /app/.
Let's go with Kev's suggested fix for now and revisit why the build process changes the URL after the release.
from jcoleman In the build-tools directory, these files contain the string "/sa/pi": builders/soa/p-consoles/jbpm/src/main/webapp/web-inf/jbpm4jsf-config.xml: <pattern>^/sa/pi/(\d+).jpg$</pattern> builders/soa/p-consoles/jbpm/src/main/webapp/web-inf/web.xml: <url-pattern>/sa/pi/*</url-pattern> builders/jbpm/resources/web-production.xml: <url-pattern>/sa/pi/*</url-pattern> builders/jbpm/resources/web-development.xml: <url-pattern>/sa/pi/*</url-pattern> From our conversation, the first 2 are for the consoles, no idea about the others. Should all 4 be changed to "/app/pi" ? The string doesn't appear in the built versions, presumably because it's been packed into a war file.
fixed in trunk
Unpacking the built jbpm-console.war files in both the standalone and embedded versions shows that the jbpm4jsf-config.xml and web.xml files still contain the string "sa/pi/*" : $ grep "[app|sa]/pi" deploy/WEB-INF/*xml server/server/jbpm/deploy/WEB-INF/*xml deploy/WEB-INF/jbpm4jsf-config.xml: <pattern>^/sa/pi/(\d+).jpg$</pattern> deploy/WEB-INF/web.xml: <url-pattern>/sa/pi/*</url-pattern> server/server/jbpm/deploy/WEB-INF/jbpm4jsf-config.xml: <pattern>^/sa/pi/(\d+).jpg$</pattern> server/server/jbpm/deploy/WEB-INF/web.xml: <url-pattern>/sa/pi/*</url-pattern> so the change to "/app/si/*" is not being propagated correctly.
fixed in trunk.
Verified in both standalone and embedded servers in CR3.