I assume you are running the jboss that comes with the starter kit.
I believe you need to remove the jbpm.sar and jbpm.war. I think you see that error comes when both the jbpm.sar and the jbpm-bpel.sar are deployed.
Try that and see if you have better luck.
Otherwise you can use JBOSS 4.0.x. However, you may have to upgrade the jbossws.sar for versions under 4.0.5. But I am not 100% sure.
What I am working with:
JBPM: Both 3.1.4 and 3.2 beta (I have 2 installs for testing purposes)
JBOSS: 4.0.4 with upgraded jbossws
Thank you very much for replying.
1. If i remove jbpm.sar and jbpm.war, will jbpm thing work?
In the meanwhile i tried, installing
I am able to succesfully intergrate jboss+jbpm+jbpel, but when i deployed hello example that comes with jbpel package, when opened http://localhost:8080/hello/greeter
then in console it gave me error "HTTP Get not support"
What should I do to resolve this. I assume i need to upgrated jbosssws for this as you told.
I have replaced \jboss-4.0.4.GA\server\default\deploy\jbossws14.sar
with jboss 4.0.5 =>> jbossws14.sar
but still when i open http://localhost:8080/hello/greeter then i receive following message in browser
HTTP GET not supported
Bump... Newbie need help!
Yes the jbpm-bpel should support the existing jbpm. Currently I am at the same place you are, except I get a error querying the jbpm_processdefinitions table.
http://jira.jboss.com/jira/browse/BPEL-232 Seems to suggest a bug.
So I have helped you as far as I am able.
Thanks for replying.
Regarding my error "HTTP GET not supported", get method is not implemented in hello example, it is like that you need to deploy hello-client.jar and then need to post message from client.
I tried atm example also, it seem fine, i went till pressing "connect".
please learn the basics of soap before starting with webservices. SOAP uses HTTP POST, not GET, so it is normal to get the 'not supported' message
Try http://localhost:8080/hello/greeter?wsdl to get the WSDL document of the service directly to your browser and confirm the server is running.
A response of "GET not supported" instead of "404 not found" already indicates that the web service is up and running. As Ronald says, SOAP requires the POST method.
The J2EE client (hello-client.jar) is deployed automatically by the ant script before it runs the unit test. You don't need to deploy it manually. If you are running into problems, please post the stack trace and server log and we'll try to help.
So, now I want to know which versions of following
I should use get working my BPEL hello world example.
The user guide mentions that jBPM BPEL has been tested in JBoss AS 4.0.3.SP1, 4.0.4.GA and 4.0.5.GA in the default configuration.
jdk-1.4.2 and 1.5.0 both work well, provided you endorse the XML APIs as described in the manual.
Regarding jBPM, use the version that comes with the BPEL distribution. Again, the user guide explicitly says that you do not need to download jBPM separately because the required libraries are already provided.
The alpha series of jBPM BPEL used jBPM 3.0.x. The beta series used jBPM 3.1.x, except for the latest beta3 which already uses jBPM 3.2.beta1. Generally, you can replace the jBPM jars provided with the BPEL distribution with any version of the same branch, but only the bundled version has been tested.