blocks|key|5134420|text|您有两种可能性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5134421|为您的系统实现一个符合JDBC的驱动程序，这样您就可以“直接”使用Hibernate之类的JPA实现(尽管您可能需要为您的系统创建自定义方言)。|5134422|直接使用JPA规范进行编程，就像ObjectDB所做的那样，它完全绕过了SQL和JPA实现的需要。|offset|length|5134423|后一种方法可能更简单，但您仍然需要实现完整的JPA+API。如果它是一个自定义的内部系统，那么做任何一个都没有什么意义。|5134424|entityMap|0|LINK|mutability|MUTABLE|url|https://www.objectdb.com/^0|0|0|G|8|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

You have two possibilities.

Implement a JDBC compliant driver for your system, so you can use a JPA implementation such as Hibernate "directly" (although you may need to create a custom dialect for your system).

Program directly against the JPA specification like <a href="https://www.objectdb.com/" rel="nofollow noreferrer">ObjectDB</a> does, which bypasses the need to go through SQL and JPA implementations completely.

The latter one is probably easier, but you'd still need to implement the full JPA API. If it's a custom in-house-only system, there's very little sense in doing either one.

blocks|key|1012271|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1012272|1012273|使用像H2这样的现有数据库实现，并将其与JPA集成在一起。|ordered-list-item|1012274|在这个数据库中，创建一个H2存储过程或函数，并通过JPA从当前应用程序中调用它。有关如何创建this+H2+documentation存储过程或函数的信息，请参阅Java。(您可能还想浏览“将函数用作表”一节。)|offset|length|1012275|为服务方法定义了一个协议，并将其封装在一个模型类中。可以将此模型类的实例传递给函数/SP并检索响应。|1012276|1012277|警告：我自己从来没有这样做过，但我认为它会起作用的。|style|BOLD|1012278|1012279|尽管该图单独显示了H2，但它很可能与“您的Java/JEE应用程序”在同一个JVM中。但是，由于不需要使用H2，因此我将其显示为单独的实体。|1012280|​|1012281|📷|atomic|1012282|1012283|entityMap|0|LINK|mutability|MUTABLE|url|http://www.h2database.com/html/features.html#user_defined_functions|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6137649d8021dd3f0594f502a0cf4d10.png|imageAlt^0|0|0|0|1A|L|0|0|0|0|0|2|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|-4|4|5|6|1C|7|@]|8|@]|9|$]]|$1|A|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]|$1|B|3|C|4|D|6|1E|7|@]|8|@]|9|$]]|$1|E|3|F|4|D|6|1F|7|@]|8|@$G|1G|H|1H|1|1I]]|9|$]]|$1|I|3|J|4|D|6|1J|7|@]|8|@]|9|$]]|$1|K|3|-4|4|5|6|1K|7|@]|8|@]|9|$]]|$1|L|3|M|4|5|6|1L|7|@$G|1M|H|1N|N|O]]|8|@]|9|$]]|$1|P|3|-4|4|5|6|1O|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|1P|7|@]|8|@]|9|$]]|$1|S|3|T|4|5|6|1Q|7|@]|8|@]|9|$]]|$1|U|3|V|4|W|6|1R|7|@]|8|@$G|1S|H|1T|1|1U]]|9|$]]|$1|X|3|T|4|5|6|1V|7|@]|8|@]|9|$]]|$1|Y|3|-4|4|5|6|1W|7|@]|8|@]|9|$]]]|Z|$10|$4|11|12|13|9|$14|15]]|16|$4|17|12|18|9|$19|1A|1B|-4]]]]

One idea I thought up just now, that I feel may work is this:

<ol>
<li>Use an existing database implementation like H2 and use the JPA integration with that. H2 already has a JPA integration libraries, so it should be easy.</li>
<li>In this database, create a Java stored procedure or function and call it from your current application through JPA. See <a href="http://www.h2database.com/html/features.html#user_defined_functions" rel="nofollow noreferrer">this H2 documentation</a> on how to create a Java stored procedure or function. (You may want to explore the section "Using a Function as a Table" also.)</li>
<li>Define a protocol for the service methods and encapsulate it in a model class. An instance of this model class may be passed to the function/SP and responses retrieved.</li>
</ol>

Caveat: I have never done this myself but I think it will work.

<hr>

Edit: Here is a diagram representing the thought. Though the diagram show H2 separately, it will most probably be in the same JVM as "Your Java/JEE application". However, since it is not necessary to use H2, I have shown it as as separate entity.

<a href="https://i.stack.imgur.com/3So27.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3So27.png" alt="enter image description here"></a>

We have a (possibly large) custom data structure implemented in Java (8+). It has a simple and optimal API for querying pieces of data. The logical structure is roughly similar to an RDMS (it has e. g. relations, columns, primary keys, and foreign keys), but there is no SQL driver.

The main goal is to access the data via ORM (mapping logical entities to JPA annotated beans). It would be nice if we could use JPQL. Hibernate is preferred but other alternatives are welcome too.

What is the simplest way to achieve this? Which are the key parts of such an implementation?

(P. S. Directly implementing <code>SessionImplementor</code>, <code>EntityManagerImplementor</code> etc. seems to be too complicated.)

How to map custom data structures to bean entities with JPA/Hibernate?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们有一个用Java (8+)实现的(可能很大的)自定义数据结构。它有一个简单而优化的API来查询数据片段。逻辑结构大致类似于RDMS (例如，它具有关系、列、主键和外键)，但没有SQL驱动程序。主要目标是通过ORM访问数据(将逻辑实体映射到JPA带注释的bean)。如果我们可以使用JPQL，那就太好了。Hiberna...

问如何使用JPA/Hibernate将自定义数据结构映射到bean实体？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用JPA/Hibernate将自定义数据结构映射到bean实体？EN