[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-j] NEW ISSUE: Redirecting callbacks
Actually I'm saying the exact opposite. If client A invokes service B
with a callback destination of C, the lifecycle of endpoint C should not
be tied in any way to the lifecycle of the callback endpoint for A. The
only tie should be between B's lifecycle and C's lifecycle. If B calls
direct to C, this goal is achieved. If B calls back to A and A forwards
the callback invocation to C, the lifecycle of A's callback endpoint is
tied to some combination of C's lifecycle and B's lifecycle.
Simon
Simon C. Nash, IBM Distinguished Engineer
Member of the IBM Academy of Technology
Tel. +44-1962-815156 Fax +44-1962-818999
"Patil, Sanjay" <sanjay.patil@sap.com>
30/01/2008 23:24
To
Simon Nash/UK/IBM@IBMGB, "OASIS Java" <sca-j@lists.oasis-open.org>
cc
Subject
RE: [sca-j] NEW ISSUE: Redirecting callbacks
Not sure I follow. Are you suggesting that the lifecycle of the endpoint
providing the callback interface should be tied up with the lifecycle
of the client component invoking the bidi interface. If yes, then this
concern should equally apply even when the callback invocation is not
redirected through the client component.
-- Sanjay
> -----Original Message-----
> From: Simon Nash [mailto:NASH@uk.ibm.com]
> Sent: Wednesday, Jan 30, 2008 15:08 PM
> To: OASIS Java
> Subject: RE: [sca-j] NEW ISSUE: Redirecting callbacks
>
> If the original callback endpoint isn't reachable, this won't work.
> Keeping an endpoint open indefinitely just in case a callback
> intended for
> a third party arrives at some future time seems lke a bad idea.
>
> Simon
>
> Simon C. Nash, IBM Distinguished Engineer
> Member of the IBM Academy of Technology
> Tel. +44-1962-815156 Fax +44-1962-818999
>
>
>
> "Patil, Sanjay" <sanjay.patil@sap.com>
> 30/01/2008 23:02
>
> To
> Simon Nash/UK/IBM@IBMGB, "OASIS Java" <sca-j@lists.oasis-open.org>
> cc
>
> Subject
> RE: [sca-j] NEW ISSUE: Redirecting callbacks
>
>
>
>
>
>
>
> I think it should still be possible for the original caller
> to disappear
> and the callback invocations be redirected to the registered object by
> the SCA runtime (on the caller side). Not sure I understand what would
> make it impossible.
>
> -- Sanjay
>
> > -----Original Message-----
> > From: Simon Nash [mailto:NASH@uk.ibm.com]
> > Sent: Wednesday, Jan 30, 2008 14:39 PM
> > To: OASIS Java
> > Subject: Re: [sca-j] NEW ISSUE: Redirecting callbacks
> >
> > We will have fun debating the resolution to this. I find the
> > idea of a
> > multi-hop forward to the real destination extremely unappealing.
> > Presumably the reason for the current words was that the
> > original caller
> > may no longer be available, so this change would nullify the
> > value of the
> > capability. Rather than reducing confusion, I think the
> change would
> > increase confusion because the semantics in the case that the
> > original
> > caller has gone away would no longer be well-defined. If we
> > think that
> > providing the currently specified facility is not
> desirable, I would
> > prefer to simply remove the ability to specify a service
> > reference as the
> > callback object.
> >
> > Simon
> >
> > Simon C. Nash, IBM Distinguished Engineer
> > Member of the IBM Academy of Technology
> > Tel. +44-1962-815156 Fax +44-1962-818999
> >
> >
> >
> > "Michael Rowley" <mrowley@bea.com>
> > 30/01/2008 20:13
> >
> > To
> > "OASIS Java" <sca-j@lists.oasis-open.org>
> > cc
> >
> > Subject
> > [sca-j] NEW ISSUE: Redirecting callbacks
> >
> >
> >
> >
> >
> >
> >
> > RAISER: Michael Rowley
> >
> > TARGET: Java Common Annotations and APIs, section 6.7.5
> > Customizing the
> > callback
> >
> > DESCRIPTION:
> >
> > The last paragraph of this section says:
> >
> > A callback object may be a service reference to another
> > service. In that
> > case, the callback messages go directly to the service that
> > has been set
> > as the callback. If the callback object is not a service
> > reference, then
> > callback messages go to the client and are then routed to the
> > specific
> > instance that has been registered as the callback object.
> > However, if the
> > callback interface has a stateless scope, then the callback
> > object must be
> > a service reference.
> >
> > The second sentence of this (saying that ?... callback messages go
> > directly...?) is overly constraining has complex and confusing
> > implications for runtimes.
> >
> > PROPOSAL:
> >
> > Remove the second sentence from this paragraph.
> >
> >
> >
> >
> >
> >
> >
> >
> > Unless stated otherwise above:
> > IBM United Kingdom Limited - Registered in England and Wales
> > with number
> > 741598.
> > Registered office: PO Box 41, North Harbour, Portsmouth,
> > Hampshire PO6 3AU
> >
> >
> >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail. You may a link to this group and all
> > your TCs in OASIS
> > at:
> > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> > oups.php
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all
> your TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php
>
>
>
>
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales
> with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth,
> Hampshire PO6 3AU
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all
> your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr
> oups.php
>
>
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]