I can see the overlap but I think the Metadata service is only for
pages/components and I was looking for a general purpose application
default solution. For example you could store the email address for
the site admin in here. I don't think the MetaData service would be
appropriate for that.
Perhaps the other bit I was not clear about is the standardized way
the keys are stored. For example the defaults for a module are stored
in this format.
public class MyDefaults extends AbstractStaticDefaults implements
StaticDefaults {
public final static String defaultKey = "default:" + MiscModule.id +
":defaultKey:abc";
}
This allows the default service to look them up by module id, provides
a namespace and the default value is obvious.
I can see the two working together. The real problem I trying to solve
is a common solution that is easily used by module builders as well as
application builders that allows defaults to be stored in an
application specific way (most likely a database). Currently the
pieces are there what's lacking I think is a convention for doing it.
Without the convention everyone solves the problem in a different way
and the modules/applications cannot interoperate easily.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
