Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <20303694.1176989655914.JavaMail.jira@brutus>
Date: Thu, 19 Apr 2007 06:34:15 -0700 (PDT)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Updated: (CXF-542) Support the factory pattern using a
 single stateless service endpoint
In-Reply-To: <16365106.1176844695634.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated CXF-542:
---------------------------

    Attachment: multiplex-cxf-542.1.patch

update: modification to getEndpointReferenceId to simplify, allowing the runtime to provide the bus and destination from the MessageContext Map.
Added Destination as a a property to MessageImpl to make it available to the runtime.

> Support the factory pattern using a single stateless service endpoint 
> ----------------------------------------------------------------------
>
>                 Key: CXF-542
>                 URL: https://issues.apache.org/jira/browse/CXF-542
>             Project: CXF
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Gary Tully
>         Attachments: multiplex-cxf-542.1.patch, multiplex-cxf-542.patch
>
>
> provide support fo the features described at http://mail-archives.apache.org/mod_mbox/incubator-cxf-dev/200704.mbox/%3c1D195F515BDFE04EA40FA8D046308D6A0302AB@emea-ems1.IONAGLOBAL.com%3e
> The factory pattern of statefull service interaction does not scale with webservices. However in the case of a single implementation endpoint where the state is embedded in the endpoint reference, it is possible to scale the factory pattern in a reasonable matter. the state embedded in the endpoint reference is used as a key into some persistent store that is used for the duration on the request dispatch.
> Support of this nature requires a mechanism to propagate state in an endpoint reference. ie: create an endpoint reference for an existing service with an embedded id, the option to retrieve the id at runtime from the current endpoint reference.
> For a client, an easy way to use an endpoint reference is required. Something like the jaxws2.0 service.getPort(endpointreferencetype...)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.