Actually, SDO object is a common but special DTO object.
It has some dynamic feature similiar to XML, what's more, it has no static
setter/getter method, so hibernate won't recognize it as a JavaBean object
dynamic-map mode in hibernate is good, but not enough, I'm not sure whether it can
support inheritance and relationship as good as POJO.
----- Original Message -----
From: "Max Rydahl Andersen" <max.andersen(a)jboss.com>
To: "Eta Huang" <huangkai(a)primeton.com>
Sent: Wednesday, October 11, 2006 4:48 PM
Subject: Re: [hibernate-dev] What is the easiest and safest way to customize Hiberate for
other entity mode?
On Wed, 11 Oct 2006 04:10:56 +0200, Eta Huang
<huangkai(a)primeton.com>
wrote:
> Hi all:
> I'm developing SDO(Service Data Object) implementation, and when I
> wanna persist them Hibernate is the first one came to my mind. I tried
> it's dynamic-map mode, but that's not what i expected, I want to
> customize Hibernate to make it full SDO support. For the sake of safety,
> the minimal classes needed to be overrided or changed, the better.
> Any hibernate guru can show me the right way? very thankful!
What are the problems you are forseeing with SDO's ?
Could you sum up the differences there are between a JavaBean and SDO ?
Is SDO's completely dynamic and has no fixed structure ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com