libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

Fix a typo and format code indent

Browse source
This commit is contained in:
Kohei Tamura 2019-04-19 00:37:06 +09:00 committed by Stian Thorgersen
parent d6eb802a66
commit 6d265a2da5
1 changed files with 22 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
server_development/topics/providers.adoc
View file

@ -22,27 +22,27 @@ import ...
public class MyThemeSelectorProviderFactory implements ThemeSelectorProviderFactory { public class MyThemeSelectorProviderFactory implements ThemeSelectorProviderFactory {
@Override @Override
public ThemeSelectorProvider create(KeycloakSession session) { public ThemeSelectorProvider create(KeycloakSession session) {
return new MyThemeSelectorProvider(session); return new MyThemeSelectorProvider(session);
} }
@Override @Override
public void init(Config.Scope config) { public void init(Config.Scope config) {
} }
@Override @Override
public void postInit(KeycloakSessionFactory factory) { public void postInit(KeycloakSessionFactory factory) {
} }
@Override @Override
public void close() { public void close() {
} }
@Override @Override
public String getId() { public String getId() {
return "myThemeSelector"; return "myThemeSelector";
} }
} }
---- ----
@ -68,9 +68,9 @@ public class MyThemeSelectorProvider implements ThemeSelectorProvider {
return "my-theme"; return "my-theme";
} }
@Override @Override
public void close() { public void close() {
} }
} }
---- ----
@ -233,7 +233,7 @@ For example to disable the Infinispan user cache provider add:
The service providers can be packaged within any Java EE component so long as you set up the `META-INF/services` The service providers can be packaged within any Java EE component so long as you set up the `META-INF/services`
file correctly to point to your providers. For example, if your provider needs to use third party libraries, you file correctly to point to your providers. For example, if your provider needs to use third party libraries, you
can package up your provider within an ear and store these third pary libraries in the ear's `lib/` directory. can package up your provider within an ear and store these third party libraries in the ear's `lib/` directory.
Also note that provider jars can make use of the `jboss-deployment-structure.xml` file that EJBs, WARS, and EARs Also note that provider jars can make use of the `jboss-deployment-structure.xml` file that EJBs, WARS, and EARs
can use in a {appserver_name} environment. See the {appserver_name} documentation for more details on this file. It can use in a {appserver_name} environment. See the {appserver_name} documentation for more details on this file. It
allows you to pull in external dependencies among other fine grain actions. allows you to pull in external dependencies among other fine grain actions.
@ -283,7 +283,7 @@ You must put the `@Remove` annotation on the `close()` method of your provider.
will never be cleaned up and you may eventually see error messages. will never be cleaned up and you may eventually see error messages.
Implementations of `ProviderFactory` are required to be plain java objects. Your factory class would Implementations of `ProviderFactory` are required to be plain java objects. Your factory class would
perform a JNDI lookup of the Stateful EJB in its create() method. perform a JNDI lookup of the Stateful EJB in its `create()` method.
[source,java] [source,java]
---- ----
@ -307,4 +307,4 @@ public class EjbExampleUserStorageProviderFactory
=== Available SPIs === Available SPIs
If you want to see list of all available SPIs at runtime, you can check `Server Info` page in admin console as described in <<_providers_admin_console,Admin Console>> section. If you want to see list of all available SPIs at runtime, you can check `Server Info` page in admin console as described in <<_providers_admin_console,Admin Console>> section.