3 Replies Latest reply on Jan 2, 2006 4:48 PM by aguizar

    When will jbpm-bpel-1.0-alpha-4 release?

    fwshk

      Excuse me,

      Would anyone like to tell me the release day of jbpm-bpel-1.0-alpha-4 ?
      I have posted http://www.jboss.com/index.html?module=bb&op=viewtopic&t=74470 some questions and waiting the new release as the reply.
      Time is running, Please notify me if it is not going to release in few days.

      In the past 2 days, I have written some code to deploy BPEL process automatically.
      In my code, it is possible to generate almost all files which are required for the deployment.
      I would like to know, will jBPM include such funcation in the future?

      My code require user to input:
      - Log4j Configure File Path (log4j.properties)
      - Hibernate Configure File Path (hibernate.cfg.xml)
      - Hibernate Configure Property File Path (hibernate.properties)
      - WSCompiler Home Folder (C:/Sun/jwsdp-1.6/)
      - Definition Folder (The folder contains the definition files)
      - Build Folder (The folder to be contain all generated files)
      - A Set Definition Filename (*.bpel, *.wsdl ...)
      - Output Definition Par Filename (*.par)
      - Output WSCompile Configure Filename (wscompile-cfg.xml)
      - Output Java Type Mapping Filename (jaxrpc-mapping.xml)
      - Output Web War Filename (*.war)
      - Output Client Jar Filename (*-client.jar)
      - Output Application Ear Filename (*-application.ear)
      - Deploy Hostname (localhost)
      - Deploy Host Port (8080)

      And the user only provide the below files:
      - log4j.properties
      - hibernate.cfg.xml
      - hibernate.properties
      - *.bpel
      - *.wsdl
      - bpel-definition.xml

      Then my program will generate all other files
      and the final output is the *-application.ear which can be deploy directly

      The problem is I just write the code very quick,
      that not really parse the *.bpel, *.wsdl and bpel-definition.xml
      I make many assumption in my code.

      A BPEL and WSDL reader is required if the generation need to better.
      A similar reader is already existing exist in jBPM BPEL
      which used in deploy-definition and generate-service.

      What I am going to say is will jBPM BPEL generate the deployment files in future?
      It is only required to make some modify of exist reader to provide other output.
      And the feature will make jBPM BPEL more user-friendly.

      Is my thinking is correct?
      Is it not possible or not recommend to generate deployment files?
      Please correct me if anything is wrong.

      Thank you very much again ^^
      Roy

        • 1. Re: When will jbpm-bpel-1.0-alpha-4 release?
          fwshk

          I miss something in the input of my auto deployment program
          It also require the mapping of partnerLinkName and the WSDL location

          For example:
          sessionFactory -> http://localhost:8080/session/sessionFactory?wsdl

          • 2. jBPM BPEL 1.0 alpha 4 released!!
            aguizar

            jBPM BPEL 1.0 alpha 4 is now available at
            sourceforge.
            The link in the JBoss jBPM downloads page still points to the previous person. We'll fix that shortly.

            • 3. Re: When will jbpm-bpel-1.0-alpha-4 release?
              aguizar

              A design goal of the BPEL extension was to leverage as much of JEE web services as possible. WS4EE in turn leverages a lot from servlets.

              While you are right in that most artifacts are amenable for automatic generation, I didn't want to hide them from the experienced developer who knows her way around the servlet/web service deployment descriptors.

              On the other hand, I agree that the amount of artifacts is not friendly to the new user. She prefers to enter the minimal required data and accept sensible defaults for the remaining settings. We are definitely interested in offering such a feature.

              Would you want to contribute your code? We could adapt the existing BPEL and WSDL readers to produce whatever output that is needed.