MessageService and JMS

[mteira]

Hello.
Sorry for crossposting, but I sent this yesterday to the jBPM-users forum, and after knowing the existence of this other forum, I think it matches better here:

Hello.
I'm interested into implementing a clustered capable workflow system, and started reading the user tutorial of jBPM and also some of the source code to see how the thing works.

I need to support concurrent execution for the actions associated with parallel tokens into process instances (and also for tokens from different process instances). Having into account that I want to run inside a J2EE server, I'm observing the following facts:
1.-CommandExecutorThread is not the way to go for me, because it consumes the messages in a single thread, so, a Task with two simultaneous Tokens is not going to execute the two branches at the same time. I think that with this approach, different tasks are not running actions in parallel neither. The running thread is another problem to deploy it inside a J2EE application server.
2.-Using DbMessageService as MessageService implementation needs the messages to be consumed from a central point. This seems also a not J2EE friendly approach.

So, I think that the most natural way to implement it is to use a JMS message service, and so, implement MDBs to consume those messages and run the required actions, in a similar way CommandExecutorThread is working but only consuming the J2EE provided message.
This will probably be a good starting point to provide clustering capabilities, since the JMS component can be clustered, and we could consume the messages from different J2EE servers.

Do you think this is a right approach? Any comments about this?


I've also seen that there's a org.jbpm.msg.jms package that seems to be an effort to implement just this, a MessageService JMS implementation. But it seems it's under construction (as I can see some TODO comments in the code , and some methods remain unimplemented). I'm I right. Is this an effort to do what I'm trying to do?

Is somebody working into this? Where could I find more information about it?

Regards.

[tom.baeyens]

your observations are correct:

| 1.-CommandExecutorThread is not the way to go for me, because it
| consumes the messages in a single thread, so, a Task with...

Indeed there were problems with the command executor thread. Even on a standard java platform (for which it was intended) this was not good enough. We merged the timers and messages into jobs as the basis for our scheduler and message service targetted for the standard java platform. And now we're finishing this rewrite. Multiple concurrent threads should now be supported. Also the jobs will all be executed in a separate transaction.

| I've also seen that there's a org.jbpm.msg.jms package that seems to
| be an effort to implement just this, a MessageService JMS
| implementation. But it seems it's under construction

Indeed. That is under construction. Currently we are trying to set up a test environment for this in HEAD of CVS. see jpdl/test. that is a sub project in which i want to set up the server side tests with cactus to have a test environment for our JMS implementation of the message service and for our EJB Timer implementation of our scheduler service.

All help in setting up this test environment and testing the our JMS implementation of the MessageService is welcome ! Check out jboss/configuration for configuring your jboss and jpdl/test for the test environment that i was going to set up.

Can you get the JMS based message service impl running in jboss ? How would you improve what we have in HEAD of cvs today in module jbpm.3 ?

[mteira]

Thanks a lot for your response, Tom.

I've been only playing with the starters-kit 3.1. But I'm going to checkout the CVS version and take a look to what is being done. I'll try to setup that environment in a jboss server, but expect a storm of questions about it. ;-)

Is this forum an appropiate place to expose those questions about that setup?

Regards.

Manuel

[mteira]

Hello again.

I have some problems to checkout that code. I've checked out the whole jbpm.3 module (HEAD) and no test directory appeared under jbpm.3. Also, I've been trying with the sourceforge.net CVS viewer, and yes, there's a test directory, but I was looking in some directories and it seems to be no files inside any of them.

I have to say that the CVS access information in the jboss page was not working for me , and I had to change the server name from cvs.sourceforge.net to jbpm.cvs.sourceforge.net (I had to do this while checking other SF proyects recently, so, I thought it was related with some policy change in sourceforge). After this change, my CVS access uses this data:

CVSROOT=:pserver:[e-mail]:2401/cvsroot/jbpm
Module: jbpm.3

jbpm.3 is checking out successfully, but I cannot find any test or jboss directory there.

Any idea?

Regards
--
Manuel

[tom.baeyens]

