The logic I used for the password encoder is a bit screwed up and might can be improved. I intentionally didn't throw an exception there (I return NULL) because I want the whole model to continue loading into the modeler, but the loading code is in the framework -- and we can't have the GUI-less framework opening error dialog panels. So, I returned a NULL and catch that later in the modeler after the rest of the model finishes loading. In an application that is using that code, it won't be able to login to the DB and that should be enough of a problem for the user to go look at the logs. It isn't pretty, but it works. Always open to suggestions, of course!
Thanks! /dev/mrg On Thu, Aug 21, 2008 at 2:55 PM, Andrus Adamchik <[EMAIL PROTECTED]> wrote: > Ok. I guess it makes sense in this case, as the encoder is invoked on saving > the model, so CM needs to access it in runtime. > > Andrus
