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…

As a developer, “Chatter” is something I love most, apart from other goodies like Sites etc given by force.com platform. So can’t resist my temptation to digg what’s next with Chatter in coming Winter’11 release. Regarding this I got good insights from…

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…

This post tries to cover a common night mare while developing solutions on top of Salesforce using Partner/Enterprise WSDL web services. So this post can be super helpful for developers working with following technologies with Salesforce Partner/Enterpise WSDLs…

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…

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…

Apex wrapper on Apex DOM classes(Document, XmlNode). It exposes W3C DOM API for XML manipulation, which is pretty popular and known to most developers, so saves…

My Open Source SFDC Endeavor "Fast Apex XML DOM" was featured by SFDC March 2010 Developer Newsletter…

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..

YUI Dependency Configurator is a great tool for getting a single unified JS or CSS instead of several css/js files. Only problem with that is it doesn't works over "HTTPS". Browser's like Internet Explorer fail to load a web page delivered over HTTPS containing JS/CSS delivered over un-secure(HTTP) URLs…

Apex wrapper classes aka “Fast Apex XML Dom” has reached a point that I can share with all on force.com Codeshare. Now Apex test classes have more than 95% code coverage(All Legal, no fake lines added :)))…

This post explains how to quickly start using the new wrapper Apex API. Developers coding previously on either Ron Hess’s XmlDOM or standard w3c xmldom will feel almost no difference and no learning curve in using this API…

On many occasions we might need to access some HTML DOM element inside a component from page using JavaScript. Example scenarios can be page fetching value of text field inside a component using JavaScript…