ServiceMix无法找到OSGI数据源

时间：2015-04-24 03:47:01

标签： java osgi openjpa blueprint-osgi apache-servicemix

我一直在深入研究ServiceMix 5.4.0和OSGi，并且在OpenJPA中遇到了一种相当奇怪的行为。

我有一个像这样定义的数据源：

<blueprint
        xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd">

    <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
        <property name="driverClassName" value="org.postgresql.Driver"/>
        <property name="url" value="jdbc:postgresql://localhost:5432/test"/>
        <property name="username" value="test"/>
        <property name="password" value="test"/>
    </bean>

    <service interface="javax.sql.DataSource" ref="dataSource">
      <service-properties>
        <entry key="osgi.jndi.service.name" value="jdbc/test"/>
      </service-properties>
    </service>
</blueprint>

使用jndi：names命令，我可以验证数据源是否可见：

karaf@root> jndi:names
JNDI Name            Class Name                                                  
osgi:service/jndi    org.apache.karaf.jndi.internal.JndiServiceImpl              
osgi:service/jdbc/test org.apache.commons.dbcp.BasicDataSource                     
karaf@root>

我的persistence.xml：

<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">

    <persistence-unit name="test" transaction-type="JTA">               
        <jta-data-source>osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/test)</jta-data-source>

        <class>com.example.persistence.security.User</class>

        <exclude-unlisted-classes>true</exclude-unlisted-classes>

        <properties>
            <property name="openjpa.jdbc.DBDictionary" value="postgres"/>                       
            <property name="openjpa.Log" value="slf4j"/>
        </properties>
    </persistence-unit>
</persistence>

然后我通过Blueprint将持久性单元注入DAO类：

<?xml version="1.0" encoding="UTF-8"?>

<blueprint  default-activation="eager" 
            xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
            xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.0.0"
            xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.0.0">

    <bean id="securityDAO" class="com.example.security.dao.SecurityDAOImpl" init-method="init">
        <tx:transaction method="*" value="Required" />
        <jpa:context property="entityManager" unitname="test" />
    </bean>

    <service ref="securityDAO" interface="com.example.security.dao.SecurityDAO">
    </service>


</blueprint>

成功注入了持久性单元，我在DAO的init方法中验证了这一点：

public void init() {
    if (em==null) {
        log.error("Entity manager not found. Check JPA configuration.");
        throw new RuntimeException("No EntityManager found");
    }

    log.info("Started SecurityDAO");
}

在我辛勤工作之后，当我从另一个bean调用我的DAO方法时，ServiceMix会给我以下一个神秘的异常：

....
public void setSecurityDAO (SecurityDAO dao) {
    this.dao = dao;
}

@Override
protected void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
    String userName = req.getParameter("userName");
    String password = req.getParameter("password");

    // Invocation of injected DAO results in exception
    User u = dao.authenticateUser(userName, password);

这导致以下结果：

Caused by: java.lang.RuntimeException: The DataSource osgi:service/javax.sql.DataSource/(osgi.jndi.service.name=jdbc/test) required by bundle persistence/0.0.1.SNAPSHOT could not be found.
    at org.apache.aries.jpa.container.unit.impl.JndiDataSource.getDs(JndiDataSource.java:87)
    at org.apache.aries.jpa.container.unit.impl.DelayedLookupDataSource.getConnection(DelayedLookupDataSource.java:36)
    at org.apache.openjpa.lib.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:116)
    at org.apache.openjpa.lib.jdbc.DecoratingDataSource.getConnection(DecoratingDataSource.java:93)
    at org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:233)
    ... 54 more
Caused by: javax.naming.NoInitialContextException: Unable to find the InitialContextFactory org.eclipse.jetty.jndi.InitialContextFactory.
    at org.apache.aries.jndi.ContextHelper.getInitialContext(ContextHelper.java:148)
    at org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:49)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
    at javax.naming.InitialContext.init(InitialContext.java:244)
    at javax.naming.InitialContext.<init>(InitialContext.java:216)
    at org.apache.aries.jpa.container.unit.impl.JndiDataSource.getDs(JndiDataSource.java:64)
    ... 58 more

某种程度上，OSGi导出的数据源没有进入持久性捆绑包。奇怪的是，当我将以下代码添加到init-method以查看是否可以执行测试查询时，OpenJPA不仅不会在init方法中抛出异常，而是调用现在触发异常的DAO同样有效：

public void init() {
    if (em==null) {
        log.error("Entity manager not found. Check JPA configuration.");
        throw new RuntimeException("No EntityManager found");
    }

    try {
        Query q = em.createNativeQuery("SELECT 1=1");           
        q.getFirstResult();         
    } catch (Exception ex) {
        log.error("Unable to execute test query against database", ex);
        throw new RuntimeException(ex);
    }

    log.info("Started SecurityDAO");
}

