You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Alessio Soldano (JIRA)" <ji...@apache.org> on 2015/04/08 22:31:12 UTC
[jira] [Updated] (CXF-6335) Explicitly set HTTPConduit on client inbound message

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

Alessio Soldano updated CXF-6335:
---------------------------------
    Description: 
On client side, an instance of HTTPConduit is saved in the Message when the ConduitSelector is used on client (in particular, the prepare(Message message) method is called on the selector). That applies to the oubound message only, though. The inbound message is not explicitly linked to the conduit, untill something actually needs it (lazy approach), for instance the PolicyInVerificationInterceptor.
This is a problem as the selector clears the message context cache after having selected the conduit, which is a performance issue as we end up computing the cache twice for response messages. The conduit should be selected (actually copied from the outbound message) soon after having created the response inbound Message, to prevent double cache computing.

  was:
On client side, an instance of HTTPConduit is saved in the Message when the ConduitSelector is used on client (in particular, the prepare(Message message) method is called on the selector). That applies to the oubound message only, though. The inbound message is not explicitly linked to the conduit, untill something actually needs it (lazy approach), for instance the PolicyInVerificationInterceptor.
This is a problem as the selector clears the message context cache after having selected the conduit, which is a performance issue as we end up computing the cache twice for response messages. The conduit should be selected (actually copied from the outbound message) soon after having created the response inbound Message, to prevent double cache wiping.


> Explicitly set HTTPConduit on client inbound message
> ----------------------------------------------------
>
>                 Key: CXF-6335
>                 URL: https://issues.apache.org/jira/browse/CXF-6335
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-WS Runtime, Transports
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: 3.1.0, 3.0.5
>
>
> On client side, an instance of HTTPConduit is saved in the Message when the ConduitSelector is used on client (in particular, the prepare(Message message) method is called on the selector). That applies to the oubound message only, though. The inbound message is not explicitly linked to the conduit, untill something actually needs it (lazy approach), for instance the PolicyInVerificationInterceptor.
> This is a problem as the selector clears the message context cache after having selected the conduit, which is a performance issue as we end up computing the cache twice for response messages. The conduit should be selected (actually copied from the outbound message) soon after having created the response inbound Message, to prevent double cache computing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)