Cargo

cargo-core-api-generic should discover implementations through META-INF/services

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.8
  • Fix Version/s: 1.0.1
  • Component/s: Generic
  • Labels:
    None
  • Number of attachments :
    0

Description

Today, DefaultContainerFactory and DefaultDeployerFactory has all the relevant implemenation names hard-coded. This isn't ideal because it prevents people from implementing Cargo API outside the cargo project, and also just not modular.

It should be possible to revise these implementations to use the standard service discovery mechanism.

Issue Links

This issue is depended upon by:
CARGO-771 Make all containers use the CARGO factories Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Massol added a comment -

I completely agree! I wanted to do this a long time ago but never came to do it. I personally don't have much experience on doing this and any help is most welcome.

Show
Vincent Massol added a comment - I completely agree! I wanted to do this a long time ago but never came to do it. I personally don't have much experience on doing this and any help is most welcome.
Hide
Permalink
Savas Ali Tokmen added a comment -

Finished, as marked by CARGO-771

Show
Savas Ali Tokmen added a comment - Finished, as marked by CARGO-771

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.