You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2007/04/17 23:18:15 UTC

[jira] Created: (CXF-542) Support the factory pattern using a single stateless service endpoint

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



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.


[jira] Updated: (CXF-542) Support the factory pattern using a single stateless service endpoint

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ 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.r530748.patch

update to revision 5307

remove code duplication in ContextUtils, use EndpointReferenceUtils instead. Use Names constants through out. tx Eoghan.

> 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, multiplex-cxf-542.r530748.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.


[jira] Closed: (CXF-542) Support the factory pattern using a single stateless service endpoint

Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bozhong Lin closed CXF-542.
---------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-RC

> 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
>             Fix For: 2.0-RC
>
>         Attachments: multiplex-cxf-542.1.patch, multiplex-cxf-542.patch, multiplex-cxf-542.r530748.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.


[jira] Updated: (CXF-542) Support the factory pattern using a single stateless service endpoint

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Updated: (CXF-542) Support the factory pattern using a single stateless service endpoint

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ 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.patch

This patch implements support for Multiplex Addressing on a CXF transport using WS-A and using address context for HTTP as a config option.
The implementation is system test driven rather than unit test dirven so the unit test coverage still needs some work, for example MAPCodecTest needs a refactor to test the inclusion of reference parameters.  

Of interest is the change to support ServiceImpl.getPort(EndpointReferenceType) by replacing the use of string address in EndpointInfo with an instance of an EndpointReferenceType. This saves on duplication but incurs a small overhead. The filtering of this endpoint info down to the conduits is also worth a look to see if  it is done correctly.

the factory_pattern system test demonstrates the functionality.



> 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.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.