3:44 p.m.
Hey all,
I am still getting the same error I started out with and am still unable to get my process
definition to display on the jBPM web app.
Here are the steps I've taken thus far
1) I downloaded a new copy of Eclipse (Version: 3.2.2)
2) Downloaded jbpm runtime and suite (both 3.2.1).
3) Setting the runtime (Window-> Preferences-> Jbpm-> JBPM Runtime) to ?JBoss
Jbpm Runtime 3.2.1?
4) Deleting my old versions of jbpm (starter kit 3.1.3 and 3.2.1) and Eclipse (3.3)
5) Using the advice in this post
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963971#...
5 cont.) to deal w/ the message I received upon startup with my new eclipse "An
internal error occurred during: "Initializing Java tooling"". The stack
trace I had was exactly the same as the one in the forum post above. Is there a Jira Issue
for this? I searched the Jira site using max.andersen(a)jboss.com?s name and the date range
I thought it might have been reported in and found nothing. Not a big deal as the forum
post covers how to fix the problem pretty extensively.
6) Resetting the workspace (cleared up the other errors I had been experiencing)
7) Importing my project from my previous workspace
8) Attempted to deploy my project.
I attempted to deploy the processdefinition from the web app and received the error:
anonymous wrote :
| Error deploying process: An exception of type "org.jbpm.jpdl.JpdlException"
was thrown. The message is: [[ERROR] no processdefinition.xml inside process archive]
Thanks to msandoz, I tried deploying locally in Eclipse. When I deployed the process
archive from the web app it produced the an error (but was still more constructive than
the processdefinition error ;-D). Here is the error it produced:
anonymous wrote : Error deploying process: An exception of type
"org.jbpm.jpdl.JpdlException" was thrown. The message is: [[ERROR] couldn't
parse process definition]
When I try to deploy from Eclipse's deployment tab I receive the error:
anonymous wrote : An exception happened during the deployment of the process. Reason: an
unexpected exception caused the deployment to fail.
Here is the stack-trace:
java.io.FileNotFoundException: http://localhost:8080/jbpm/upload
| at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
| at org.jbpm.ui.util.ProcessDeployer.deployProcessWithServlet(Unknown Source)
| at org.jbpm.ui.util.ProcessDeployer.access$3(Unknown Source)
| at org.jbpm.ui.util.ProcessDeployer$1.run(Unknown Source)
| at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
| at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
| at
org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:479)
| at org.jbpm.ui.util.ProcessDeployer.showProgressMonitorDialog(Unknown Source)
| at org.jbpm.ui.util.ProcessDeployer.deploy(Unknown Source)
| at org.jbpm.ui.editor.form.deployment.DeploymentForm$1.widgetSelected(Unknown Source)
| at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
| at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
| at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
| at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
| at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
| at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
| at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
| at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
| at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
| at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
| at org.eclipse.core.launcher.Main.run(Main.java:977)
| at org.eclipse.core.launcher.Main.main(Main.java:952)
In my current IDE version, other than changing my jbpm server preferences, I am not sure
how to tell the IDE to deploy to jbpm-console instead of jbpm/deploy (which appears to be
the first complain in the stack trace). This, however, is a side issue to the main issue
that I still cannot view my process definition from the site localhost:8080/jbpm-console.
It is because of this that I attempted to deploy from the web app, but as I previously
stated, received the same error as before.
If anyone has any thoughts about how to get my locally saved process archive to display on
the Web App I would be most grateful. Thanks again to everyone who has spent time thinking
about this thread.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069804#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...