We went through a similar thing a few years back with SSL certificates.
GoDaddy offered super-cheap (relatively speaking) certs, but none of the major browsers had GoDaddy in their default list of certification entities at that time.
So the upshot of using a GoDaddy cert was that every visitor would get a "not trusted" warning, even though the cert was legitimate.
That's not something you want your users to see when they're in the middle of signing up or downloading something from your site.
I don't know whether or not this concept applies to java & jar too, but you might want to confirm it before making a decision.
It worked for Mark Shuttleworth during (before) the first boom. It could work for you, too!
There's a lot of competition out there these days, and the cost/time of getting accepted by all of the browsers put your time to revenues sometime two or three years into the future. In other words, it's a hard business to get into to, and you'll probably need a source of revenue while you wait. That's why folks who sell domains are getting into the business...they have some revenues from the domain business for those two or three years, and then they have a large customer base to sell the certs to.
We went through a similar thing a few years back with SSL certificates.
GoDaddy offered super-cheap (relatively speaking) certs, but none of the major browsers had GoDaddy in their default list of certification entities at that time.
So the upshot of using a GoDaddy cert was that every visitor would get a "not trusted" warning, even though the cert was legitimate.
That's not something you want your users to see when they're in the middle of signing up or downloading something from your site.
I don't know whether or not this concept applies to java & jar too, but you might want to confirm it before making a decision.