Accounts example?

[manosbatsis]

Started looking at migrating Corbean's BNMS starter from the old Corda Solutions imlementation to the this bn-extension. It's late and i'm a bit dizzy so please bear with me and a couple of questions:

• It it fair to say the new BNIdentity interface largely replaces the old Membership metadata in terms of customisation purposes (excluding groups/roles)?
• Is it possible to use any existing or custom implementation of BNIdentity to assign groups and/or roles to Corda Accounts?
• If no accounts-aware implementation is readily available, does the extension support multiple MembershipStates with the same MembershipIdentity.cordaIdentity but different MembershipIdentity.businessIdentity? The reason I'm asking is because BNService methods like .getMembership() seem to assume a single result per networkId and Party combination which, in my understanding and the case of Corda Accounts, beats the purpose of allowing a custom BNIdentity implementation in the first place. Unless of course one can roll out their own BNService-ish replacement as a Corda Service to work around current service API limitations via custom criteria queries/logic and so on.

[manosbatsis]

@tubibuto @bpaunescu: After our discussion in https://github.com/corda/bn-extension/pull/33 would you be interested in a PR that

• Provides additional service methods or stand-alone service without the assumption of only single result per networkId and Party combination
• Adds method signatures to accept additional query criteria