Hibernate代理序列化并在客户端接收
我不了解生成的代理类对象（CGLib增强的POJO）如何传输到远程客户端并仍然保留其生成Lazy Init的能力。例外情况。
这是否意味着存在某种契约，即某种类（代理）的所有转移对象将再次重新实例化为代理？客户端从哪里获取这些生成的类？抱歉，我完全不明白。
I lack understanding of how does the generated proxy class object (CGLib enhanced POJO) is transferred to the remote client and still retains its ability to generate Lazy Init. Exceptions.
Does that mean that there is some kind of contract that all the transferred objects of some kind of class (a proxy) will be reinstantiated as proxies again? Where does the client obtain those generated classes? Sorry, but I totally do not understand.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
因为您的远程客户端应用程序现在依赖于 Hibernate。如果您的远程客户端的类路径上没有 Hibernate，您将收到
NoClassDefFoundError。这表明 Hibernate 的抽象有多么漏洞。基本上，不要通过网络传递对象 - 传递消息（如果您愿意，可以使用消息来创建对象）。
Because your remote client application now has a dependency on Hibernate. If your remote client doesn't have Hibernate on the classpath you'll get a
NoClassDefFoundError. This demonstrates how leaky the abstraction is with Hibernate.Basically, don't pass objects across the network - pass messages (which can then be used to create objects, if you so wish).
代理未初始化。当它们被转移时，它们会丢失最初与之关联的
Session。因此，当尝试在远程端初始化它们时，逻辑上会失败。您可以在发送它们之前使用
Hibernate.initialize(aProxy)完全初始化它们。有关详细信息，请检查 这个答案。
The proxies are uninitialized. When they are transferred, they loose the
Sessionthey were originally associated with. So when an attempt is made to initialize them on the remote side, it logically fails.You can initialize them fully before sending them, using
Hibernate.initialize(aProxy)For more information check this answer.