如何将持久性单元的JPA EntityManagerFactory设置为非“默认" [英] How to set JPA EntityManagerFactory for persistence unit NOT to 'default'

查看:1007
本文介绍了如何将持久性单元的JPA EntityManagerFactory设置为非“默认"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

毫无疑问,Spring-boot的所有默认配置都可以.但是现在我需要将应用程序部署到Weblogic 12.2 Server上,并且遇到一些有关持久性的问题.

Noramlly all the default configurations of Spring-boot are totally fine. But now I need to deploy my application to a Weblogic 12.2 Server and I am facing some issues regarding persistence.

我只是想知道如何将持久性单元的JPA EntityManagerFactory设置为默认".因为通过启动应用程序,我可以看到那些日志:

I just wondering how to set the JPA EntityManagerFactory for persistence unit NOT to 'default'. Because by startup of the application I can see those logs:

2017-05-23 08:16:34.608  INFO 30827 - j.LocalContainerEntityManagerFactoryBean []: Building JPA container EntityManagerFactory for persistence unit 'default'
2017-05-23 08:16:35.090  INFO 30827 - o.hibernate.jpa.internal.util.LogHelper  []: HHH000204: Processing PersistenceUnitInfo [
    name: default
    ...]
2017-05-23 08:16:36.025  INFO 30827 - org.hibernate.Version                    []: HHH000412: Hibernate Core {5.0.11.Final}
2017-05-23 08:16:36.026  INFO 30827 - org.hibernate.cfg.Environment            []: HHH000206: hibernate.properties not found
2017-05-23 08:16:36.029  INFO 30827 - org.hibernate.cfg.Environment            []: HHH000021: Bytecode provider name : javassist
2017-05-23 08:16:36.925  INFO 30827 - o.hibernate.annotations.common.Version   []: HCANN000001: Hibernate Commons Annotations {5.0.1.Final}
2017-05-23 08:16:39.632  INFO 30827 - org.hibernate.dialect.Dialect            []: HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect
2017-05-23 08:16:48.205  INFO 30827 - j.LocalContainerEntityManagerFactoryBean []: Initialized JPA EntityManagerFactory for persistence unit 'default'
2017-05-23 08:16:55.348  INFO 30827 - o.h.h.i.QueryTranslatorFactoryInitiator  []: HHH000397: Using ASTQueryTranslatorFactory

所以我不确定weblogic是使用默认的持久性单元(eclipselink)还是真正休眠.因此,我正在考虑在我的spring-boot应用程序中的任何位置显式设置持久性单元.

So I am not sure if weblogic is using the default persistence unit (eclipselink) or really hibernate. So I was thinking to set the persistence unit explicity anywhere in my spring-boot application.

有什么方法可以将休眠设置为显式默认单位?

Is there any way to set hibernate as default unit explicit?

我之前曾问过这个问题,因为我在运行时遇到了异常. org.eclipse.persistence库用于解组xml.

I was asking this before because I get an exception by runtime. The org.eclipse.persistence libraries are used for unmarshalling xml.

Caused by: org.eclipse.persistence.exceptions.DescriptorException: 
Exception Description: No conversion value provided for the value [ToConfirm] in field [@SubStatus].
Mapping: org.eclipse.persistence.oxm.mappings.XMLDirectMapping[subStatus-->@SubStatus]
Descriptor: XMLDescriptor(at.myCompany.bookingHubClient.schema.BookingHubUserTypes.BookResponse --> [DatabaseTable(BookResponse)])
    at org.eclipse.persistence.exceptions.DescriptorException.noFieldValueConversionToAttributeValueProvided(DescriptorException.java:1066)
    at org.eclipse.persistence.mappings.converters.ObjectTypeConverter.convertDataValueToObjectValue(ObjectTypeConverter.java:226)
    at org.eclipse.persistence.jaxb.JAXBEnumTypeConverter.convertDataValueToObjectValue(JAXBEnumTypeConverter.java:119)
    at org.eclipse.persistence.oxm.mappings.XMLDirectMapping.convertDataValueToObjectValue(XMLDirectMapping.java:528)
    at org.eclipse.persistence.oxm.mappings.XMLDirectMapping.getAttributeValue(XMLDirectMapping.java:296)
    at org.eclipse.persistence.oxm.mappings.XMLDirectMapping.getAttributeValue(XMLDirectMapping.java:1)
    at org.eclipse.persistence.internal.oxm.XMLDirectMappingNodeValue.attribute(XMLDirectMappingNodeValue.java:169)
    at org.eclipse.persistence.internal.oxm.record.UnmarshalRecordImpl.startElement(UnmarshalRecordImpl.java:922)
    at org.eclipse.persistence.internal.oxm.record.SAXUnmarshallerHandler.startElement(SAXUnmarshallerHandler.java:373)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:380)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:614)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3135)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:880)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:118)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
    at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
    at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:133)
    at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:173)
    at org.eclipse.persistence.internal.oxm.record.XMLReader.parse(XMLReader.java:243)
    at org.eclipse.persistence.internal.oxm.record.SAXUnmarshaller.unmarshal(SAXUnmarshaller.java:401)
    at org.eclipse.persistence.internal.oxm.record.SAXUnmarshaller.unmarshal(SAXUnmarshaller.java:654)
    at org.eclipse.persistence.internal.oxm.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:581)
    at org.eclipse.persistence.jaxb.JAXBUnmarshaller.unmarshal(JAXBUnmarshaller.java:323)
    at org.glassfish.jersey.jaxb.internal.XmlRootElementJaxbProvider.readFrom(XmlRootElementJaxbProvider.java:140)
    at org.glassfish.jersey.jaxb.internal.AbstractRootElementJaxbProvider.readFrom(AbstractRootElementJaxbProvider.java:134)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.invokeReadFrom(ReaderInterceptorExecutor.java:256)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:235)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:155)
    at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1085)
    at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:852)
    at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:786)
    at org.glassfish.jersey.client.ClientResponse.readEntity(ClientResponse.java:326)
    at org.glassfish.jersey.client.InboundJaxrsResponse$1.call(InboundJaxrsResponse.java:115)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
    at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:419)
    at org.glassfish.jersey.client.InboundJaxrsResponse.runInScopeIfPossible(InboundJaxrsResponse.java:267)
    at org.glassfish.jersey.client.InboundJaxrsResponse.readEntity(InboundJaxrsResponse.java:112)
    at at.myCompany.bookingHubClient.client.RestClient.doWSCallBook(RestClient.java:85)
    at at.myCompany.thirdPartyBookingService.service.impl.hotel.BookResponseServiceImpl.getBookResponse(BookResponseServiceImpl.java:36)
    ... 78 common frames omitted

