[jira] Issue Comment Edited: (SM-1603) Develop cxf-bc provider/cxf-bc consumer/cxf-se test cases to verify expected results over all 8 mtomEnabled property permutations

["Ron Gavlin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46089#action_46089 ] 

rgavlin edited comment on SM-1603 at 9/30/08 11:47 PM:
----------------------------------------------------------

Hi Freeman,

I don't think it is reasonable to "couple" the mtomEnabled flag for these individual, de-coupled endpoints. Rather, I think the behavior for all 8 legitimate permutations of mtomEnabled configurables should be at least understood and exercised in a test case. 

In our environment, the person writing the smx-cxf-se is usually a different person than the one responsible for writing the smx-cxf-bc consumer that exposes it outside the bus. There is then a third person who would be writing the smx-cxf-bc provider that interacts with the smx-cxf-bc consumer or even the smx-cxf-se directly. 

Since the mtomEnabled flag is configurable on each endpoint, and since it is configured independent of the wsdl and therefore not formally published, it seems reasonable to expect that all 8 permutations would be handled gracefully. Of course, mtom would be leveraged where appropriately configured as strictly an optimization technique.

Ron

      was (Author: rgavlin):
    Hi Freeman,

I don't think it is reasonable to "couple" the mtomEnabled flag for these individual, de-coupled endpoints. Rather, I think the behavior for all 8 legitimate permutations of mtomEnabled configurables should be at least understood and exercised in a test case. 

In our environment, the person writing the smx-cxf-se is usually a different person than the one responsible for writing the smx-cxf-bc consumer that exposes it outside the bus. There is a third person would be writing the smx-cxf-bc provider that interacts with the smx-cxf-bc consumer. Since the mtomEnabled flag is configurable on each endpoint, and since it is configured independent of the wsdl and therefore not formally published, it seems reasonable to expect that all 8 permutations would be handled gracefully, of course, leveraging mtom where appropriate as strictly an optimization technique.

Ron
  
> Develop cxf-bc provider/cxf-bc consumer/cxf-se test cases to verify expected results over all 8 mtomEnabled property permutations 
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1603
>                 URL: https://issues.apache.org/activemq/browse/SM-1603
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-cxf-bc, servicemix-cxf-se
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>


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