You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2018/02/28 17:56:00 UTC
[jira] [Commented] (DAFFODIL-628) Add support for JAF logging
mechanism
[ https://issues.apache.org/jira/browse/DAFFODIL-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380751#comment-16380751 ]
Michael Beckerle commented on DAFFODIL-628:
-------------------------------------------
Our Schema Definition Warning system now requires that a WarnID be created to allow selective suppression of individual warnings.
A similar ID system is needed for errors, and should cover both Schema-Definition (compile and runtime issued) and Processing errors including Validation errors.
However, I had very bad experience in a former life, with internationalization (i18n) and localization (L11n) of a large software system where the outsource team tasked with i18n/l11n basically destroyed the code base, enlarging it 3x and making it unmaintainable. I collected as set of lessons learned from this. Much of what I wrote in this is relevant to Daffodil: [I18n and L11n Issues and Ideas | https://docs.google.com/document/d/1gFh5kpA5wIeamNIfZPDamH2tZEY-tyjM6N7N5gn-s6Q/edit?usp=sharing |http://example.com], which I would suggest is required reading before we do anything further and develop a policy for Daffodil that will support JAF logging, i18n, etc.
> Add support for JAF logging mechanism
> -------------------------------------
>
> Key: DAFFODIL-628
> URL: https://issues.apache.org/jira/browse/DAFFODIL-628
> Project: Daffodil
> Issue Type: New Feature
> Components: API, Back End
> Reporter: Steve Lawrence
> Priority: Major
> Fix For: deferred
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)