You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2012/10/23 04:04:12 UTC

[jira] [Created] (SMXCOMP-951) refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property

Freeman Fang created SMXCOMP-951:
------------------------------------

             Summary: refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property
                 Key: SMXCOMP-951
                 URL: https://issues.apache.org/jira/browse/SMXCOMP-951
             Project: ServiceMix Components
          Issue Type: Improvement
          Components: servicemix-shared
            Reporter: Freeman Fang


AsyncBaseLifeCycle always calls processExchangeInTx regardless of exchange being in Transaction or not, though in processExchangeInTx code it covers both with or without Transaction cases,  this can still confuse end user in case of failure stack trace analysis. 
Should add another method like processExchangeWithoutTx which take care of no Transaction case, and  check if(tx == null) then call into different method in different cases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SMXCOMP-951) refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property

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

Freeman Fang resolved SMXCOMP-951.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2012.01

commit fix
http://svn.apache.org/viewvc?rev=1401142&view=rev
                
> refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-951
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-951
>             Project: ServiceMix Components
>          Issue Type: Improvement
>          Components: servicemix-shared
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2012.01
>
>
> AsyncBaseLifeCycle always calls processExchangeInTx regardless of exchange being in Transaction or not, though in processExchangeInTx code it covers both with or without Transaction cases,  this can still confuse end user in case of failure stack trace analysis. 
> Should add another method like processExchangeWithoutTx which take care of no Transaction case, and  check if(tx == null) then call into different method in different cases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (SMXCOMP-951) refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property

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

Freeman Fang reassigned SMXCOMP-951:
------------------------------------

    Assignee: Freeman Fang
    
> refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-951
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-951
>             Project: ServiceMix Components
>          Issue Type: Improvement
>          Components: servicemix-shared
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> AsyncBaseLifeCycle always calls processExchangeInTx regardless of exchange being in Transaction or not, though in processExchangeInTx code it covers both with or without Transaction cases,  this can still confuse end user in case of failure stack trace analysis. 
> Should add another method like processExchangeWithoutTx which take care of no Transaction case, and  check if(tx == null) then call into different method in different cases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Work started] (SMXCOMP-951) refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property

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

Work on SMXCOMP-951 started by Freeman Fang.

> refector AsyncBaseLifeCycle to avoid call into processExchangeInTx even the Exchange has no Transaction property
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-951
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-951
>             Project: ServiceMix Components
>          Issue Type: Improvement
>          Components: servicemix-shared
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>
> AsyncBaseLifeCycle always calls processExchangeInTx regardless of exchange being in Transaction or not, though in processExchangeInTx code it covers both with or without Transaction cases,  this can still confuse end user in case of failure stack trace analysis. 
> Should add another method like processExchangeWithoutTx which take care of no Transaction case, and  check if(tx == null) then call into different method in different cases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira