Second-Generation Managed Packaging Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Namespace-Based Visibility for Apex Classes in Second-Generation Managed Packages
The @NamespaceAccessible makes public Apex in
a package available to other packages that use the same namespace. Without this annotation,
Apex classes, methods, interfaces, and properties defined in a second-generation managed
package aren’t accessible to the other packages with which they share a namespace. Apex that
is declared global is always available across all namespaces, and needs no
annotation.
Considerations for Apex Accessibility Across Packages
- You can't use the @NamespaceAccessible annotation for an @AuraEnabled Apex method.
- You can add or remove the @NamespaceAccessible annotation at any time, even on managed and released Apex code. Make sure that you don’t have dependent packages relying on the functionality of the annotation before adding or removing it.
- When adding or removing @NamespaceAccessible Apex from a package, consider the impact to customers with installed versions of other packages that reference this package’s annotation. Before pushing a package upgrade, ensure that no customer is running a package version that would fail to fully compile when the upgrade is pushed.
- If a public interface is declared as @NamespaceAccessible, then all interface members inherit the annotation. Individual interface members can’t be annotated with @NamespaceAccessible.
- If a public or protected variable or method is declared as @NamespaceAccessible, its defining class must be either global or public with the @NamespaceAccessible annotation.
- If a public or protected inner class is declared as @NamespaceAccessible, its enclosing class must be either global or public with the @NamespaceAccessible annotation.
This example shows an Apex class marked with the
@NamespaceAccessible annotation. The
class is accessible to other packages within the same namespace. The first
constructor is also visible within the namespace, but the second constructor isn’t.
// A namespace-visible Apex class
@NamespaceAccessible
public class MyClass {
private Boolean bypassFLS;
// A namespace-visible constructor that only allows secure use
@NamespaceAccessible
public MyClass() {
bypassFLS = false;
}
// A package private constructor that allows use in trusted contexts,
// but only internal to the package
public MyClass (Boolean bypassFLS) {
this.bypassFLS = bypassFLS;
}
@NamespaceAccessible
protected Boolean getBypassFLS() {
return bypassFLS;
}
}