Great, thanks, do you want me to make the change? I noticed that the IS_REST flag gets loaded in the external config, so I'll change that too.
I also see that version is a system property??? ----- Original Message ----- From: "Shawn McKinney" <[email protected]> To: [email protected] Sent: Wednesday, May 4, 2016 1:49:22 PM Subject: Re: Static Config Initialization Problems > On May 4, 2016, at 8:30 AM, Shawn McKinney <[email protected]> wrote: > > which initialized in the > private void init() > > during instance construction. Not sure what the problem is, it should work. > Looking in the debugger atm…. OK, figured it out. Code needs to change just a little bit more... Simply declare all the member variables here: public class RestUtils { private String HTTP_PW; private String HTTP_HOST; private String HTTP_PORT; private String HTTP_PROTOCOL; private String VERSION; private String SERVICE; private String URI; and then load all their values later inside the init method: private void init() { HTTP_UID = Config.getInstance().getProperty( "http.user" ); HTTP_PW = ( ( EncryptUtil.isEnabled() ) ? EncryptUtil.getInstance().decrypt( Config .getInstance().getProperty( HTTP_PW_PARAM ) ) : Config.getInstance().getProperty( HTTP_PW_PARAM ) ); HTTP_HOST = Config.getInstance().getProperty( "http.host" ); HTTP_PORT = Config.getInstance().getProperty( "http.port" ); HTTP_PROTOCOL = Config.getInstance().getProperty( "http.protocol", "http" ); VERSION = System.getProperty( "version" ); SERVICE = "fortress-rest-" + VERSION; URI = HTTP_PROTOCOL + "://" + HTTP_HOST + ":" + HTTP_PORT + "/" + SERVICE + "/"; which gets us past the junit test failures. There is minor tweak that must be made to the realm to go along with this. The fortress rest is good but haven’t test the web component yet. I think we’re getting close. Also still need to run the jmeter tests of before / after to make sure we haven’t slowed anything down. I don’t think so but you never know. Thanks, Shawn