feel free to shoot your storm of questions here in the dev forum. head of CVS has a new build structure. more modular, but sometimes a bit more complex.

initial pointers:

start with checking out jbpm.3, then read build/readme.html

then the jboss configuration deployment stuff is in jboss/configuration/build.xml

[tom.baeyens]

oops. the cvs server has moved some time ago to jboss. anoncvs.forge.jboss.com i'll update it right away.

let me know if that works for you

[tom.baeyens]

here's a link to the appropriate cvs info http://www.jboss.com/products/jbpm/downloads

website needs updating. there are a few pages out of sync...

[mteira]

OK. I was using the one available here:

http://labs.jboss.com/portal/jbossjbpm/download/index.html

The new server worked and I have the code. I'm going to start reading it.


Thanks again.

[mteira]

Hello again.
I've just imported the CVS tree into an Eclipse project. I've setup the local repository. but when I try to run the /build/build.xml build target (from Eclipse too) I got the following output:

Buildfile: C:\src\Eclipse\jbpm\build\build.xml
build:
create.manifest:
generate:
compile.dependencies:
compile:
compile.java.sources:
include.resources:
create.manifest:
jpdl.dependencies:
jpdl:
jar.dependencies:
jar:
[jar] Building jar: C:\src\Eclipse\jbpm\jpdl\jar\target\jbpm-jpdl.jar
package:
install:
[copy] Copying 1 file to C:\Documents and Settings\Administrador\jbpm\repository\jbpm\jpdl\3.2.Alpha1-SNAPSHOT\lib

BUILD FAILED
C:\src\Eclipse\jbpm\build\build.xml:31: The following error occurred while executing this line:
C:\src\Eclipse\jbpm\jpdl\db\build.xml:35: C:\Documents and Settings\Administrador\jbpm\repository\jbpm\identity\3.2.Alpha1-SNAPSHOT\lib not found.

Total time: 2 seconds


What could be the reason?

Thanks a lot.

[mteira]

Hello.
I'm still running into problems to run satisfactory a lot of ant targets into the project. It seems there are implicit dependencies that the build scripts are not aware of.

Anyway, in order to taste the CVS version, I've deployed into a running jboss the ear (from /enterprise/ear) jbpm.ear succesfully. But I'm missing the users into the database (and so, I'm not able to login into the jbpm-console included with that ear). I've found that there's information about those users into /jboss/db/src/main/resources/identities.xml, but I don't know if there's a way to automate interting that data into the DB (I'm using an oracle datasource). In the starters-kit I found it to be just a matter of configuring an hibernate.cfg file and then run some ant target to generate scripts for the given database.

BTW, I made a pair of changes during my fight against the code:
1.-Changed the application.xml at /enterprise/ear/src/main/resources/META-INF
Index: application.xml
===================================================================
RCS file: /cvsroot/jbpm/jbpm.3/enterprise/ear/src/main/resources/META-INF/application.xml,v
retrieving revision 1.2
diff -u -r1.2 application.xml
--- application.xml 28 Aug 2006 14:06:02 -0000 1.2
+++ application.xml 12 Sep 2006 08:10:45 -0000
@@ -6,7 +6,10 @@
<display-name>jbpm-enterprise-beans</display-name>


- jbpm-console.war
+
+ <web-uri>jbpm-console.war</web-uri>
+ <context-root>/jbpm-console</context-root>
+




As the webapp was not deploying correctly under my jboss 4.0.4 GA.

