On Mar 12, 2014, at 8:50 PM, [email protected] wrote:

> Yip, that's what I was using in the Modeler but the username and pass have to 
> be in a properties file and I was hoping that there was a simple alternative.

Usually the problem with specifying password (and other settings) in the 
Modeler is that they are different between your dev environment and final 
deployment environment. So while properties are not as simple as using UI, it 
is a sensible alternative that will let you change those without unpacking your 
deployment artifacts, etc.

Andrus

Reply via email to