Edit: probably this request does not make sense as more than 1000 items shouldn't be displayed on on page - instead i should use query more and display a "next 1000 items" link on the page

hi guys, i need a hint for displaying the results of a query with more than 1000 items. i browse them by doing a for loop but haven't found any example to bind them to a vf-page so far. i wonder if it actually can be done by PageReference Method (as i did with lists returned by queries with less results).

Hi there, i'm a bloody beginner in apex and i don't know how to write a simple test-class for the following controller extension of the case controller :

it was written to avoid an "email to:" field from beeing filled with thestandard contact for the account associated with the case when replying to a mailin the case. it is called in a special section within the case-vf page. all emailsfor this case are displayed an can be replyed by link. it works perfectly but must betested as you know.

the code below is my testclass attempt so far. i have no idea how to calla testcase of mine from which i know what emails and their subjects are.i simply wanna compare the amount of emails or some or one subject.

Hi there, i'm a bloody beginner in apex and i don't know how to write a simple test-class for the following controller extension of the case controller :

it was written to avoid an "email to:" field from beeing filled with thestandard contact for the account associated with the case when replying to a mailin the case. it is called in a special section within the case-vf page. all emailsfor this case are displayed an can be replyed by link. it works perfectly but must betested as you know.

the code below is my testclass attempt so far. i have no idea how to calla testcase of mine from which i know what emails and their subjects are.i simply wanna compare the amount of emails or some or one subject.

There are VisualForce pages in our application, whose controllers make web service calls to an external service. This service authenticates the caller by using the standard salesforce.com SSO (Single Sign-on) procedures, namely, the VF controller passes the API URL and the current session ID to the web service as parameters and the web service in turn calls back to the salesforce.com API to validate the session. It gets the API URL from the VF page, and the session Id using UserInfo.getSessionId().

This strategy is documented and implemented in sample salesforce.com code and has been working for us for the better part of the year. It continues to work from custom field formulas as well.

Along comes Winter '09 and it no longer works in VisualForce. The session ID we pass to the web service is now invalid. The error is: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader. The only clue is that the URL hosting the page has changed (although the API url has not). No code has changed on our side.