The configuration for the JBoss JCA container is located in the config/ directory.
The JBoss JCA container uses JBoss Logging framework as the implementation.
The configuration is done in the
config/logging.properties
file.
Consult the JBoss Logging documentation on how the service can be configured.
The JBoss JCA container uses the JBoss Transaction Manager as its transaction implementation.
The configuration is done in the
config/transaction.xml
file.
Consult the JBoss Transaction documentation on how the service can be configured.
The JBoss JCA deployer is configured in the
config/bootstrap/jca.xml
file, as the
<bean name="RADeployer"
interface="com.github.fungal.spi.deployers.Deployer"
class="org.jboss.jca.deployers.fungal.RADeployer">
<depends>BeanValidation</depends>
<depends>WorkManager</depends>
</bean>
bean.
Table 5.1. JCA Deployer
| Property | Type | Description |
|---|---|---|
| ArchiveValidation | boolean |
Toggle archive validation for the deployment units.
Default: true |
| ArchiveValidationFailOnWarn | boolean |
Should an archive validation warning report fail the deployment.
Default: false |
| ArchiveValidationFailOnError | boolean |
Should an archive validation error report fail the deployment.
Default: true |
| BeanValidation | boolean |
Toggle bean validation (JSR-303) for the deployment units.
Default: true |
| DefaultBootstrapContext | org.jboss.jca.core.api.CloneableBootstrapContext | Specifies the default bootstrap context for resource adapters |
| BootstrapContexts | Map<String, org.jboss.jca.core.api.CloneableBootstrapContext> | Bootstrap context map (unique name to a cloneable bootstrap context) which allows developers to bind (through jboss-ra.xml) their resource adapter to a specific bootstrap context instance. |
| PrintStream | java.io.PrintStream | Specifies which print stream that should be used to handle the LogWriters |
| ScopeDeployment | boolean |
Should each deployment be scoped (isolated) from the container. This feature allows
deployment of libraries of a different version than used in the container environment.
Default: false |
The Java EE Connector Architecture 1.6 specification allows units of javax.resource.spi.Work to be executed in a specific security context.
This is done through the use of Java Authentication Service Provider Interface for Containers (JSR-196) call backs using the javax.security.auth.callback.Callback interface.
The support is activated by letting the work instance implement the
javax.resource.spi.work.WorkContextProvider
interface and returning an instance of javax.resource.spi.work.SecurityContext.
There is currently support for injecting a user/roles setup based on the files
config/users.properties
config/roles.properties
The format of the users.properties file is
username1=password1
username2=password2
The format of the roles.properties file is
username1=role1,role2
username2=role3,role4
The user/roles setup can be configured through the UsersRoles bean in the config/bootstrap/jca.xml file.
<!-- Users / roles -->
<bean name="UsersRoles"
interface="org.jboss.jca.core.spi.security.Callback"
class="org.jboss.jca.core.security.UsersRoles">
<property name="UsersProperties">${jboss.jca.home}/config/users.properties</property>
<property name="RolesProperties">${jboss.jca.home}/config/roles.properties</property>
</bean>
The JBoss JCA project features a web server which is used to serve web archive deployments.
The configuration is done in the
system/web.xml
file.
The web server can be removed from the environment by removing the web.xml file in
system/
Furthermore all .WAR files in the same directory should be removed too.