[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tuscany-dev
Subject:    [jira] Resolved: (TUSCANY-3395) Tidying up Contribution Scanner API
From:       "Luciano Resende (JIRA)" <dev () tuscany ! apache ! org>
Date:       2009-12-17 23:32:18
Message-ID: 870425934.1261092738595.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/TUSCANY-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Luciano Resende resolved TUSCANY-3395.
--------------------------------------

    Resolution: Fixed

Fixed, we now return a artifact list as a result of contribution scan:
    List<Artifact> scan(Contribution contribution) throws ContributionReadException;

> Tidying up Contribution Scanner API
> -----------------------------------
> 
> Key: TUSCANY-3395
> URL: https://issues.apache.org/jira/browse/TUSCANY-3395
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-2.0
> Reporter: Luciano Resende
> Assignee: Luciano Resende
> Fix For: Java-SCA-2.0
> 
> 
> Currently, the contribution scanner interface have two methods to
> process contribution artifacts, the scan will return a list of URIs as
> String, and then, in ContributionContentProcessor, we retrieve the
> artifact URL for each URI.
> I'd like to tide up this process, and have the scan return a list of a
> object that would have both the artifact URI and URL... possibly
> List<Artifact>. This would allow retrieving the necessary basic
> artifact information in one call instead of duplicating calls which
> might have performance impact in some environments where contribution
> information is scattered in multiple locations.

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


[prev in list] [next in list] [prev in thread] [next in thread]