You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Hans G Knudsen (JIRA)" <ji...@apache.org> on 2007/06/19 14:41:26 UTC

[jira] Created: (RAMPART-49) RampartPolicyBuilder logs to console/System.out

RampartPolicyBuilder logs to console/System.out
-----------------------------------------------

                 Key: RAMPART-49
                 URL: https://issues.apache.org/jira/browse/RAMPART-49
             Project: Rampart
          Issue Type: Bug
          Components: rampart-core
    Affects Versions: 1.1, 1.2
            Reporter: Hans G Knudsen
             Fix For: 1.2, 1.3


RampartPolicyBuilder logs on System.out if it does not know the assertion class.

If you eg include a sandesha2:RMAssertion in your service policy - this will result in a lot of 'noice' in logfiles.

Proposal : 
    Write to log.debug instead




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


[jira] Updated: (RAMPART-49) RampartPolicyBuilder logs to console/System.out

Posted by "Hans G Knudsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hans G Knudsen updated RAMPART-49:
----------------------------------

    Attachment: policy_builder_logging.diff

changes System.out -> log.debug

> RampartPolicyBuilder logs to console/System.out
> -----------------------------------------------
>
>                 Key: RAMPART-49
>                 URL: https://issues.apache.org/jira/browse/RAMPART-49
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.1, 1.2
>            Reporter: Hans G Knudsen
>             Fix For: 1.2, 1.3
>
>         Attachments: policy_builder_logging.diff
>
>
> RampartPolicyBuilder logs on System.out if it does not know the assertion class.
> If you eg include a sandesha2:RMAssertion in your service policy - this will result in a lot of 'noice' in logfiles.
> Proposal : 
>     Write to log.debug instead

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


[jira] Resolved: (RAMPART-49) RampartPolicyBuilder logs to console/System.out

Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruchith Udayanga Fernando resolved RAMPART-49.
----------------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.2)

http://svn.apache.org/viewvc?view=rev&rev=553467

> RampartPolicyBuilder logs to console/System.out
> -----------------------------------------------
>
>                 Key: RAMPART-49
>                 URL: https://issues.apache.org/jira/browse/RAMPART-49
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.1, 1.2
>            Reporter: Hans G Knudsen
>             Fix For: 1.3
>
>         Attachments: policy_builder_logging.diff
>
>
> RampartPolicyBuilder logs on System.out if it does not know the assertion class.
> If you eg include a sandesha2:RMAssertion in your service policy - this will result in a lot of 'noice' in logfiles.
> Proposal : 
>     Write to log.debug instead

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