Apex static is always confusing for me. I am from a Java background, so it took a while for me to really understand the differences between Apex and Java static. This post discusses apex controller static behavior, i.e., in relation to Visualforce only. Here by Apex Controller static, I mean static variables/blocks declared in the controller associated with a Visualforce page.

<apex:actionRegion /> is interesting and somewhat ignored tag in Visualforce. Tag is ignored, because Visualforce documentation is not in depth, to explain the real utility of this tag. So this post explains some stuff around action region to make it easy for developers to understand…

I stumbled upon a strange Batch Apex issue today. My batch job was going well in a few SFDC orgs; after deploying the same to a new org it stopped working completely. I just see, “First error: Attempt to de-reference a null object” in debug and apex logs. 

You must be stuck up with Apex, when sorting is required on instances of user defined classes and pre-loaded Sobjects. Unfortunately standard Apex API just gives a method List.sort(), that just works with primitive data types…

apex-lang is an open source Apex library, its Apex port of very popular Apache Common Lang java project. Almost all java developers and open source projects in Java depend on Apache Common Lang. This is really good to see that something similar came to apex in open source. apex-lang is comprising of many Utility classes that port the Apache’s stuff to apex…

Salesforce releases are exciting for me, I am always eager to know whats coming next in this release. While writing some other blog post on “Chatter for Winter’11”, I was going thru Quinton’s blog post on Salesforce blog. On a screen shot on this blog post, I noticed a few interesting things (might be related to Winter’11 release), those are highlighted in red circles in picture below…

This post explains how to best handle/access primitives, lookups and child relationships, when working with Partner-Sobject compiled from Salesforce WSC WSDL complier…

This post compares “com.sforce.soap.partner.sobject.SObject” generated by compiling Partner WSDL with WSC, to SObject class generated with Java libs like Apache Axis. This might be of interest for those developers who compiled Partner WSDL with other libs like Apache CXF etc..

Yesterday’s blog post explained how to best use Apache Axis and WSC stubs in parallel on same JVM or Project. This post reveals another small trick for developers using both WSC and Apache Axis WSDL2Java stubs together in a project/jvm. The trick focuses on reducing the number of login() call via Partner or Enterprise Stubs…

This post is specially for those, having a Java Application(Production) working with SFDC web services via Apache-Axis stubs(WSDL2Java), but because of known advantages from WSC, you want to add some new functionality, like Bulk API as mentioned in SFDC blog here…

I mentioned few days back about starting integration of Tolerado with WSC. The latest updates on this integration are

Tolerado-WSC is code complete [beta* :)]. I am testing the API now…

I am researching on how to best use & integrate “WSC” with Tolerado. This research mainly focuses on

How to preserve and reuse a single sfdc login session across the all the WSDLs. This should again go in transparent fashion as with Tolerado for Apache Axis…

I am working and doing R&D with the Salesforce WSC library to get Tolerado ported to it. Most of the pieces worked well, but I was initially stuck with Metadata WSDL issues. I faced the following two major blockers: Metadata WSDL Compilation Issue and Metadata Connector Config Issue.

Developers are always too concerned about many things, like making the Web Service call work right for them and implementing the biz requirements. So handling exceptions and giving them proper treatment is mostly not a priority…

Web Services are something that are either used as provider or client by almost every developer. Web services are usually exposed via SOAP, these days RESTful web services are common too. One thing common in all types web services is HTTP protocol, its the base protocol wrapped by SOAP / REST implementations…

Sometimes while working with Salesforce Web Service APIs, we get a “No Operation Available for Request” error. This error comes because the “Web service ENDPOINT URL” is not correct. In my case, this error came when I was trying to use “apex.wsdl” for executing Apex test cases via my Java code.

501 error comes when we cross the governor limit, that is, “total number of records retrieved by SOQL queries”. As per this limit, a single Apex testMethod can only retrieve 500 rows in all SOQL calls.

Force.com(Apex/Visualforce) developers spend lot of coding time waiting for file SAVE operation to finish. This is specially panic for developers working on huge force.com projects having many classes, pages, objects and components…

Today I was done with coding the 3 important missing API’s in Fast Apex XML DOM’s TODO list. The latest code is checked into Google Code SVN. Following are the newly added API’s to TG_XmlNode.cls..