You need to sign in to do that
Don't have an account?
heuye
must i mark component controller,all its methods and properties as global?
it seems when i mark a component as global in a managed package, i have to mark the component controller,all methods and all properties global,then,it works fine.
that's a little wierd.
i hope i can use the component in another managed pacakge,but i want to keep some methods private,since it's hard to refacter if all methods are global.
what should i do?
I don't think you have any choice in this case. If you mark the component as global, that means it can be used anywhere that the managed package is installed. If the controller, or parts of it, aren't global, then that would mean the controller (or parts of it) aren't accessible, which would break some or all of the component functionality.
i registered a new Developer Edition org,and tried this in the new org,it works fine.and i don't need to mark all of them global.
maybe the behavior changed in latest version?