Rectangle 27 0

public List<TestObject__c> objects {get; private set;}

It creates the getter/setter for you and looks cleaner imo. As for your current issue, yes - it's hard saving code directly into production - especially with test classes in separate files.

Best to do this in a sandbox/dev org then deploy to production (deploy to server - Force.com IDE). But if you must save directly into production then I'd combine test methods with your class. But in the long run, having @test atop a dedicated test class is the way to go. It won't consume your valuable resources this way.

Yeah, I got fed up with it soon afterwards and did pretty much what you just described.

salesforce - Apex error: "Save error: Method does not exist or incorre...

salesforce apex-code
Rectangle 27 0

Either partnerSoapSforceComWrapper on your first line is not the correct variable name, or it doesn't have a method signature update_x(List <Contact>).

Where is partnerSoapSforceComWrapper defined? If you post more code I could give a more definitive answer. Hopefully the above helps you find the problem.

eclipse - Method does not exist or incorrect signature? - Stack Overfl...

eclipse salesforce
Rectangle 27 0

Assuming this is in Apex, List<Contact> will be a reference to the built in Contact type, and not the Contact type you imported from the WSDL, and so its not a descendent of the sObject_x type. But once you've gotten that sorted out, I expect you'll be further stuck because wsdl2apex does not support the xsd:any element used by the partner WSDL, so once you get it to compile, you won't be able to do anything useful.

eclipse - Method does not exist or incorrect signature? - Stack Overfl...

eclipse salesforce
Rectangle 27 0

So this turns out to be an issue of a bad compiler error message. What the issue was is that I wasn't using the correct signature for fromCharArray. It required a List of integers and I'm passing a List of String. In the long run I didn't want that method anyway. What helped me come to this conclusion was calling return System.String.fromCharArray(InputArray) and it showed me that I may be using an incorrect signature for that method. Hope this helps others debug their Apex code.

salesforce - Getting Variable does not exist: String in an apex method...

salesforce apex-code apex
Rectangle 27 0

You'are trying to use the instance method as a static. Create an instance of ConnectApi.BinaryInput

ConnectApi.BinaryInput binaryInput = new ConnectApi.BinaryInput(fileBlob, null, filename);

salesforce - Error: Compile Error: Method does not exist or incorrect ...

salesforce apex-code salesforce-chatter
Rectangle 27 0

Make the changeObject method a static method

public static void changeOject(list<le_object__c> newList, list<le_object__c> oldList){
  }

And you do not need to instantiate the class in the trigger, as the method is now static you can directly call the method something like this:

TestingTrigger.changeObject(trigger.new, trigger.old);

triggers - Apex coding error: Method does not exist or incorrect signa...

methods triggers salesforce call