geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-5874) Merge global context(jca) in KernelContextGbean into blueprint service jcaContextProvider
Date Tue, 22 Mar 2011 08:11:06 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009579#comment-13009579
] 

Ivan commented on GERONIMO-5874:
--------------------------------

Personally, I would like to leave the jca context there, as in the past, it is used to bind
the some resources from system and users, if there are users looking up resources with absolute
jndi name in this context, it would be easy for them to migrate their applications. What we
need to do now is just to update the kernelContextGBean to make sure those resources are binded
to the specified context correctly.

> Merge global context(jca) in KernelContextGbean into blueprint service jcaContextProvider
> -----------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5874
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5874
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: naming
>    Affects Versions: 3.0
>            Reporter: viola.lu
>            Assignee: viola.lu
>            Priority: Minor
>             Fix For: 3.0
>
>
> Before 3.0, all resource are bound to global context with jca prefix. But in 3.0, now
jca is exposed as blueprint service for use:
> <service id="jcaContextProvider"
>              interface="javax.naming.spi.ObjectFactory">
>         <service-properties>
>             <entry key="osgi.jndi.url.scheme" value="jca"/>
>         </service-properties>
>         <bean class="org.apache.geronimo.naming.WritableURLContextFactory">
>             <argument>
>                 <value>jca</value>
>             </argument>
>         </bean>
>     </service>
> So have to update KernelContextGBean, bind all gbeans implemented resourcesource interface
to jcaContextProvider 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message