当然,我看到有转换问题,但是在tomcat上它正在运行,并且我不使用任何eclipse库.因此,意味着任何weblogic库都将取代我的库.

Sure I see there is a conversion issue, but on tomcat its running and I dont use any eclipse libraries. So means any library of weblogic is overriding mine.

此行出现异常:

 javax.ws.rs.core.Response bookResponse = response.readEntity(BookResponse.class);

有什么想法可以让应用再次运行吗?

Any idea to get the app running again?

这是我的weblogic.xml:

This is my weblogic.xml:

<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app
    xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app
        http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd">
    <wls:context-root>/third-party-booking-service</wls:context-root>
    <wls:container-descriptor>
        <wls:prefer-application-packages>
            <wls:package-name>org.slf4j.*</wls:package-name>
            <wls:package-name>org.springframework.*</wls:package-name>
            <wls:package-name>com.google.common.*</wls:package-name>
            <wls:package-name>javax.annotation.*</wls:package-name>
            <wls:package-name>com.sun.jersey.*</wls:package-name>
            <wls:package-name>org.codehaus.jackson.jaxrs.*</wls:package-name>
            <wls:package-name>org.jboss.logging.*</wls:package-name>
            <wls:package-name>org.hibernate.*</wls:package-name>
            <wls:package-name>com.fasterxml.*</wls:package-name>
            <wls:package-name>org.glassfish.jersey.jaxb.*</wls:package-name>
            <wls:package-name>antlr.*</wls:package-name>
        </wls:prefer-application-packages>
    </wls:container-descriptor>
</wls:weblogic-web-app>

推荐答案

如果对某人有帮助,以下内容可在WebSphere ND 8.5.5.15/16上为我工作.我正在使用的Spring引导版本是2.1.8.RELEASE,它可以通过后续的升级工作到最新的2.3.4.

In case it helps someone, the following works for me on WebSphere ND 8.5.5.15/16. The Spring boot version i am using is 2.1.8.RELEASE, and it works through subsequent upgrades up to the latest 2.3.4.

@Configuration
public class JPAConfiguration {
    
    @Bean
    public LocalContainerEntityManagerFactoryBean entityManagerFactory() {
        LocalContainerEntityManagerFactoryBean em = new LocalContainerEntityManagerFactoryBean();
        em.setDataSource(dataSource());

        em.setPackagesToScan(new String[] { "com.example.model" });
        em.setPersistenceUnitName("org.hibernate.jpa.HibernatePersistenceProvider");

        HibernateJpaVendorAdapter vendorAdapter = new HibernateJpaVendorAdapter();
        vendorAdapter.setGenerateDdl(false);
        em.setJpaVendorAdapter(vendorAdapter);

        return em;
    }
    
    @Bean
    public DataSource dataSource(){
        DriverManagerDataSource dataSource = new DriverManagerDataSource();
       
        dataSource.setDriverClassName("oracle.jdbc.OracleDriver");
        dataSource.setUrl("jdbc:oracle:thin:@xx.xx.xx.xx:xxxx:db");
        dataSource.setUsername("username");
        dataSource.setPassword("password");

        return dataSource;
    }
}

如果您想了解有关LocalContainerEntityManagerFactoryBean的更多信息,则文档为

If you want more information about LocalContainerEntityManagerFactoryBean, the documentation is here. The important part is:

FactoryBean根据JPA的创建一个JPA EntityManagerFactory 标准容器自举合同.这是最强大的方法 在Spring应用程序中设置共享的JPA EntityManagerFactory 语境;然后可以将EntityManagerFactory传递给基于JPA的DAO 通过依赖注入.请注意,切换到JNDI查找或 LocalEntityManagerFactoryBean的定义只是一个问题 配置!

FactoryBean that creates a JPA EntityManagerFactory according to JPA's standard container bootstrap contract. This is the most powerful way to set up a shared JPA EntityManagerFactory in a Spring application context; the EntityManagerFactory can then be passed to JPA-based DAOs via dependency injection. Note that switching to a JNDI lookup or to a LocalEntityManagerFactoryBean definition is just a matter of configuration!

与LocalEntityManagerFactoryBean一样,配置设置为 通常从驻留在META-INF/persistence.xml配置文件中的文件读取 在类路径中,根据常规JPA配置 合同.但是,此FactoryBean更加灵活,因为您可以 覆盖persistence.xml文件的位置,指定JDBC 链接到的数据源,等等.

As with LocalEntityManagerFactoryBean, configuration settings are usually read in from a META-INF/persistence.xml config file, residing in the class path, according to the general JPA configuration contract. However, this FactoryBean is more flexible in that you can override the location of the persistence.xml file, specify the JDBC DataSources to link to, etc.

这篇关于如何将持久性单元的JPA EntityManagerFactory设置为非“默认"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