Hi Emre, I think the preferred way is the first one you suggest. If you try and register it again it throws a meaningful exception: for the given gateway a module with given version already exists. You can of course do the second one but essentially the server should anyway do the same in the first approach, so why to to burden this logic at client side.
This is just my guess, I will ask Chathuri to validate/correct this. Suresh > On Jun 3, 2015, at 11:07 AM, Emre Brookes <[email protected]> wrote: > > Is there a recommended way to register a module that may or may not already > exist ? > > should one just try registering it again (does it throw an understandable > error?) > (e.g. registerApplicationModule ) > > or validate against an application module list ? > (e.g. getAllAppModules ) > > -E. >
