Our organization created a managed package that consumes a web service hosted by our own company.

The web service methods are called using an HTTPS endpoint.

After installation, the code that executes a call one of the web service's method is getting the following error:

"Web service callout failed: Unable to find header type info forconfig".

If we change the web service URL to use "http" instead of "https", the web method call works.

So what does it mean this error message? How we can use "https" protocol, instead of "http" for the web service calls? 

Our organization has defined a custom object in our managed package, to be added at a SalesForce organization upon installation.

However, this custom object stores sensitive data, which is supposed to be used *only* by the classes and pages in the managed package.

We would like to know if there is a way to configure the security in the package (or in the target organization, after installation) such that:

1) The custom object can not be accessed by classes and pages outside the managed package. 

2) The custom object data can not be browsed by OQL queries sent through the Apex Web Services API.

We are currently developing an Apex application to be packaged and listed in the AppExchange directory.

Our application contains custom buttons associated with the Account, Case, Contact, Lead, Opportunity objects.

Before we created the package, we added the custom buttons to their respective page layouts (Account, Case, Contact, Lead, Opportunity) in our development organization where the application was developed.

After we installed our managed package in one of our sandboxes, we found out that the custom buttons were not displaying in the respective sandbox page layouts.

We tried adding the custom buttons manually, after the installation, by customizing the layout of the respective pages and drag-and-dropping the custom buttons.

However, we found out that this action did not have an organization-wide effect. By logging with a different user, we would not see the custom buttons in the respective page layouts that had been added by another user.

So our questions are:

1) Can the installation of a managed package also add custom buttons to the page layouts of the target organization?

2) If not, how should proceed the user performing the installation in order to manually add the custom buttons to the respective layouts, in a way that the action has an organization-wide effect (all users of the organization would see the custom buttons)?

We do not want to settle with a solution where, after package installation, each and every user of the organization would have to add manually the custom buttons.

I have installed the Force.com IDE in Eclipse successfully.

But while code assistance (autocomplete) is feature enabled for the source files of the Apex classes, I cannot find a way to have it also enabled for the Visualforce page files.

For instance, when I am typing "<apex:form>" element, the editor does not show the available attributes for the this element, like it is displayed in the online Apex Visualforce pages editor.

Is this a feature not yet available in the current version of the Force.com IDE plugin?

Our organization created a managed package that consumes a web service hosted by our own company.

The web service methods are called using an HTTPS endpoint.

After installation, the code that executes a call one of the web service's method is getting the following error:

"Web service callout failed: Unable to find header type info forconfig".

If we change the web service URL to use "http" instead of "https", the web method call works.

So what does it mean this error message? How we can use "https" protocol, instead of "http" for the web service calls? 

We are currently developing an Apex application to be packaged and listed in the AppExchange directory.

Our application contains custom buttons associated with the Account, Case, Contact, Lead, Opportunity objects.

Before we created the package, we added the custom buttons to their respective page layouts (Account, Case, Contact, Lead, Opportunity) in our development organization where the application was developed.

After we installed our managed package in one of our sandboxes, we found out that the custom buttons were not displaying in the respective sandbox page layouts.

We tried adding the custom buttons manually, after the installation, by customizing the layout of the respective pages and drag-and-dropping the custom buttons.

However, we found out that this action did not have an organization-wide effect. By logging with a different user, we would not see the custom buttons in the respective page layouts that had been added by another user.

So our questions are:

1) Can the installation of a managed package also add custom buttons to the page layouts of the target organization?

2) If not, how should proceed the user performing the installation in order to manually add the custom buttons to the respective layouts, in a way that the action has an organization-wide effect (all users of the organization would see the custom buttons)?

We do not want to settle with a solution where, after package installation, each and every user of the organization would have to add manually the custom buttons.

I need to add a custom page layout in Package , but Add option for Package there is no PageLayout .

how can i add a pagelayout to Lead object in package ??

can we do that in package?