ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vipul Sabhaya" <vipulsabh...@hotmail.com>
Subject Re: URL Based Dispatching
Date Tue, 08 May 2007 23:51:46 GMT
Yes, this is the problem i'm facing -- I need the Elements to be the same in 
multiple operations, and i'm using Doc/Lit style.

I was hoping that there would be a way to specify the operation, without 
relying on the Element in the body.

Is there a way to do this?

>From: "Matthieu Riou" <matthieu.riou@gmail.com>
>Reply-To: matthieu.riou@gmail.com
>To: ode-user@incubator.apache.org
>Subject: Re: URL Based Dispatching
>Date: Tue, 8 May 2007 16:21:59 -0700
>MIME-Version: 1.0
>Received: from mail.apache.org ([]) by 
>bay0-mc3-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Tue, 8 
>May 2007 16:22:21 -0700
>Received: (qmail 11078 invoked by uid 500); 8 May 2007 23:22:27 -0000
>Received: (qmail 11069 invoked by uid 99); 8 May 2007 23:22:27 -0000
>Received: from herse.apache.org (HELO herse.apache.org) (    
>by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2007 16:22:27 -0700
>Received: pass (herse.apache.org: domain of matthieu.riou@gmail.com 
>designates as permitted sender)
>Received: from [] (HELO wx-out-0506.google.com) 
>(    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 
>2007 16:22:20 -0700
>Received: by wx-out-0506.google.com with SMTP id i26so6246wxd        for 
><ode-user@incubator.apache.org>; Tue, 08 May 2007 16:21:59 -0700 (PDT)
>Received: by with SMTP id a9mr7020449agb.1178666519230;        
>Tue, 08 May 2007 16:21:59 -0700 (PDT)
>Received: by with HTTP; Tue, 8 May 2007 16:21:59 -0700 (PDT)
>Mailing-List: contact ode-user-help@incubator.apache.org; run by ezmlm
>Precedence: bulk
>List-Help: <mailto:ode-user-help@incubator.apache.org>
>List-Unsubscribe: <mailto:ode-user-unsubscribe@incubator.apache.org>
>List-Post: <mailto:ode-user@incubator.apache.org>
>List-Id: <ode-user.incubator.apache.org>
>Delivered-To: mailing list ode-user@incubator.apache.org
>X-ASF-Spam-Status: No, hits=4.6 
>X-Spam-Check-By: apache.org
>DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;        d=gmail.com; s=beta;  

>DomainKey-Signature: a=rsa-sha1; c=nofws;        d=gmail.com; s=beta;       

>References: <BAY118-F38CC740D2A71269AC1823ED8440@phx.gbl>
>X-Virus-Checked: Checked by ClamAV on apache.org
>X-OriginalArrivalTime: 08 May 2007 23:22:22.0031 (UTC) 
>Hi Vipul,
>ODE doesn't route to a specific operation using the URL, AFAIK this looks
>more like a REST type of thing and doesn't really follow WS basic profile.
>Routing to an operation is performed using the message content.
>If your service has a document/literal binding, the message body should
>contain a single element under the body and this element should be the same
>one as declared for your part. If your service has an rpc / literal 
>the body should also contain a single element but in that case it should
>directly be the operation name (no namespace).
>In both cases, the routing will be performed correctly, either based on the
>element type or on the operation. The only restriction (as mentioned in
>basic profile) is that for doc/lit, your elements should all be different
>from one operation to another.
>Check the DynPartner example bundled with ODE, you'll see that the 
>process has 2 receives with 2 different operations:
>On 5/8/07, Vipul Sabhaya <vipulsabhaya@hotmail.com> wrote:
>>Does ODE support URL-based dispatching of webservices? -- according to the
>>Axis2 docs, they seem to support the following:
>>Where operationName can be put on the URL.  I am trying to write a BPEL
>>process that have 2 Receives, each receive is on a specific wsdl
>>See what you're getting into…before you go there

PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
Live Hotmail. 

View raw message