[JBoss JIRA] Created: (JBJCA-482) Add spy functionality to JDBC resource adapter
by Jesper Pedersen (JIRA)
Add spy functionality to JDBC resource adapter
----------------------------------------------
Key: JBJCA-482
URL: https://issues.jboss.org/browse/JBJCA-482
Project: IronJacamar
Issue Type: Task
Components: JDBC
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Add functionality to the JDBC resource adapter such that statements executed are logged against a special logger instance - if enabled (boolean spy). Default value is false.
General methods - like execute(String) and close() - should be logged at INFO level.
Control methods - like rollback() and commit() - should be logged at DEBUG level.
It should be possible to identify the statements based on the deployed datasource name.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Resolved: (JBJCA-26) Making JCA security more pluggable
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-26?page=com.atlassian.jira.plugin.s... ]
Jesper Pedersen resolved JBJCA-26.
----------------------------------
Resolution: Out of Date
> Making JCA security more pluggable
> ----------------------------------
>
> Key: JBJCA-26
> URL: https://issues.jboss.org/browse/JBJCA-26
> Project: IronJacamar
> Issue Type: Feature Request
> Components: Core
> Reporter: Adrian Brock
> Assignee: Jesper Pedersen
>
> We need a mechanism to make JCA security more pluggable.
> This is to cater for use cases where some extra context needs to be used.
> The connection manager only understands a subject.
> The connection factory (e.g. DataSource) only understands the CRI (method parameters).
> The pooling uses both without needing to understand what they are in detail.
> This change would provide a "wrapper" connection manager that can do things
> more associated to context, e.g. it could be connection factory specific,
> i.e. it understands the CRI and can do things that the connection factory doesn't do
> or it can do things based on information.
> An example of other information would allowing a per deployment
> security domain such that you have different pre-configured user/password per ejb.
> With something like the following in META-INF/jboss-[web].xml
> <jboss>
> <enterprise-beans>
> <session>
> <ejb-name>Whatever</ejb-name>
> ...
> <resource-ref>
> <res-ref-name>jdbc/DataSource</res-ref-name>
> <jndi-name>java:/MySQLDS</jndi-name>
> <security-domain>FooBar</security-domain>
> </resource-ref>
> </session>
> </enterprise-beans>
> </jboss>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months