You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Mike Edwards (JIRA)" <de...@tuscany.apache.org> on 2009/04/17 10:10:15 UTC
[jira] Created: (TUSCANY-2974) Need to include Artifact name in
Error/Warning messages when processing Contributions
Need to include Artifact name in Error/Warning messages when processing Contributions
-------------------------------------------------------------------------------------
Key: TUSCANY-2974
URL: https://issues.apache.org/jira/browse/TUSCANY-2974
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Problem Determination
Affects Versions: Java-SCA-2.0
Reporter: Mike Edwards
Assignee: Mike Edwards
Priority: Minor
Fix For: Java-SCA-2.0
There are often cases where the processing of artifacts within a Contribution, particularly Composite files, where problems are found and are reported. However, it is often the case that these messages do not contain the name of the artifact involved. When the Contribution contains many artifacts, this is not at all helpful.
Here is a typical example from running one of the OASIS Assembly testcases recently:
INFO: Loading contribution: file:/C:/Strategy/SCA/OASIS-Assembly/OASIS_SCA_Tests/Assembly/TestCases/target/
17-Apr-2009 09:05:53 org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader
SEVERE: XMLSchema validation error occured in: null ,line = 40, column = 2, Message = cvc-complex-type.3.2.2: Attribute 'promotes' is not allowed to appear in element 'reference'.
- that "null" indicates a willingness to give the information about the artifact, but examining the code shows that the artifact name is not available to the error processing system.
The handling of problem reporting must be upgraded so that the artifact name is always included in any message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2974) Need to include Artifact name in
Error/Warning messages when processing Contributions
Posted by "Mike Edwards (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700079#action_12700079 ]
Mike Edwards commented on TUSCANY-2974:
---------------------------------------
Looking at the classes involved in generating and processing the messages like the one quoted above, it seems simplest to add a property "artifactName" to the Monitor interface and to the MonitorImpl class.
The artifactName is known to classes such as CompositeDocumentProcessor, and these classes also have access to a Monitor object which is passed down to the lower level XMLStreamReader and which handles errors when they are found. So the artifactName in the Monitor can be used when generating messages...
> Need to include Artifact name in Error/Warning messages when processing Contributions
> -------------------------------------------------------------------------------------
>
> Key: TUSCANY-2974
> URL: https://issues.apache.org/jira/browse/TUSCANY-2974
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Problem Determination
> Affects Versions: Java-SCA-2.0
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Priority: Minor
> Fix For: Java-SCA-2.0
>
>
> There are often cases where the processing of artifacts within a Contribution, particularly Composite files, where problems are found and are reported. However, it is often the case that these messages do not contain the name of the artifact involved. When the Contribution contains many artifacts, this is not at all helpful.
> Here is a typical example from running one of the OASIS Assembly testcases recently:
> INFO: Loading contribution: file:/C:/Strategy/SCA/OASIS-Assembly/OASIS_SCA_Tests/Assembly/TestCases/target/
> 17-Apr-2009 09:05:53 org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader
> SEVERE: XMLSchema validation error occured in: null ,line = 40, column = 2, Message = cvc-complex-type.3.2.2: Attribute 'promotes' is not allowed to appear in element 'reference'.
> - that "null" indicates a willingness to give the information about the artifact, but examining the code shows that the artifact name is not available to the error processing system.
> The handling of problem reporting must be upgraded so that the artifact name is always included in any message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.