[
https://issues.apache.org/jira/browse/PIVOT-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508673#comment-13508673
]
Steven Swor edited comment on PIVOT-882 at 12/3/12 11:45 AM:
-------------------------------------------------------------
A couple things to keep in mind:
* Pivot is designed to be run from both standalone applications and applets.
Internal Pivot logging should not break stuff when running from within an
untrusted applet.
* Adding logging to Pivot shouldn't introduce a whole slew of dependencies or
bloat applications/applets.
was (Author: sworisbreathing):
A couple things to keep in mind:
# Pivot is designed to be run from both standalone applications and applets.
Internal Pivot logging should not break stuff when running from within an
untrusted applet.
# Adding logging to Pivot shouldn't introduce a whole slew of dependencies or
bloat applications/applets.
> Internal Logging Mechanism
> --------------------------
>
> Key: PIVOT-882
> URL: https://issues.apache.org/jira/browse/PIVOT-882
> Project: Pivot
> Issue Type: Brainstorming
> Affects Versions: 2.0, 2.0.1, 2.0.2
> Reporter: Steven Swor
> Priority: Minor
> Labels: logging
> Fix For: 2.1
>
>
> As of 2.0.2, Pivot does some internal logging using calls to System.out and
> System.err (for example, when using {{org.apache.pivot.json.JSONSerializer}}
> with {{verbose = true}}).
> It would be really nice if Pivot could leverage a more robust logging API
> instead, but certain design decisions come into play when choosing a logging
> framework.
--
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
