ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: ReliableMessaging support?
Date Fri, 18 Apr 2008 20:03:29 GMT
Then it will require custom code to support WS-RM.   When we get to it,
we'll try to provide a configurable handler so you can write your own or
customize the default ones.

alex


On Wed, Apr 16, 2008 at 3:36 PM, Sukma Agung Verdianto <save.nx@gmail.com>
wrote:

> Hi Alex,
> Thanks for your quick response,
> Sandesha2 require an option to be set before last invocation, the name is
> LAST_MESSAGE option, this will indicate that the message is the last
> message
> transmitted in current exchange.
> Please take a look at sandesha2 example on
> http://ws.apache.org/sandesha/sandesha2/userGuide.html#one_way and
> http://ws.apache.org/sandesha/sandesha2/userGuide.html#request_reply
>
> Regards,
> Sukma
>
> On Thu, Apr 17, 2008 at 5:06 AM, Alex Boisvert <boisvert@intalio.com>
> wrote:
>
> > Sukma,
> >
> > It would be nice to see what you had to code to use WS-RM that couldn't
> be
> > expressed in Axis2's service configuration file.
> >
> > Point #2 is a fallback mechanism, I don't believe it's going to apply to
> > all
> > modules if #1 didn't suffice.
> >
> > alex
> >
> >
> > On Wed, Apr 16, 2008 at 3:00 PM, Sukma Agung Verdianto <
> save.nx@gmail.com>
> > wrote:
> >
> > > Hi Alex,
> > > I have been trying to invoke WS-RM service with Axis2, and it is not
> > > possible without adding some code to set options to the ServiceClient.
> > >
> > > Will your 2nd point works with other Axis2 modules such as addressing
> > > (ws-addressing) and rampart (ws-security)?
> > > I mean, That will be great if the configuration handler will also
> works
> > > with
> > > other Axis2 modules, so we can take a lot of advantages of Axis2
> > modules?
> > >
> > > Regards,
> > > Sukma
> > >
> > > On Thu, Mar 27, 2008 at 8:29 PM, Alex Boisvert <boisvert@intalio.com>
> > > wrote:
> > >
> > > > (I'm moving the discussion on the dev list; please remove the user
> > list
> > > > from
> > > > CC: if you reply to this message)
> > > >
> > > > Hi Harry,
> > > >
> > > > At this time, Ode doesn't have any facility for external endpoint
> > > specific
> > > > configuration.
> > > >
> > > > Roughly speaking, there's two ways that can be done with Axis2,
> > > >
> > > > 1) Load a specific ConfigurationContext per external endpoint
> > > (axis2.xml,
> > > > perhaps named according to the external service's name to avoid
> > clashes)
> > > > 2) Configure partnerLink bindings in deploy.xml, pass this
> > configuration
> > > > during the invoke, and have some kind of configuration handler(s)
> set
> > > the
> > > > various options on ServiceClient.
> > > >
> > > > Both require changes in ExternalService.  The first one is probably
> > > > quicker
> > > > (a few hours' work) and more general.  The second allows for custom
> > code
> > > > and
> > > > very specific configuration to happen on the endpoint, some of which
> > may
> > > > not
> > > > be possible through axis2.xml.  I'm guessing the latter would
> require
> > a
> > > > 2-3+
> > > > days to put all the necessary infrastructure in place.
> > > >
> > > > Have you been successful invoking WS-RM services by using only
> > > > axis2.xmlconfiguration on the client?  Or did it require some
> > > > hand-coding to set
> > > > options on the ServiceClient?   I can probably whip out the first
> > > > implementation during the next week.  Alexis Midon is also working
> in
> > > this
> > > > area at the moment so he might want to chime in...
> > > >
> > > > alex
> > > >
> > > >
> > > > On Wed, Mar 26, 2008 at 8:53 PM, Harry Moyer <
> harry.moyer@redwahoo.com
> > >
> > > > wrote:
> > > >
> > > > > I am hoping that Alex can qualify and quantify what you meant by
> the
> > > > > words "some coding" in the statement below:
> > > > >
> > > > > "but it's not possible to call services requiring WS-RM without
> some
> > > > > coding"
> > > > >
> > > > > We have done a lot of Axis2 development to get Reliable Messaging
> > and
> > > > > Security policy assertions to first work and then interoperate
> > between
> > > > > two Axis2 endpoints.
> > > > >
> > > > > A best case scenario would be to integrate these policy assertions
> > > > > within an ODE/Axis2 environment.
> > > > >
> > > > > Thanks in advance for your assistance.
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Harry Moyer
> > > > > Red Wahoo
> > > > >
> > > > >
> > > > > "Tue, 05 Feb 2008 15:39:14 GMT
> > > > >
> > > > > Hi Sukma,
> > > > >
> > > > > At this time, ReliableMessaging support is not complete in Ode.
> > > > > Process
> > > > > endpoints may be exposed with WS-RM support, but it's not possible
> > to
> > > > > call
> > > > > services requiring WS-RM without some coding.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

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