11 Replies Latest reply on Dec 3, 2007 6:10 PM by Alejandro Guizar

    JBoss jBPM - BPeL - eclipse

    Tina Kleb Newbie

      Hi,
      I got the following specifications to use for creating a Web Application:
      JBoss jBPM
      BPeL
      Eclipse

      So I downloaded JBoss jBPM, eclipse 3.3 and the plugin for BPeL via the update-site http://download.eclipse.org/technology/bpel/update-site/
      For JBoss jBPM I got jbpm-jpdl-3.2.2.
      Starting the server via the console run.bat -c jbpm works and I am able to have a look at http://localhost:8080/jbpm-console/sa/processes.jsf

      When I created a BPEL 2.0-Project (I choose BPEL-Project and not JBoss jBPM Project because a JBoss jBPM Project works with jPDL) in eclipse I am able to draw a diagram but I am not able to create a server by right clicking in the server window and selecting New, Server, JBoss v3.2.3.
      When I choose the jdk and point the Application Server Directory to C:\jboss\jbpm-jpdl-3.2.2 I will get the error Missing classpath entry C:\jboss\jbpm-jpdl-3.2.2\bin\run.jar.
      When I point it to C:\jboss\jbpm-jpdl-3.2.2\server\server I will get the error Missing classpath entry C:\jboss\jbpm-jpdl-3.2.2\server\server\default\lib\javax.servlet.jar.

      Why does eclipse look for the default directory of JBoss?
      The file javax.servlet.jar is located in C:\jboss\jbpm-jpdl-3.2.2\server\client

      Does somebody know something?

      Thanks, Tina

        • 1. Re: JBoss jBPM - BPeL - eclipse
          Agustín Gañan Newbie

          Maybe you could start reading this post.
          http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106514#4106514
          I will wait your questions in the forum
          Good luck

          • 2. Re: JBoss jBPM - BPeL - eclipse
            Tina Kleb Newbie

            Thanks a lot for the link!

            I started to create a project like the demo does. The first step is not a problem but when trying to download the wsdl-files I will get the following eclipse-error:
            IWAB0135E An unexpected error has occurred.
            UDDIException
            (502)Proxy Error


            Do I have to change some properties of eclipse?

            Besides there is an other question:
            Is it possible to see the deployed process on the console?

            Thanks, Tina

            • 3. Re: JBoss jBPM - BPeL - eclipse
              Agustín Gañan Newbie

              Hi Tina,
              It seems to be an error in your proxy configuration, not eclipse but I'm not sure.
              There is another way to get the wsdl (my way, :-)).
              Using your web browser (Mozilla, Internet Explorer) go to the web service page an save the wsld in your local system.
              Here
              http://www.xmethods.net/ve2/Directory.po;jsessionid=4XUrFKQiN3_SA1yBd80-LqLJ(QHyMHiRM)
              there are some services to start. Click on the service name and then follow the WSDL link.
              It goes to the WSDL declaration of the service, then you save this page where you want.
              Be carefull with the file extension, my browser put .xml by default, and the wsdl must be .wsdl and first of all check if the web service works, there are some of them that are offline.

              When you say:

              Is it possible to see the deployed process on the console?

              What do you mean? only the bpel process or the bpel process as a web service?

              I hope that it helps you,

              Agus

              • 4. Re: JBoss jBPM - BPeL - eclipse
                ARM Newbie

                hi
                You most change E:\jbpm-jpdl-3.2.2\server\server\jppm to jbpm-jpdl-3.2.2\server\server\default

                and in start.bat :

                run.bat -c jbpm

                to

                run.bat -c default

                • 5. Re: JBoss jBPM - BPeL - eclipse
                  Tina Kleb Newbie

                  Hi,

                  thanks for your help but now eclipse is looking for C:\jboss\jbpm-jpdl-3.2.2\server\lib\jboss-boot.jar.

                  • 6. Re: JBoss jBPM - BPeL - eclipse
                    Agustín Gañan Newbie

                    Your are trying to deploy the bpel process from Eclipse??
                    I think that it is no possible by the moment, you should follow the user guide.

                    Agus

                    • 7. Re: JBoss jBPM - BPeL - eclipse
                      Tina Kleb Newbie

                      Hi Agus,

                      I have a lot of questions probably depending on the fact that I am new at BPEL and JBoss.
                      First of all:
                      Where do you know all the JBoss details from?

                      When I tried to download the wsdl-file from http://www.xmethods.net/ve2/Directory.po;jsessionid=4XUrFKQiN3_SA1yBd80-LqLJ(QHyMHiRM) as you told me I did not know which one to choose because I thought I need a wsdl-file fitting to the bpel I wrote.

                      Regarding deploying bpel from eclipse:
                      In case it is not possible what does the demo http://pluto.researchstudio.at/ibpm/bpel/deploy_process.htm show?
                      Reading the user guide to get to know how to deploy a process I looked at this one http://docs.jboss.com/jbpm/v3/userguide/deployment.html which I do not understand. Do I have to add the jar-files to my java-project? Do I have to change the properties of the file build.properties? How comes the deployed process to my server-directory?

                      Is it possible to deploy the process with eclipse?

                      Please can you give me some hints because I have no more ideas to continue.
                      Tina

                      • 8. Re: JBoss jBPM - BPeL - eclipse
                        Agustín Gañan Newbie

                        Hi Tina,
                        I try to answer your question, ok?
                        1.- My knowledge of Jboss&BPEL cames to the experience of using it.
                        2.- You are reading the jbpm user guide, not BPEL user guide. Try to start with this one:
                        http://docs.jboss.com/jbpm/bpel/
                        Read this guide an this one, is a good point to start.
                        http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmBpelDesigner
                        3.- The deployment of bpel process from eclipse is not possible, you have to run the ant task.
                        My advice, start with a very simple process (like the bonjour process in the wiki guide) and then try something more complex.
                        I'm using the jboss server 4.05, the bpel extension 1.1Beta3 and the bpel plugin for eclipse 0.2.

                        I hope this can help you,

                        Regards

                        Agus

                        • 9. Re: JBoss jBPM - BPeL - eclipse
                          Tina Kleb Newbie

                          Hi Agus,

                          I thank you a lot for the hints. I now unserstand a lot more but I have new problems:
                          When calling ant deploy-definition in the directory examples/hello I get the following error:

                          BUILD FAILED
                          C:\downloads\jbpm-bpel-1.1.Beta3\jbpm-bpel-1.1.Beta3\jbpm-bpel-1.1.Beta3\example
                          s\common\bpel-build.xml:60: deployment failed, see details in the server console

                          The server console says
                          13:53:01,921 ERROR [[processDeployServlet]] Servlet.service() for servlet processDeployServlet threw exception
                          java.lang.AbstractMethodError: org.jbpm.bpel.xml.ArchiveWsdlLocator.close()V
                           at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2339)
                           at org.jbpm.bpel.xml.BpelReader.readWsdlDocument(BpelReader.java:420)
                           at org.jbpm.bpel.par.DefDescriptorArchiveParser.readDocuments(DefDescriptorArchiveParser.java:102)
                           at org.jbpm.bpel.par.DefDescriptorArchiveParser.readFromArchive(DefDescriptorArchiveParser.java:59)
                           at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:81)
                           at org.jbpm.bpel.web.ProcessDeployServlet.doGet(ProcessDeployServlet.java:50)
                           at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
                           at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
                           at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
                           at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                           at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
                           at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
                           at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                           at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
                           at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
                           at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
                           at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
                           at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
                           at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
                           at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
                           at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
                           at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
                           at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
                           at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
                           at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
                           at java.lang.Thread.run(Thread.java:619)


                          Do you have an idea what the problem is?

                          Thanks Tina

                          • 10. Re: JBoss jBPM - BPeL - eclipse
                            Agustín Gañan Newbie

                            I have had lots of BPEL exceptions but never one like this. What are you doing?????:-)

                            Are you following the tutorial steps?
                            What version of JBoss AS are installed in your computer?
                            What version of BPEL extension do you have?
                            Maybe if you post your code, I can see it and help you.

                            My advice,

                            Don't give up

                            Agus

                            • 11. Re: JBoss jBPM - BPeL - eclipse
                              Alejandro Guizar Master

                              Tina,

                              I'm guessing you downloaded JBoss AS 4.2.0 or later, which is not compatible with jBPM BPEL 1.1.Beta3. I'd suggest to upgrade to the newly released jBPM BPEL 1.1.GA.

                              If you care about the details, version 1.1.Beta3 was written against version 1.4 of WSDL4J. This is the WSDL4J version included with JBoss AS 4.0.5.

                              In JBoss AS 4.2.0 and later, WSDL4J was upgraded to version 1.6. Among other changes, method close() was added to interface javax.wsdl.xml.WSDLLocator. This change broke jBPM BPEL 1.1.Beta3 because class org.jbpm.bpel.xml.ArchiveWsdlLocator no longer implemented all methods of the previously mentioned interface.