2 Replies Latest reply on Feb 12, 2007 6:19 AM by pkovgan

    BPEL + WSIF

    pkovgan

      Hi!

      I have read 3 threads here and some blogs that try to explain some aspects of BPEL-Java coexistance and some pros and contros of attempt to exploit BPEL (below you can find those links) in WS free world...

      Anyway I want to ask simple question:

      Is it easy or not ( is it possible ) to "wrap" WS by WSIF right now in current version of JBPM-BPEL you have?
      I skip all performance problems now, I just want to know is it possible technically and is it hard(demands some modification of BPEL engine source or just modifications in WSDL?)?


      Thanks a lot!!





      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=88639

      http://jira.jboss.com/jira/browse/BPEL-135

      http://blogs.jboss.com/blog/tbaeyens/2006/03/17/To_BPEL_or_not_to_BPEL_that_is_the_question.txt

      http://blogs.jboss.com/blog/tbaeyens/2006/01/16/Simplified_BPM_for_Developers_One_process_language_is_not_enough.txt

      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82813





        • 1. Re: BPEL + WSIF
          aguizar

          Recalling the discussion in Native Java Code (POJO) Invocation incorporating WSIF is technically possible but has not been done so far. Apart from other priorities such as covering the BPEL specification and integrating with the designer, WSIF is a Java framework, intended to deal with Java objects, not XML info items.

          It is not clear to me what requirements WSIF would address. These days, with EJB3 and JSR-181/JAX-WS, it is trivial to turn a session bean or a plain object into a web service. Performance is another word that is mentioned. However, as explained in the topic referenced in the previous paragraph, the real performance hit comes from XML binding.

          From the perspective of a (standard) BPEL process having XML-typed variables, the best performing invocations occur with partners able to process XML directly or with minimal transformations, compared to partners that require complex binding to an object graph.

          Local vs. remote invocations are a separate issue outside the scope of the BPEL engine. It depends on the underlying web service implementation and network stack.

          If you could shred some light on what your requirements are for WSIF, it'd be great.

          • 2. Re: BPEL + WSIF
            pkovgan


            We do not have particular requirements to WSIF , but we are looking for "some way" to improve BPEngine-WS interop in light our performance and transaction requirements.

            As I understood so far WSIF (to be handled by Jbpm-Bpel) requires additional DOM-Java provider-serializer-bridge , that will not improve performance.
            So WSIF actually only turns things worse.

            We can't wait for http://jira.jboss.com/jira/browse/BPEL-135 to be implemented, so we will meanwhile research other opportunities.

            I 'm not adherent of this Bpel-plain java coexistence and I'll be happy to encourage my managers to probe other opportunities, but main problem is lack of other BP management "de-facto" standard....

            anyway, thanks for your answer.