Uses of Class
com.ultikits.ultitools.manager.DataScope
Packages that use DataScope
Package
Description
-
Uses of DataScope in com.ultikits.ultitools.abstracts
Fields in com.ultikits.ultitools.abstracts declared as DataScopeMethods in com.ultikits.ultitools.abstracts with parameters of type DataScopeModifier and TypeMethodDescriptionvoidUltiToolsPlugin.setDataScope(DataScope scope) Injects theDataScopecredentialPluginManagerminted for this module (D-17). -
Uses of DataScope in com.ultikits.ultitools.api
Fields in com.ultikits.ultitools.api declared as DataScope -
Uses of DataScope in com.ultikits.ultitools.interfaces
Methods in com.ultikits.ultitools.interfaces with parameters of type DataScopeModifier and TypeMethodDescriptiondefault DataSourceDataStore.getDataSource(DataScope scope) Get the JDBCDataSourcebacking this store for the given scope, needing no entity class up front (a connection pool needs only a JDBC URL).default <T extends BaseDataEntity<String>>
DataOperator<T> DataStore.getOperator(DataScope scope, Class<T> dataEntity) Get a data operator for the entityscopeowns, refusing outright when it does not (D-14).default <T extends BaseDataEntity<String>>
DataOperator<T> DataStore.getOperatorUnchecked(DataScope scope, Class<T> dataEntity) Internal, unchecked construction path used ONLY byDataStore.getOperator(DataScope, Class), called after its ownscope.owns(...)check has already passed (CR-01, 02-13). -
Uses of DataScope in com.ultikits.ultitools.interfaces.impl.data.json
Methods in com.ultikits.ultitools.interfaces.impl.data.json with parameters of type DataScopeModifier and TypeMethodDescription<T extends BaseDataEntity<String>>
DataOperator<T> JsonStore.getOperatorUnchecked(DataScope scope, Class<T> dataEntity) Internal, unchecked construction path (CR-01/CR-03, 02-13):DataStore.getOperator(DataScope, Class)'s default body calls this only after its ownscope.owns(...)check has already passed.private static StringJsonStore.identityOf(DataScope scope) Derives the same identityJsonStore.getOperator(UltiToolsPlugin, Class)andJsonStore.getOperator(File, Class)each already resolve forJsonStore.OperatorKey, from aDataScopeinstead of a raw plugin orFile.private static booleanJsonStore.isInternalScope(DataScope scope) Whetherscopeis an internal plugin's own scope -- itsdataFolderis exactly the core framework's own data folder (DataScope.forPlugin's construction).JsonStore.transactionManagerFor(DataScope scope) Resolves (creating on first use) theJsonTransactionManagerforscope, giving the JSON backend a realTransactionManagerso@Transactionalis no longer refused ondatasource.type: json(02-05, D-03). -
Uses of DataScope in com.ultikits.ultitools.interfaces.impl.data.mysql
Methods in com.ultikits.ultitools.interfaces.impl.data.mysql with parameters of type DataScopeModifier and TypeMethodDescriptionMysqlDataStore.getDataSource(DataScope scope) <T extends BaseDataEntity<String>>
DataOperator<T> MysqlDataStore.getOperatorUnchecked(DataScope scope, Class<T> dataEntity) Internal, unchecked construction path (CR-01/CR-03, 02-13):DataStore.getOperator(DataScope, Class)'s default body calls this only after its ownscope.owns(...)check has already passed.private static StringMysqlDataStore.identityFor(DataScope scope) Resolvesscope's operator-cache identity, matching whichever legacygetOperatoroverload the same scope would actually route through: the internal (plugin name) shape whenscopeis an internal plugin's own scope (itsdataFolderis exactly the core framework's own data folder,DataScope.forPlugin's construction -- the same disambiguationJsonStore.identityOf(DataScope)andSQLiteDataStore.dbPathFor(DataScope)use, 02-05), the external (canonical folder path) shape otherwise.MysqlDataStore.transactionManagerFor(DataScope scope) Resolves the same per-plugin-containerJdbcTransactionManagerinstanceMysqlDataStore.getOperator(com.ultikits.ultitools.abstracts.UltiToolsPlugin, java.lang.Class<T>)wires onto the operators it hands out forscope's own identity -- the seamPluginManager.wireTransactionalcalls to bind the AOP@Transactionalinterceptor to it, so a module's data operators and its@Transactionalbeans share one transaction, not two (T-02-TAM-11), despite every plugin sharing the one globalMysqlDataStore.dataSource. -
Uses of DataScope in com.ultikits.ultitools.interfaces.impl.data.sqlite
Methods in com.ultikits.ultitools.interfaces.impl.data.sqlite with parameters of type DataScopeModifier and TypeMethodDescriptionprivate static StringResolvesscope's backing .db file path, matching whichever legacygetOperatoroverload the same scope would actually route through: the internal (dbPathForPlugin) shape whenscopeis an internal plugin's own scope (itsdataFolderis exactly the core framework's own data folder,DataScope.forPlugin's construction -- the same disambiguationJsonStore.identityOf(DataScope)uses, 02-05), the external (dbPathForFolder) shape otherwise.SQLiteDataStore.getDataSource(DataScope scope) <T extends BaseDataEntity<String>>
DataOperator<T> SQLiteDataStore.getOperatorUnchecked(DataScope scope, Class<T> dataEntity) Internal, unchecked construction path (CR-01/CR-03, 02-13):DataStore.getOperator(DataScope, Class)'s default body calls this only after its ownscope.owns(...)check has already passed.SQLiteDataStore.transactionManagerFor(DataScope scope) Resolves the same per-plugin-containerJdbcTransactionManagerinstanceSQLiteDataStore.getOperator(com.ultikits.ultitools.abstracts.UltiToolsPlugin, java.lang.Class<T>)wires onto the operators it hands out forscope's own database file -- the seamPluginManager.wireTransactionalcalls to bind the AOP@Transactionalinterceptor to it, so a module's data operators and its@Transactionalbeans share one transaction, not two (T-02-TAM-11). -
Uses of DataScope in com.ultikits.ultitools.manager
Fields in com.ultikits.ultitools.manager with type parameters of type DataScopeModifier and TypeFieldDescriptionPluginManager.externalScopesByFolderExternal plugin data folder (canonical path) -> theDataScopeminted for it, populated byPluginManager.registerExternal(ExternalPluginAdapter, Class[]).Methods in com.ultikits.ultitools.manager that return DataScopeModifier and TypeMethodDescriptionPluginManager.findScopeForDataFolder(File dataFolder) Resolves a data folder back to the registered external plugin scope that owns it (D-18).(package private) static DataScopeDataScope.forExternal(String pluginName, File dataFolder, Set<Class<?>> ownedEntities) Mints a scope for an external Bukkit plugin borrowing the framework viaUltiToolsAPI.connect(...).(package private) static DataScopeDataScope.forPlugin(UltiToolsPlugin plugin, Set<Class<?>> ownedEntities) Mints a scope for an internalUltiToolsPluginmodule.Methods in com.ultikits.ultitools.manager with parameters of type DataScopeModifier and TypeMethodDescriptionprivate voidPluginManager.registerEntityOwnership(DataScope scope) Recordsscope's owned entities inPluginManager.entityOwnership, so a later ownership refusal (D-15) can name the actual owning module instead of only saying "not registered to you".private voidPluginManager.registerExternalScope(File dataFolder, DataScope scope) Records an external plugin'sDataScopeunder its data folder's canonical path, soPluginManager.findScopeForDataFolder(java.io.File)can resolve the caller ofDataStore.getOperator(File, Class)back to a scope (D-18) -- the same canonical-path keying 02-02's Task 2 used for the SQLite pool map, so two spellings of the same folder resolve to one entry.private static JdbcTransactionManagerPluginManager.resolveJdbcTransactionManager(DataStore dataStore, DataScope scope, DataSource dataSource) Resolves theJdbcTransactionManagerPluginManager.wireTransactional(com.ultikits.ultitools.context.SimpleContainer, com.ultikits.ultitools.manager.DataScope, com.ultikits.ultitools.aop.AopProxyResolver)should bind the AOP interceptor to, for a JDBC-capabledataStore(02-09, T-02-TAM-11).(package private) static voidPluginManager.wireAop(SimpleContainer context, DataScope scope) Attaches AOP to a plugin container.private static voidPluginManager.wireJsonTransactional(SimpleContainer context, DataScope scope, AopProxyResolver resolver, JsonStore jsonStore) Builds and registers the@Transactionaladvisor for a plugin container backed by the JSON store, oncePluginManager.wireTransactional(com.ultikits.ultitools.context.SimpleContainer, com.ultikits.ultitools.manager.DataScope, com.ultikits.ultitools.aop.AopProxyResolver)has determineddataStorecannot supply a JDBCDataSourcebut is aJsonStore(02-05, D-03).private static voidPluginManager.wireTransactional(SimpleContainer context, DataScope scope, AopProxyResolver resolver) Builds and registers the@Transactionaladvisor for one plugin container.