New url handler: symbol [PAXURL-53]

[ops4j-issues]

Toni Menzel created PAXURL-53

This came just out of some observation: sometimes, you require an artifact that is pretty much denoted by an identifier only. But there are many (environment dependent) ways to get this artifact.
Example:
referal:org.foo.bar
where the url hander just picks up org.foo.bar and passes it forward to another, environment specific "resolver". This resolver for example could pick up this artifact from a local folder with substituting the following conversion:
org.foo.bar --> file:bundles/org.foo.bar.jar

Another resolver could translate it to an ordinary mvn protocol:
org.foo.bar --> mvn:group/org.foo.bar/1.0 where group and version here comes from the configuration of the resolver.

Most important thing i wanted to make here:
the user of the refereal can just predict a "symbolic" name, and does not have to know about anyhting more.
If you want, this would be an " enduser programmable" url handler.

Any questions ?

---

Votes: 0, Watches: 0

[ops4j-issues]

Toni Menzel commented

or maybe the name "symbol" is better:
symbol:org.foo.bar

kind of like that.

[ops4j-issues]

Toni Menzel commented

well, and the service in question could be look like that:
interface SymbolResolver() {
String resolve(String in);
}

[ops4j-issues]

Alin Dreghiciu commented

I was thinking about the same but in conjunction with a plugable/configurable repository, where repository can resolve an artifact based on a string key and eventual version.
The repository will make use of Pax URL and Pax Runner scanners, somehow and be able to read "recipes" on the fly so a user could affect resolution process online.
Still, a lot of thinking.

[grgrzybek]

@tonit @adreghiciu how time flies... Do you remember this one after 14 years? :)