Not sure I care that much about the details of the implementation,
although I'm starting to feel like CDI for this use case may be
making things more complicated, not less, relative to simply newing
up an instance of the type specified in the hashAlgorithm attribute
and passing hashProperties to the constructor ...
What I think I'd like to see in terms of behavior is:
- Hash algorithm and hash properties can be specified on the
- Multiple instances of the annotation/idstore -- is that
supported? -- could specify different hash algorithms, or, they
could specify the same algorithm type, but different properties.
- At runtime, each identity store instance gets its own instance
of the hash algorithm type, even if other identity store
instances are using the same hash algorithm.
- The hash algorithm is initialized onced, up front, with the
It's possible to make an argument for deferred evaluation of
properties, etc., but that complicates things considerably and I
think doing only the above provides plenty of flexibility. An
implementation of HashAlgorithm could certainly do its own deferred
My $0.02 (or maybe $2.00).
On 07/24/2017 08:41 AM, Arjan Tijms
Will Hopkins | WebLogic Security Architect | +1.781.442.0310
Oracle Application Development
35 Network Drive, Burlington, MA 01803