openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1524) ManagedRuntime does not work for OSGi
Date Mon, 15 Mar 2010 14:04:27 GMT


Donald Woods commented on OPENJPA-1524:

I'd like to create a generic OSGiManagedRuntime class, but as I'm looking at the Aries transaction
module and not seeing how it is being registered in the ServiceRegistry with a common OSGi
name that isn't Aries specific.

        props.put(Constants.SERVICE_PID, getName());
        bundleContext.registerService(ManagedServiceFactory.class.getName(), this, props);

where getName() is -
    public String getName() {
        return "org.apache.aries.transaction";

Shouldn't the Aries TransactionManagerService also be registered as "javax.transaction.TransactionManager"?

> ManagedRuntime does not work for OSGi
> -------------------------------------
>                 Key: OPENJPA-1524
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: osgi
>    Affects Versions: 2.0.0-beta
>            Reporter: Timothy Ward
>            Assignee: Donald Woods
>             Fix For: 2.0.0
> In an OSGi runtime there is no TransactionManager registered in JNDI
> It is possible to use an osgi:services/ lookup, but it is much safer, and better practice
to look up the resource in the OSGi service registry.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message