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

Torsten Mielke updated SM-1367:
-------------------------------

    Description: 
When using authorization in SMX there is no way to retrieve any logging of the 
authorization function as there are no logging statements in the code. However 
there should be some. Unless one connects with a debugger to SMX, there is no 
way of figuring out if authorization function is called. In the case of 
authorization failing, it correctly raises exceptions, but in case it succeeds, 
one can not get any further logging.
Please add some useful logging statements in this area. 


  was:
When using authorization in FUSE ESB there is no way to retrieve any logging of 
the authorization function as there are no logging statements in the code. 
However there should be some. Unless one connects with a debugger to FUSE ESB, 
there is no way of figuring out if authorization function is called. In the 
case of authorization failing, it correctly raises exceptions, but in case it 
succeeds, one can not get any further logging.
Please add some useful logging statements in this area. 



> Provide logging statements when doing authorization in SMX
> ----------------------------------------------------------
>
>                 Key: SM-1367
>                 URL: https://issues.apache.org/activemq/browse/SM-1367
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-core
>    Affects Versions: 3.2.1
>            Reporter: Torsten Mielke
>            Priority: Minor
>
> When using authorization in SMX there is no way to retrieve any logging of 
> the authorization function as there are no logging statements in the code. 
> However there should be some. Unless one connects with a debugger to SMX, 
> there is no way of figuring out if authorization function is called. In the 
> case of authorization failing, it correctly raises exceptions, but in case it 
> succeeds, one can not get any further logging.
> Please add some useful logging statements in this area. 

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

Reply via email to