Domain models and Metro (was: First discussion - api/implpattern)
dleangen at canada.com
Tue Oct 5 11:48:42 EDT 2004
> Most APIs has a single entry class.
> JNDI - InitialContext
> XML - DocumentBuilderFactory
> and so on. The people using the API will probably screw up :o) anyway, so
> don't expect them to do stuff in main(), and your code doesn't
> have a main().
> The guys above, normally employ some form of fallback strategy, such as
> looking for files inside Jars, system properties and others.
Ok, that's interesting.
So essentially, these would be one classe (such as InitialContext) in the
API that would actually be an implementation class? Or an implementation
class that would be added to the API doc?
In any case, this makes sense and, along with your last post, pretty much
resolves the concerns I have for now. As for the unpredictable users, I
guess I'll be dealing with those "user originated" bugs as they crop up.
Getting ahead of myself just a little...
My plan is to publish the API that would be used without any framework.
Then, once that's stabilized, I'll publish an SPI that will use Metro. So,
I'll have to figure out a way to make the use of Metro completely
transparent to the user, including installation and all the rest. But I'm
still far from that point right now.
Anyway, thanks a lot for your help. :-)
More information about the support-dpml