We may be missing a few log statements there.
Anyway, to handle the error in a specific way, you can implement your
own marshaler and configure it instead of the default one. You will
be able to override the code used to send the error.
On Wed, Jun 11, 2008 at 10:54 AM, pratibhaG <[EMAIL PROTECTED]> wrote:
>
> I modified the configuration as per your suggestion. Now I get following on
> the SMX log:
>
> DEBUG - JettyContextManager - Dispatching job:
> [EMAIL PROTECTED],io=0,w=true,b=false|false]
> DEBUG - JettyContextManager - Dispatching job:
> [EMAIL PROTECTED],io=1,w=true,b=false|false]
> DEBUG - JAASAuthenticationService - Authenticating 'smx' with 'smx'
> DEBUG - HttpComponent - Receiving HTTP request: POST
> /example/ HTTP/1.1
> Authorization: Basic c214OnNteA==
> User-Agent: Jakarta Commons-HttpClient/3.1
> Host: localhost:8192
> Content-Length: 179
>
>
> DEBUG - HttpComponent - Created correlation id:
> ID:192.168.2.64-11a7656b905-17:9
> DEBUG - DeliveryChannelImpl - Send
> ID:192.168.2.64-11a7656b905-17:9 in DeliveryChannel{servicemix-http}
> DEBUG - JettyContextManager - Dispatching job:
> [EMAIL PROTECTED],io=1,w=true,b=false|false]
> DEBUG - JettyContextManager - Dispatching job:
> [EMAIL PROTECTED],io=1,w=true,b=false|false]
>
> What is parameter in the logs which says that the user is not authorized?
> Now how can I take any action. Suppose I want to send some meaningfull
> message to user. Then how can I do that.
>
> -Pratibha
> --
> View this message in context:
> http://www.nabble.com/How-to-handle-unauthorized-user-tp17771342p17773046.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
