#1479 Calling SFDC Wizard Login Op from other Script breaks wizard

[Torgil Zethson]

If the SFDC Login Operation that is created by an SFDC Wizard is called by a RunOperation call in another Script, creating new wizards may fail with the following error:

java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
...

Caused by: java.lang.NullPointerException
at com.jitterbit.integration.salesforce.LoginCredentials.equalsIgnoringSandbox(LoginCredentials.java:73)
at com.jitterbit.integration.client.ui.interchange.entity.salesforce.wizard.LoginPageModel$ExistingLoginScriptLocator.isMatchingCredentials(LoginPageModel.java:138)
at com.jitterbit.integration.client.ui.interchange.entity.salesforce.wizard.LoginPageModel$ExistingLoginScriptLocator.findExistingScript(LoginPageModel.java:128)
at com.jitterbit.integration.client.ui.interchange.entity.salesforce.wizard.LoginPageModel.getExistingScript(LoginPageModel.java:63)
at com.jitterbit.integration.client.ui.interchange.entity.salesforce.wizard.LoginPage.getExistingLoginScript(LoginPage.java:57)

This error occurs when finishing the new wizard.

[Torgil Zethson]

Fixed on the 4.0.x branch, in revision 7581 private). The fix goes into build 4.0.5.4.

[Torgil Zethson]

The fix has been merged to 4.1.x, in revision 7582 (private). The fix goes into build 4.1.0.22.

No need to merge to the trunk, since the trunk uses the new Partner-WSDL based wizards.

[Torgil Zethson]

Clarification: This bug only occurs if an existing Login Script, created by the SFDC Wizard, is copied or modified in some way. Things work fine if the Login operation is called from a Script that is created from scratch.