if the application was built with annotations like
@RequiresRoles("administrator")
and such statements were placed before
@RequiresRoles("administrator")
Entity save (Integer id) {
...
}
then how is my administrator suppose to login ?
in doGetAuthenticationInfo I search for administrator account.
it does not exist
so i proceed to create it
but i cant because the current subject has no roles
i would hate to pre-fabricate my application with an insert sql script.
the seeded entity feature for tynamo has no graceful exception logic if a
seeded entity already exists and just shuts down the whole app so its unusable.
if it did I wuold have already implemented and been flown thru that part
already but it has sat like that for 18months
is there a elegant way thru this?
