Module library attributes

[Sean Mullan]

Just to expand on this a bit - this would be useful to quickly retrieve
information associated with a module that has already been checked when it was
installed, for example - it is a platform module, or is signed by a specific
certificate that gives it special privileges (ex: a JCE provider).

Perhaps the module's context would be an appropriate place to store this type of
information. Any thoughts?

--Sean

On 12/6/11 10:05 AM, Sean Mullan wrote:
> I'd like to be able to store a persistent attribute with a module when it is
> installed that could then be retrieved at runtime when all I have is a reference
> to the Module object. I don't think this is quite the same as
> metadata, as listed in the jigsaw requirements. It is more like data that we can
> use to optimize our implementation. It doesn't necessarily have to be exposed
> via a public API.
> 
> --Sean
>