You need to sign in to do that
Don't have an account?

Namespace confusion
I am extending a VF page which resides in a managed packaged.
code is as follows:
<apex:page controller="myController" showHeader="false" sidebar="false" >
<apex:include pageName="ManagedPackage__managedPage" />
...
</apex:page>
the purpose of myController is simply to inject some javascript remoting into the managed page.
when this page renders, I get the following error:
Apex class 'ManagedPackage.myController' does not exist
the apex:page resides in the default namespace as does the custom myController. why is the page then attempting to reference myController in the managed package namespace. how do I coerce it to refer to the custom controller in the default namespace?
code is as follows:
<apex:page controller="myController" showHeader="false" sidebar="false" >
<apex:include pageName="ManagedPackage__managedPage" />
...
</apex:page>
the purpose of myController is simply to inject some javascript remoting into the managed page.
when this page renders, I get the following error:
Apex class 'ManagedPackage.myController' does not exist
the apex:page resides in the default namespace as does the custom myController. why is the page then attempting to reference myController in the managed package namespace. how do I coerce it to refer to the custom controller in the default namespace?
the problem explained above goes away when I remove the showHeader attribute from the apex:page declaration.