ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matthieu.r...@gmail.com>
Subject Re: URL Based Dispatching
Date Wed, 09 May 2007 00:10:24 GMT
I see, and I guess switching to rpc/lit isn't an option either... You can
actually try what you suggested, configuring RESTish URLs. Normally we get
the operation and service from Axis2 so if you use their routing it could
work. However this has never been tested so theory and practice could
diverge.

Matthieu

On 5/8/07, Vipul Sabhaya <vipulsabhaya@hotmail.com> wrote:
>
> 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?
> Thanks.
>
>
>
>
> >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 ([140.211.11.2]) 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) (140.211.11.133)
> >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 66.249.82.234 as permitted sender)
> >Received: from [66.249.82.234] (HELO wx-out-0506.google.com )
> >(66.249.82.234)    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 10.90.78.9 with SMTP id a9mr7020449agb.1178666519230;
> >Tue, 08 May 2007 16:21:59 -0700 (PDT)
> >Received: by 10.90.88.9 with HTTP; Tue, 8 May 2007 16:21:59 -0700 (PDT)
> >X-Message-Info:
> >LsUYwwHHNt3660MmjhEvYg2f34OAemlK+ZzoV09lDsZmbz8QigGIQtU5Yvr3lK0P
> >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
> >required=10.0tests=HTML_MESSAGE,SPF_PASS,URIBL_OB_SURBL
> >X-Spam-Check-By: apache.org
> >DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;        d=gmail.com;
> s=beta;
> >
> >h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
>
> >
>
> >b=ABDHEl5Ml/87Fevd6A36G2vyDiZ9BNu1xyRTaqH+PyKlgRbFpWFpBe/vcvIu2yrFhuNlgT27N8viqQ0Cml6Z7JoCSRjgzHCrryLFZ1me2u1hZ0NpnHdjSD9pd16wMMutXqzPxr1pgTmRY4YFslusSFJiYjzlUCpHqNIfFt7yL8w=
> >DomainKey-Signature: a=rsa-sha1; c=nofws;        d= gmail.com; s=beta;
> >
>
> >h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
> >
> >b=HKoS2/uiS+xw7gSuP6JjMyvAIa6jAEWtJbHFNDNOgD1qZZERYkG7UYeCZFny+GRZ9BU7s1x8MtoDeFK+FBaat9NnGJfZ5o4Ti3Fb1VgKUDf9W2Zr6WhHSehTUhzLu3fbOiaZeVcvOwnXSWS706RuUYxV7Wfuxq7ATTzy6QP/obk=
>
> >References: <BAY118-F38CC740D2A71269AC1823ED8440@phx.gbl>
> >X-Virus-Checked: Checked by ClamAV on apache.org
> >Return-Path:
> >ode-user-return-532-vipulsabhaya=hotmail.com@incubator.apache.org
> >X-OriginalArrivalTime: 08 May 2007 23:22:22.0031 (UTC)
> >FILETIME=[BAB545F0:01C791C7]
> >
> >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
> >binding,
> >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
> >responder
> >process has 2 receives with 2 different operations:
> >
> >http://svn.apache.org/repos/asf/incubator/ode/trunk/distro-axis2/src/examples/DynPartner/
>
> >
> >Cheers,
> >Matthieu
> >
> >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:
> >>
> >><ip:port>/axis2/services/<serviceName>/<operationName>
> >>
> >>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
> >>operation.
> >>
> >>Thanks.
> >>
> >>_________________________________________________________________
> >>See what you're getting into…before you go there
> >>http://newlivehotmail.com/?ocid=TXT_TAGHM_migration_HM_viral_preview_0507
>
> >>
> >>
>
> _________________________________________________________________
> PC Magazine's 2007 editors' choice for best Web mail—award-winning Windows
> Live Hotmail.
>
> http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message