You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2010/03/04 19:07:27 UTC
[jira] Created: (GERONIMO-5170) Register connection factories in
osgi service registry
Register connection factories in osgi service registry
------------------------------------------------------
Key: GERONIMO-5170
URL: https://issues.apache.org/jira/browse/GERONIMO-5170
Project: Geronimo
Issue Type: New Feature
Security Level: public (Regular issues)
Components: connector, osgi, persistence
Affects Versions: 3.0
Reporter: David Jencks
Assignee: David Jencks
Fix For: 3.0
The aries jpa implementation tries to look up jta-datasource and non-jta-datasource in jndi using the osgi jndi service scheme. If we stuff all our connectio n factories in the service registry this ought to work.
We can consider using this for ee jpa too, but this would be a significant change in behavior in terms of visibility. The osgi service registry is global whereas the current lookup is confined to the DAG of ancestors of the jpa module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5170) Register connection factories in
osgi service registry
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor reassigned GERONIMO-5170:
-------------------------------------
Assignee: Jarek Gawor (was: David Jencks)
> Register connection factories in osgi service registry
> ------------------------------------------------------
>
> Key: GERONIMO-5170
> URL: https://issues.apache.org/jira/browse/GERONIMO-5170
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: connector, osgi, persistence
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> The aries jpa implementation tries to look up jta-datasource and non-jta-datasource in jndi using the osgi jndi service scheme. If we stuff all our connectio n factories in the service registry this ought to work.
> We can consider using this for ee jpa too, but this would be a significant change in behavior in terms of visibility. The osgi service registry is global whereas the current lookup is confined to the DAG of ancestors of the jpa module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5170) Register connection factories in
osgi service registry
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850280#action_12850280 ]
Jarek Gawor commented on GERONIMO-5170:
---------------------------------------
Changes committed in revision 928000. I also added "jndi-name" to the geronimo-connection-1.2.xsd to specify the jndi name for lookups via osgi:service/ scheme. If "jndi-name" element is not specified, a default jndi-name will be generated.
> Register connection factories in osgi service registry
> ------------------------------------------------------
>
> Key: GERONIMO-5170
> URL: https://issues.apache.org/jira/browse/GERONIMO-5170
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: connector, osgi, persistence
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> The aries jpa implementation tries to look up jta-datasource and non-jta-datasource in jndi using the osgi jndi service scheme. If we stuff all our connectio n factories in the service registry this ought to work.
> We can consider using this for ee jpa too, but this would be a significant change in behavior in terms of visibility. The osgi service registry is global whereas the current lookup is confined to the DAG of ancestors of the jpa module.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.