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.
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.
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.
Vincent Massol added a comment - 09/Jun/06 01:15 PM 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.
Improvement
Open
Major
cargo-core-api-generic should discover implementations through META-INF/services
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.