因此，总结一下：如果我从与我的DAO不同的包调用方法，OpenJPA会抛出一个异常，表明它找不到InitialNamingContext，并且在日志中没有显示它已启动的任何指示。如果我在外部组件调用它之前在我的DAO中执行查询，OpenJPA以某种方式能够找到InitialNamingContext，OpenJPA显示在日志中，并且来自DAO包外部的后续调用开始工作。

显然，我在这里遗漏了一些基本的东西。我们将非常感谢任何帮助或深思熟虑的解释，或者我做错了什么。

编辑：

我昨晚没有注意到，但是当我在测试查询中添加时，日志中会出现以下行。当我评论该查询时，它们不存在：

... | Runtime | 220 - org.apache.openjpa - 2.3.0 | Starting OpenJPA 2.3.0
... | JDBC    | 220 - org.apache.openjpa - 2.3.0 | Using dictionary class "org.apache.openjpa.jdbc.sql.PostgresDictionary".
... | JDBC    | 220 - org.apache.openjpa - 2.3.0 | Connected to PostgreSQL version 9.9 using JDBC driver PostgreSQL Native Driver version PostgreSQL 9.3 JDBC4.1 (build 1102).

编辑2：

在普通香草卡拉夫3.0.3上尝试过，并得到了同样的错误。作为一种解决方法，我在bundle中创建了一个单独的bean来执行上述测试查询。显然，只要捆绑中的单个bean在捆绑包外的bean尝试进行调用之前调用OpenJPA，OpenJPA就会被正确初始化。

由于我在OpenJPA / ServiceMix文档中无处可见，我只能假设我在配置的其他地方做错了。

编辑3：

Per John Forth，这是MANIFEST.MF 

Manifest-Version: 1.0
Bnd-LastModified: 1430533396366
Build-Jdk: 1.8.0_45
Built-By: somedude
Bundle-Blueprint: OSGI-INF/blueprint/blueprint.xml
Bundle-Description: Database access layer for Peer Review product
Bundle-ManifestVersion: 2
Bundle-Name: Example :: Persistence
Bundle-SymbolicName: persistence-jpa
Bundle-Version: 0.0.1.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: com.example.persistence.security;version="0.0.1.SNAPSHOT",co
 m.example.security.dao;version="0.0.1.SNAPSHOT";uses:="com.example.persistence.
 security,javax.persistence"
Export-Service: com.example.security.dao.SecurityDAO
Import-Package: javax.persistence;version="[1.1,2)",org.osgi.service.blu
 eprint;version="[1.0.0,2.0.0)",org.slf4j;version="[1.7,2)"
Meta-Persistence: META-INF/persistence.xml
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.7))"
Tool: Bnd-2.3.0.201405100607

并且，由于它可能是相关的，JPA包的pom.xml：

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <parent>
        <artifactId>example</artifactId>
        <groupId>com.example</groupId>
        <version>0.0.1-SNAPSHOT</version>
    </parent>

    <artifactId>persistence-jpa</artifactId>
    <packaging>bundle</packaging>

    <name>Example :: Persistence</name>

    <dependencies>
        <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-jpa_2.0_spec</artifactId>
            <version>1.1</version>
        </dependency>

        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
            <version>1.7.7</version>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.3</version>
                <configuration>
                    <source>1.7</source>
                    <target>1.7</target>
                </configuration>
            </plugin>

            <plugin>
                <groupId>org.apache.felix</groupId>
                <artifactId>maven-bundle-plugin</artifactId>
                <version>2.5.3</version>
                <extensions>true</extensions>
                <configuration>
                    <instructions>
                        <Meta-Persistence>META-INF/persistence.xml</Meta-Persistence>
                        <Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
                        <Bundle-Version>${project.version}</Bundle-Version>                     
                        <Import-Package>*</Import-Package>
                        <Export-Package>com.example.persistence*,com.example.security.*;version=${project.version}</Export-Package>
                    </instructions>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>

1 个答案:

答案 0 :(得分：0)

如果您使用的是OSGI，则可以在MANIFEST.MF文件中定义类可见性。

因此，持久性bundle只能查看和加载在其MANIFEST.MF中导入的类。

扩展现有捆绑包的正确方法是定义附加到现有捆绑包的片段。这样，您可以提供类（例如DAO）和文件（例如persistence.xml）并使片段主机可见。

MANIFEST.MF看起来像

Bundle-ManifestVersion: 2
Bundle-Name: foo.bar.openjpa-fragment
Bundle-SymbolicName: foo.bar.openjpa-fragment;singleton:=true
Bundle-Version: 0.0.1.SNAPSHOT
Bundle-Vendor: foo bar
Fragment-Host: org.apache.openjpa-bundle
Bundle-ClassPath: .

请注意，这只是一个例子。

OSGI意味着提供适当的可见性。

您可以向现有捆绑包添加多个片段，例如将配置保存在单独的捆绑包中，这样可以更轻松地切换配置。

相关问题
最新问题