I am working on getting the Strongview API working with my Force.com app.  According to their documentation, this lit bit of code is required (C# example):

 

/* Ignore Certificate by trusting all certificate */
System.Net.ServicePointManager.CertificatePolicy = new TrustAllCertificatePolicy();

 

Shocking, right?  Anyway, is there an Apex equiqalent for this?  The part of me that wants the Force.com environment to be a safe and secure place hopes that there isn't.  The part of me that is a developer who needs to get a task done hopes there is.  ...But mostly I hope there isn't...

On a standard Salesforce edit page, when the save button is clicked, the button immediately grays out and prevents the user from clicking the button multiple times.  I'm trying to get the same effect on a VFP but I am having no luck.  Has anybody already done this?  I don't know if it's pertinent, but my save button is calling a method called Save in a custom controller.

 

 

<apex:pageBlockButtons > <apex:commandButton action="{!Save}" value="Save" id="saveBtn" /> </apex:pageBlockButtons>

 

 

 

I'm trying to finish up my testMethods on a Controller Extension I wrote for a Visualforce page.  The problem I'm running into is that the controller is involved in a lot of callouts.  There are a couple of Geocoding callouts to Google as well as 4 different callouts to our point of sale system.  Obviously testMethods don't allow callouts, but how can I get my coverage to 75% (currently at 48%) when so much of the code is tied up in callouts?  Suggestions?

Message Edited by EXRADM on 12-16-2008 01:20 PM

On a standard Salesforce edit page, when the save button is clicked, the button immediately grays out and prevents the user from clicking the button multiple times.  I'm trying to get the same effect on a VFP but I am having no luck.  Has anybody already done this?  I don't know if it's pertinent, but my save button is calling a method called Save in a custom controller.

 

 

<apex:pageBlockButtons > <apex:commandButton action="{!Save}" value="Save" id="saveBtn" /> </apex:pageBlockButtons>

 

 

 

I'm trying to finish up my testMethods on a Controller Extension I wrote for a Visualforce page.  The problem I'm running into is that the controller is involved in a lot of callouts.  There are a couple of Geocoding callouts to Google as well as 4 different callouts to our point of sale system.  Obviously testMethods don't allow callouts, but how can I get my coverage to 75% (currently at 48%) when so much of the code is tied up in callouts?  Suggestions?