And also, added a .cvsignore at /jpdl/test to avoid it complaining about changes to commit for jpdl/test/*

Index: .cvsignore
===================================================================
RCS file: .cvsignore
diff -N .cvsignore
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ .cvsignore 1 Jan 1970 00:00:00 -0000
@@ -0,0 +1,1 @@
+target


So, is there an easy and automated way to create the schema in my DB (an ant target at some directory)? And also a way to insert the data for the users and other data needed for the tests?

Thanks.

Best regards.

[mteira]

Excuses for the last post. It seems that the diffs where intercepted by the HTML parsing. Trying again with code tags:

Index: application.xml
===================================================================
RCS file: /cvsroot/jbpm/jbpm.3/enterprise/ear/src/main/resources/META-INF/application.xml,v
retrieving revision 1.2
diff -u -r1.2 application.xml
--- application.xml 28 Aug 2006 14:06:02 -0000 1.2
+++ application.xml 12 Sep 2006 08:16:10 -0000
@@ -6,7 +6,10 @@
 <display-name>jbpm-enterprise-beans</display-name>

 <module>
- <war>jbpm-console.war</war>
+ <web>
+ <web-uri>jbpm-console.war</web-uri>
+ <context-root>/jbpm-console</context-root>
+ </web>
 </module>

 <module>

Index: .cvsignore
===================================================================
RCS file: .cvsignore
diff -N .cvsignore
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ .cvsignore 1 Jan 1970 00:00:00 -0000
@@ -0,0 +1,1 @@
+target

[mteira]

I've been fighting against the ant build files, my ignorance and the jBPM CVS to finally, be able to deploy the jbpm.ear inside my JBoss 4.0.4 GA.

My first question is about the changes I had to make. I want to think that at least some of them can be considered general fixes and not needed by an incorrect local setup. So, what is the preferred way to publish those changes? Just telling here? JIRA?

I'm running into problems now while trying to deploy a process from the graphical designer into Eclipse. I'm getting a very odd oracle exception complaining about a select sentence that seems to work fine when pasted into a SQLPlus session. I'm suspecting that perhaps hibernate version shipped with JBoss 4.0.4 GA could have some incompatibilities with the one needed by jBPM itself. I've pasted the full exception in the jBPM users forum as:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90558

I'm using oracle datasources because I had bad experiences in the past with the READ_UNCOMMITED transaction isolation level of hypersonic, so I would like to test jBPM under a real world database (the one we are using in our production systems).

To avoid errors in the Uploader applet bundled in the console war (bundled in the jbpm.ear) I made the following changes in it s build.xml file:

### Eclipse Workspace Patch 1.0
#P jbpm
Index: console/build.xml
===================================================================
RCS file: /cvsroot/jbpm/jbpm.3/console/build.xml,v
retrieving revision 1.6
diff -u -r1.6 build.xml
--- console/build.xml 13 Sep 2006 17:57:06 -0000 1.6
+++ console/build.xml 14 Sep 2006 10:29:08 -0000
@@ -50,6 +50,7 @@
 <lib file="${lib.jsf.impl.local}" />
 <lib file="${lib.jsf.api.local}" />
 <lib file="${lib.facelets.local}" />
+ <lib file="${lib.commons.fileupload.local}" />

 <!-- jbpm web application classes -->
 <classes dir="target/classes" />

Also, to be able to deploy from the designer, I needed to change (again) the application.xml for the jbpm.ear:

### Eclipse Workspace Patch 1.0
#P jbpm
Index: enterprise/ear/src/main/resources/META-INF/application.xml
===================================================================
RCS file: /cvsroot/jbpm/jbpm.3/enterprise/ear/src/main/resources/META-INF/application.xml,v
retrieving revision 1.2
diff -u -r1.2 application.xml
--- enterprise/ear/src/main/resources/META-INF/application.xml 28 Aug 2006 14:06:02 -0000 1.2
+++ enterprise/ear/src/main/resources/META-INF/application.xml 14 Sep 2006 10:30:56 -0000
@@ -6,7 +6,10 @@
 <display-name>jbpm-enterprise-beans</display-name>

 <module>
- <war>jbpm-console.war</war>
+ <web>
+ <web-uri>jbpm-console.war</web-uri>
+ <context-root>/jbpm</context-root>
+ </web>
 </module>

 <module>

So, now I'm stucked with that Oracle error, trying to deploy a process into JBPM to start testing JMS Message Service.

Any hint about that error?

Thanks a lot.

[tom.baeyens]

first of all a remark. i understand your frustrations. we are finishing a big restructuring of the jbpm source code base. also the build scripts still have quite some rough edges. please bear with us. it's normal that you experience some problems in the new structure. let us know your problems. we are eager to get it right asap.

FYI: main reason for this restructuring is better alignment with the multi process language approach that we're heading towards.

i added the file upload lib to the console build script. thanks.

about the /jbpm web-uri: i suppose that this change was necessary to get the designer working with the web console, right ? the default proposed deployment url is now /jbpm. jbpm-console.war fits better with our new naming scheme. also i like the /jbpm-console URI better then /jbpm. so we'll update the default that is presented in the deployment tab in the eclipse designer. would that resolve your second issue.

i'll now take a look at your oracle error.

[mteira]

first of all a remark. i understand your frustrations. we are finishing a big restructuring of the jbpm source code base. also the build scripts still have quite some rough edges. please bear with us. it's normal that you experience some problems in the new structure. let us know your problems. we are eager to get it right asap.

Thanks for the response. I was starting to think that all my trouble was my fault, and didn't want to disturb you anymore with my problems. I understand the problems on such a restructuring, and would like to help finding them.

about the /jbpm web-uri: i suppose that this change was necessary to get the designer working with the web console, right ? the default proposed deployment url is now /jbpm. jbpm-console.war fits better with our new naming scheme. also i like the /jbpm-console URI better then /jbpm. so we'll update the default that is presented in the deployment tab in the eclipse designer. would that resolve your second issue.

In its original state, that application.xml failed to deploy inside my JBoss (4.0.4 GA). Don't remember the exact reason but complained about the war entry. That was the reason why I changed it specifying the web-uri. On a first attempt, I chose "jbpm-console" just to resemble the name of the webapp, but then, when I tried to deploy a process from Eclipse (using the gd from the designers-kit 3.1) it failed because it tried to use jbpm instead of jbpm-console. I didn't find a place to configure that parameter and so, I changed that web-uri to be /jbpm. I don't mind what web-uri to use, only that it should be changed in the two places (web-uri and designer process deployer).


I've updated my local copy of the repository and tried to build just using ant (I had some trouble running some of the CVS targets and messed up my install ;-) ). I'm trying now to build the designer and it worked, running ant at:

jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build

Then, I tried to install it into a fresh eclipse install. Just using the jbpm-gpd-site-3.0.11-SNAPSHOT.zip generated into the repository, telling the eclipse to update from a local archived site. The eclipse is version 3.2, installed running rule:

ant install.eclipse

into that same directory. Something bad happened, because after restarting, Eclipse is not able to open any project, and I can see into the error log:

java.lang.NullPointerException
 at org.jbpm.ui.util.JbpmClasspathContainer.getJarNames(Unknown Source)
 at org.jbpm.ui.util.JbpmClasspathContainer.createJbpmLibraryEntries(Unknown Source)
 at org.jbpm.ui.util.JbpmClasspathContainer.getClasspathEntries(Unknown Source)
 at org.eclipse.jdt.internal.core.JavaModelManager.containerPutIfInitializingWithSameEntries(JavaModelManager.java:494)
 at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4118)
 at org.jbpm.ui.util.JbpmClasspathContainerInitializer.initialize(Unknown Source)
 at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:1900)
 at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1267)
 at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:1470)
 at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2169)
 at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:2073)
 at org.eclipse.jdt.internal.core.JavaModelManager.determineIfOnClasspath(JavaModelManager.java:808)
 at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:697)
 at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:626)
 at org.eclipse.jdt.core.JavaCore.create(JavaCore.java:1383)
 at org.eclipse.jdt.internal.ui.ResourceAdapterFactory.getAdapter(ResourceAdapterFactory.java:44)
 at org.eclipse.core.internal.runtime.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:63)
 at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:256)
 at org.eclipse.core.runtime.PlatformObject.getAdapter(PlatformObject.java:66)
 at org.eclipse.jdt.internal.ui.filters.NamePatternFilter.select(NamePatternFilter.java:62)
 at org.eclipse.jdt.internal.ui.viewsupport.ProblemTreeViewer.isFiltered(ProblemTreeViewer.java:187)
 at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.isFiltered(PackageExplorerPart.java:301)
 at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.getFilteredChildren(PackageExplorerPart.java:281)
 at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:534)
 at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:719)
 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
 at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:696)
 at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:892)
 at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1240)
 at org.eclipse.jface.viewers.AbstractTreeViewer$4.treeExpanded(AbstractTreeViewer.java:1252)
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:181)
 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.Widget.sendEvent(Widget.java:952)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937)
 at org.eclipse.swt.widgets.Tree.wmNotifyChild(Tree.java:6254)
 at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:3794)
 at org.eclipse.swt.widgets.Composite.WM_NOTIFY(Composite.java:1166)
 at org.eclipse.swt.widgets.Control.windowProc(Control.java:3298)
 at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025)
 at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
 at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1842)
 at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1319)
 at org.eclipse.swt.widgets.Tree.WM_LBUTTONDOWN(Tree.java:5171)
 at org.eclipse.swt.widgets.Control.windowProc(Control.java:3279)
 at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:4768)
 at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025)
 at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
 at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1923)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2966)
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
 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)

One thing that I'm confused about is that it seems not to be a jbpm core included into the zip file, as I found into the local-site bundled with the starters-kit. This is what I have into my jbpm-gpd-site-3.0.11-SNAPSHOT.zip file:

C:\Documents and Settings\Administrador\jbpm\repository\jbpm\designer\jpdl\3.0.1
1-SNAPSHOT>unzip -l jbpm-gpd-site-3.0.11-SNAPSHOT.zip
Archive: jbpm-gpd-site-3.0.11-SNAPSHOT.zip
 Length Date Time Name
 -------- ---- ---- ----
 0 14/09/06 14:55 features/
 0 14/09/06 14:55 plugins/
 399 14/09/06 14:26 .project
 8446 14/09/06 14:55 features/org.jbpm.gd.jpdl.feature.source_3.0.11.jar
 9088 14/09/06 14:55 features/org.jbpm.gd.jpdl.feature_3.0.11.jar
 1292277 14/09/06 14:55 plugins/org.apache.xerces_2.8.0.v200606131651.jar
 484641 14/09/06 14:26 plugins/org.eclipse.draw2d_3.2.0.v20060626.jar
 89698 14/09/06 14:26 plugins/org.eclipse.emf.common.ui_2.2.0.v20060627105
7.jar
 154682 14/09/06 14:26 plugins/org.eclipse.emf.common_2.2.0.v200606271057.j
ar
 169972 14/09/06 14:26 plugins/org.eclipse.emf.ecore.xmi_2.2.0.v20060627105
7.jar
 749588 14/09/06 14:26 plugins/org.eclipse.emf.ecore_2.2.0.v200606271057.ja
r
 125210 14/09/06 14:26 plugins/org.eclipse.emf.edit.ui_2.2.0.v200606271057.
jar
 225067 14/09/06 14:26 plugins/org.eclipse.emf.edit_2.2.0.v200606271057.jar

 748073 14/09/06 14:26 plugins/org.eclipse.gef_3.2.0.v20060626.jar
 91656 14/09/06 14:26 plugins/org.eclipse.jem.util_1.2.0.v20060530_RC2.jar

 35071 14/09/06 14:26 plugins/org.eclipse.wst.common.core_1.1.0.v200606130
645.jar
 182926 14/09/06 14:26 plugins/org.eclipse.wst.common.emf_1.1.0.v2006061306
45.jar
 122035 14/09/06 14:26 plugins/org.eclipse.wst.common.emfworkbench.integrat
ion_1.1.0.v200606130645.jar
 37662 14/09/06 14:26 plugins/org.eclipse.wst.common.environment_1.0.100.v
200606130645.jar
 123058 14/09/06 14:26 plugins/org.eclipse.wst.common.frameworks.ui_1.1.0.v
200606130645.jar
 106267 14/09/06 14:26 plugins/org.eclipse.wst.common.frameworks_1.1.0.v200
606130645.jar
 162102 14/09/06 14:26 plugins/org.eclipse.wst.common.project.facet.core_1.
1.0.v200606130645.jar
 102255 14/09/06 14:26 plugins/org.eclipse.wst.common.ui.properties_1.0.100
.v200606130645.jar
 119099 14/09/06 14:26 plugins/org.eclipse.wst.common.ui_1.1.0.v20060614212
2.jar
 31779 14/09/06 14:26 plugins/org.eclipse.wst.common.uriresolver_1.1.0.v20
0606130645.jar
 367107 14/09/06 14:26 plugins/org.eclipse.wst.sse.core_1.1.0.v200606141450
.jar
 670902 14/09/06 14:26 plugins/org.eclipse.wst.sse.ui_1.0.101.v200606191900
.jar
 96453 14/09/06 14:26 plugins/org.eclipse.wst.validation.ui_1.1.0.v2006061
30645.jar
 184914 14/09/06 14:26 plugins/org.eclipse.wst.validation_1.1.0.v2006061306
45.jar
 603544 14/09/06 14:26 plugins/org.eclipse.wst.xml.core_1.1.0.v200606142000
.jar
 646889 14/09/06 14:26 plugins/org.eclipse.wst.xml.ui_1.0.100.v200606141450
.jar
 61015 14/09/06 14:26 plugins/org.eclipse.wst.xsd.core_1.1.0.v200606130645
.jar
 918340 14/09/06 14:26 plugins/org.eclipse.wst.xsd.ui_1.1.0.v200606142122.j
ar
 197009 14/09/06 14:26 plugins/org.eclipse.xsd.edit_2.2.0.v200606271057.jar

 697947 14/09/06 14:26 plugins/org.eclipse.xsd_2.2.0.v200606271057.jar
 636 14/09/06 14:55 plugins/org.jbpm.gd.jpdl.help_3.0.11.jar
 754909 14/09/06 14:55 plugins/org.jbpm.gd.jpdl.ui_3.0.11.jar
 1960 14/09/06 14:26 readme.html
 282 14/09/06 14:26 site.xml
 -------- -------
 10372958 39 files

Do I need to manually install something on eclipse before installing the designer?

Regards and thanks for anwering.

[mteira]

About the problem deploying in JBoss 4.0.4 GA the jbpm.ear with the provided application.xml , it was:

12:41:54,945 INFO [EARDeployer] Init J2EE application: file:/opt/jboss/server/oracluster/deploy/jbpm.ear
12:41:54,972 ERROR [MainDeployer] Could not initialise deployment: file:/opt/jboss/server/oracluster/deploy/jbpm.ear
org.jboss.deployment.DeploymentException: Invalid module content, must be one of: ejb, web, java, connector, service, har,
 at org.jboss.deployment.J2eeModuleMetaData.importXml(J2eeModuleMetaData.java:166)
 at org.jboss.deployment.J2eeModuleMetaData.importXml(J2eeModuleMetaData.java:107)
 at org.jboss.deployment.J2eeApplicationMetaData.importApplicationXml(J2eeApplicationMetaData.java:178)
 at org.jboss.deployment.J2eeApplicationMetaData.importXml(J2eeApplicationMetaData.java:139)
 at org.jboss.deployment.EARDeployer.init(EARDeployer.java:141)
 at org.jboss.deployment.MainDeployer.init(MainDeployer.java:861)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:798)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
 at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy6.deploy(Unknown Source)
 at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
 at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:417)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy4.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
 at $Proxy5.deploy(Unknown Source)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
 at org.jboss.Main.boot(Main.java:200)
 at org.jboss.Main$1.run(Main.java:464)
 at java.lang.Thread.run(Thread.java:595)
12:41:54,986 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@4e9bcc36 { url=file:/opt/jboss/server/oracluster/deploy/jbpm.ear }
 deployer: org.jboss.deployment.EARDeployer@9c2715
 status: null
 state: FAILED
 watch: file:/opt/jboss/server/oracluster/deploy/jbpm.ear
 altDD: null
 lastDeployed: 1158316914971
 lastModified: 1158316914000
 mbeans:

And that's why I changed it to a web tag with its context-root.

Any idea about my problem with the designer compressed site? Is it missing something?

Thanks a lot.