Home » Eclipse Projects » Riena » Riena with Hibernate on serverside
| |
| Re: Riena with Hibernate on serverside [message #489256 is a reply to message #488857] |
Fri, 02 October 2009 07:03   |
 Jens Mayer
Messages: 19
Registered: September 2009
Location: Hamburg |
Junior Member |
|
|
Hi Stefan,
thanks for your advice. I guess you're right: digging into the serialization/deserialization-mechanism of hessian seems too complex to me and possibly has to be maintained for future hibernate releases.
By now, I took the DTO-way and it's working fine. The only thing I have to think over is how to replicate the data between entity-objects and DTO:
- putting the data from multiple entity-objects in one request-oriented DTO and vice versa (will minimze the transferred data, but harder to maintain)
or
- building a DTO for each entity-class, moving the data between these classes via reflection (might produce a performance issue)
one will see...
Tschüß,
Jens
| Stefan Liebig wrote on Wed, 30 September 2009 10:02 | Hi Jens,
De/serializing objects that require some sort of context (which is not
appropriately reconstructable) is difficult. One thing that you could do
is to create a customized AbstractRienaSerializerFactory that could
handle the de/serialization for those kind of objects. Such factories
can be contributed with the extension point
" org.eclipse.riena.communication.hessian.AbstractSerializerFa ctory ".
However, writing such factories requires some insight into the hessian
de/serialization mechanism.
I would propose to introduce ´data transfer´ objects (pojos) within your
service signature and map them to the hibernate-proxy objects.
Tschüß,
Stefan
jens.mayer1@gmx.de wrote:
> Hi,
>
> actually i'm writing a small example-app with riena remote services and
> hibernate as ORM-Framework on the serverside.
>
> My first approach was to reuse the entity-classes on client-side (making
> hibernate-dependencies optional). Seems not to be a good idea - the
> hessian deserializer throws an LayzyInitializationException when it
> tries to deserialize hibernate-proxy-classes, because there's no
> PersistenceContext available on the client-side. 
> What might be the best practice for this case ?
>
> Thanks in advance,
>
> Jens
|
|
|
|
| Re: Riena with Hibernate on serverside [message #489268 is a reply to message #489256] |
Fri, 02 October 2009 07:52 |
|
This is a multi-part message in MIME format.
--------------050003070701000207080702
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
jens,
you should take a look at Gilead:
Gilead stands for Generic Light Entity Adapter
It permits you to send Persistent entities (and especially the partially
loaded ones) outside the JVM (GWT, Flex, Web-Services, Google AppEngine
....) without pain.
No LazyInitialisationException. No DTO mapping. Just POJO and Domain
Driven Design :)
http://noon.gilead.free.fr/gilead/
ekke
jens.mayer1@gmx.de schrieb:
> Hi Stefan,
>
> thanks for your advice. I guess you're right: digging into the
> serialization/deserialization-mechanism of hessian seems too complex
> to me and possibly has to be maintained for future hibernate releases.
>
> By now, I took the DTO-way and it's working fine. The only thing I
> have to think over is how to replicate the data between entity-objects
> and DTO:
> putting the data from multiple entity-objects in one request-oriented
> DTO and vice versa (will minimze the transferred data, but harder to
> maintain)or
> building a DTO for each entity-class, moving the data between these
> classes via reflection (might produce a performance issue)
> one will see...
>
> Tschüß, Jens
>
> Stefan Liebig wrote on Wed, 30 September 2009 10:02
>> Hi Jens,
>>
>> De/serializing objects that require some sort of context (which is
>> not appropriately reconstructable) is difficult. One thing that you
>> could do is to create a customized AbstractRienaSerializerFactory
>> that could handle the de/serialization for those kind of objects.
>> Such factories can be contributed with the extension point "
>> org.eclipse.riena.communication.hessian.AbstractSerializerFa ctory ".
>> However, writing such factories requires some insight into the
>> hessian de/serialization mechanism.
>>
>> I would propose to introduce ´data transfer´ objects (pojos) within
>> your service signature and map them to the hibernate-proxy objects.
>>
>> Tschüß,
>> Stefan
>>
>> jens.mayer1@gmx.de wrote:
>> > Hi,
>> > > actually i'm writing a small example-app with riena remote
>> services and > hibernate as ORM-Framework on the serverside.
>> > > My first approach was to reuse the entity-classes on client-side
>> (making > hibernate-dependencies optional). Seems not to be a good
>> idea - the > hessian deserializer throws an
>> LayzyInitializationException when it > tries to deserialize
>> hibernate-proxy-classes, because there's no > PersistenceContext
>> available on the client-side. :?
>> > What might be the best practice for this case ?
>> > > Thanks in advance,
>> > > Jens
>
>
--
ekke (ekkehard gentz)
independent software-architect
senior erp-consultant
eclipse | osgi | equinox | mdsd | oaw | emf | uml
max-josefs-platz 30, D-83022 rosenheim, germany
mailto:ekke@ekkes-corner.org
homepage (de): http://gentz-software.de
blog (en): http://ekkes-corner.org
twitter: @ekkescorner
skype: ekkes-corner
Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490
--------------050003070701000207080702
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
jens,<br>
<br>
you should take a look at Gilead:<br>
<br>
Gilead stands for Generic Light Entity Adapter<br>
It permits you to send Persistent entities (and especially the
partially loaded ones) outside the JVM (GWT, Flex, Web-Services, Google
AppEngine ...) without pain.<br>
No LazyInitialisationException. No DTO mapping. Just POJO and Domain
Driven Design :)<br>
<br>
<a class="moz-txt-link-freetext" href="http://noon.gilead.free.fr/gilead/">http://noon.gilead.free.fr/gilead/</a><br>
<br>
ekke<br>
<a class="moz-txt-link-abbreviated" href="mailto:jens.mayer1@gmx.de">jens.mayer1@gmx.de</a> schrieb:
<blockquote cite="mid:ha48jv$4b2$1@build.eclipse.org" type="cite">Hi
Stefan,
<br>
<br>
thanks for your advice. I guess you're right: digging into the
serialization/deserialization-mechanism of hessian seems too complex to
me and possibly has to be maintained for future hibernate releases.
<br>
<br>
By now, I took the DTO-way and it's working fine. The only thing I have
to think over is how to replicate the data between entity-objects and
DTO:
<br>
putting the data from multiple entity-objects in one request-oriented
DTO and vice versa (will minimze the transferred data, but harder to
maintain)or
<br>
building a DTO for each entity-class, moving the data between these
classes via reflection (might produce a performance issue)
<br>
one will see...
<br>
<br>
Tschüß, Jens
<br>
<br>
Stefan Liebig wrote on Wed, 30 September 2009 10:02
<br>
<blockquote type="cite">Hi Jens,
<br>
<br>
De/serializing objects that require some sort of context (which is not
appropriately reconstructable) is difficult. One thing that you could
do is to create a customized AbstractRienaSerializerFactory that could
handle the de/serialization for those kind of objects. Such factories
can be contributed with the extension point "
org.eclipse.riena.communication.hessian.AbstractSerializerFa ctory ".
<br>
However, writing such factories requires some insight into the hessian
de/serialization mechanism.
<br>
<br>
I would propose to introduce ´data transfer´ objects (pojos) within
your service signature and map them to the hibernate-proxy objects.
<br>
<br>
Tschüß,
<br>
Stefan
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jens.mayer1@gmx.de">jens.mayer1@gmx.de</a> wrote:
<br>
> Hi,
<br>
> > actually i'm writing a small example-app with riena remote
services and > hibernate as ORM-Framework on the serverside.
<br>
> > My first approach was to reuse the entity-classes on
client-side (making > hibernate-dependencies optional). Seems not to
be a good idea - the > hessian deserializer throws an
LayzyInitializationException when it > tries to deserialize
hibernate-proxy-classes, because there's no > PersistenceContext
available on the client-side. :?
<br>
> What might be the best practice for this case ?
<br>
> > Thanks in advance,
<br>
> > Jens
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<p style="margin-bottom: 0cm;"> <font ,="" color="#808080"
face="Verdana, sans-serif"> <font size="4">ekke (ekkehard gentz)<br>
</font> <font size="3"> independent software-architect<br>
senior erp-consultant<br>
</font> <font size="2">eclipse | osgi | equinox | mdsd | oaw | emf |
uml<br>
max-josefs-platz 30, D-83022 rosenheim, germany<br>
<a class="moz-txt-link-freetext" href="mailto:ekke@ekkes-corner.org">mailto:ekke@ekkes-corner.org</a><br>
homepage (de): <a class="moz-txt-link-freetext" href="http://gentz-software.de">http://gentz-software.de</a><br>
blog (en): <a class="moz-txt-link-freetext" href="http://ekkes-corner.org">http://ekkes-corner.org</a><br>
twitter: @ekkescorner<br>
skype: ekkes-corner<br>
</font> <font size="1"> Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID:
DE189929490<br>
</font> </font> </p>
</div>
</body>
</html>
--------------050003070701000207080702--
ekke
independent software architect
blog: http://ekkes-corner.org
twitter: @ekkescorner
|
|
|
| Re: Riena with Hibernate on serverside [message #533066 is a reply to message #489268] |
Wed, 12 May 2010 07:37 |
Uwe Hehn
Messages: 7
Registered: May 2010 |
Junior Member |
|
|
Hi Ekke,
thanks for the valuable hint!
However, I would like to ask you about some clarifications on the issue.
Let's say I have an example of a Riena App where in the client I have the application and all the SubModlueViews and Controllers.
In the "Common" part I have the entities Person and Address, where Person has List<Address> adresses and the interaces IPersons and IPersonSearch.
In the "Server" part I have a PersonService, which implements IPersons and IPersonSearch.
So far so simple.
Now I want to add HibernateJPA to make Persons persistent.
What would be the best approach using Gilead?
Do I have to Persons extends LightEntity?
Should the entities (Person and Address) be @Entity in the same time and still reside in "Common"? That would mean, that they are send over to the client by the service. What is the purpose of Gilead then?
Sorry, I'm confused....
I would be gratefull if you could shed some light here or point me to right direction. Thanx.
Greets,
Uwe
| ekke (ekkehard gentz) wrote on Fri, 02 October 2009 03:52 | This is a multi-part message in MIME format.
--------------050003070701000207080702
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
jens,
you should take a look at Gilead:
Gilead stands for Generic Light Entity Adapter
It permits you to send Persistent entities (and especially the partially
loaded ones) outside the JVM (GWT, Flex, Web-Services, Google AppEngine
....) without pain.
No LazyInitialisationException. No DTO mapping. Just POJO and Domain
Driven Design 
http://noon.gilead.free.fr/gilead/
ekke
--------------050003070701000207080702--
|
|
|
| |
| Re: Riena with Hibernate on serverside [message #583860 is a reply to message #488857] |
Fri, 02 October 2009 07:03 |
Jens Mayer
Messages: 19
Registered: September 2009
Location: Hamburg |
Junior Member |
|
|
Hi Stefan,
thanks for your advice. I guess you're right: digging into the serialization/deserialization-mechanism of hessian seems too complex to me and possibly has to be maintained for future hibernate releases.
By now, I took the DTO-way and it's working fine. The only thing I have to think over is how to replicate the data between entity-objects and DTO:
putting the data from multiple entity-objects in one request-oriented DTO and vice versa (will minimze the transferred data, but harder to maintain)or
building a DTO for each entity-class, moving the data between these classes via reflection (might produce a performance issue)
one will see...
Tschüß,
Jens
Stefan Liebig wrote on Wed, 30 September 2009 10:02
> Hi Jens,
>
> De/serializing objects that require some sort of context (which is not
> appropriately reconstructable) is difficult. One thing that you could do
> is to create a customized AbstractRienaSerializerFactory that could
> handle the de/serialization for those kind of objects. Such factories
> can be contributed with the extension point
> " org.eclipse.riena.communication.hessian.AbstractSerializerFa ctory ".
> However, writing such factories requires some insight into the hessian
> de/serialization mechanism.
>
> I would propose to introduce ´data transfer´ objects (pojos) within your
> service signature and map them to the hibernate-proxy objects.
>
> Tschüß,
> Stefan
>
> jens.mayer1@gmx.de wrote:
> > Hi,
> >
> > actually i'm writing a small example-app with riena remote services and
> > hibernate as ORM-Framework on the serverside.
> >
> > My first approach was to reuse the entity-classes on client-side (making
> > hibernate-dependencies optional). Seems not to be a good idea - the
> > hessian deserializer throws an LayzyInitializationException when it
> > tries to deserialize hibernate-proxy-classes, because there's no
> > PersistenceContext available on the client-side. :?
> > What might be the best practice for this case ?
> >
> > Thanks in advance,
> >
> > Jens
|
|
|
| Re: Riena with Hibernate on serverside [message #583872 is a reply to message #583860] |
Fri, 02 October 2009 07:52 |
|
This is a multi-part message in MIME format.
--------------050003070701000207080702
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
jens,
you should take a look at Gilead:
Gilead stands for Generic Light Entity Adapter
It permits you to send Persistent entities (and especially the partially
loaded ones) outside the JVM (GWT, Flex, Web-Services, Google AppEngine
....) without pain.
No LazyInitialisationException. No DTO mapping. Just POJO and Domain
Driven Design :)
http://noon.gilead.free.fr/gilead/
ekke
jens.mayer1@gmx.de schrieb:
> Hi Stefan,
>
> thanks for your advice. I guess you're right: digging into the
> serialization/deserialization-mechanism of hessian seems too complex
> to me and possibly has to be maintained for future hibernate releases.
>
> By now, I took the DTO-way and it's working fine. The only thing I
> have to think over is how to replicate the data between entity-objects
> and DTO:
> putting the data from multiple entity-objects in one request-oriented
> DTO and vice versa (will minimze the transferred data, but harder to
> maintain)or
> building a DTO for each entity-class, moving the data between these
> classes via reflection (might produce a performance issue)
> one will see...
>
> Tschüß, Jens
>
> Stefan Liebig wrote on Wed, 30 September 2009 10:02
>> Hi Jens,
>>
>> De/serializing objects that require some sort of context (which is
>> not appropriately reconstructable) is difficult. One thing that you
>> could do is to create a customized AbstractRienaSerializerFactory
>> that could handle the de/serialization for those kind of objects.
>> Such factories can be contributed with the extension point "
>> org.eclipse.riena.communication.hessian.AbstractSerializerFa ctory ".
>> However, writing such factories requires some insight into the
>> hessian de/serialization mechanism.
>>
>> I would propose to introduce ´data transfer´ objects (pojos) within
>> your service signature and map them to the hibernate-proxy objects.
>>
>> Tschüß,
>> Stefan
>>
>> jens.mayer1@gmx.de wrote:
>> > Hi,
>> > > actually i'm writing a small example-app with riena remote
>> services and > hibernate as ORM-Framework on the serverside.
>> > > My first approach was to reuse the entity-classes on client-side
>> (making > hibernate-dependencies optional). Seems not to be a good
>> idea - the > hessian deserializer throws an
>> LayzyInitializationException when it > tries to deserialize
>> hibernate-proxy-classes, because there's no > PersistenceContext
>> available on the client-side. :?
>> > What might be the best practice for this case ?
>> > > Thanks in advance,
>> > > Jens
>
>
--
ekke (ekkehard gentz)
independent software-architect
senior erp-consultant
eclipse | osgi | equinox | mdsd | oaw | emf | uml
max-josefs-platz 30, D-83022 rosenheim, germany
mailto:ekke@ekkes-corner.org
homepage (de): http://gentz-software.de
blog (en): http://ekkes-corner.org
twitter: @ekkescorner
skype: ekkes-corner
Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490
--------------050003070701000207080702
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
jens,<br>
<br>
you should take a look at Gilead:<br>
<br>
Gilead stands for Generic Light Entity Adapter<br>
It permits you to send Persistent entities (and especially the
partially loaded ones) outside the JVM (GWT, Flex, Web-Services, Google
AppEngine ...) without pain.<br>
No LazyInitialisationException. No DTO mapping. Just POJO and Domain
Driven Design :)<br>
<br>
<a class="moz-txt-link-freetext" href="http://noon.gilead.free.fr/gilead/">http://noon.gilead.free.fr/gilead/</a><br>
<br>
ekke<br>
<a class="moz-txt-link-abbreviated" href="mailto:jens.mayer1@gmx.de">jens.mayer1@gmx.de</a> schrieb:
<blockquote cite="mid:ha48jv$4b2$1@build.eclipse.org" type="cite">Hi
Stefan,
<br>
<br>
thanks for your advice. I guess you're right: digging into the
serialization/deserialization-mechanism of hessian seems too complex to
me and possibly has to be maintained for future hibernate releases.
<br>
<br>
By now, I took the DTO-way and it's working fine. The only thing I have
to think over is how to replicate the data between entity-objects and
DTO:
<br>
putting the data from multiple entity-objects in one request-oriented
DTO and vice versa (will minimze the transferred data, but harder to
maintain)or
<br>
building a DTO for each entity-class, moving the data between these
classes via reflection (might produce a performance issue)
<br>
one will see...
<br>
<br>
Tschüß, Jens
<br>
<br>
Stefan Liebig wrote on Wed, 30 September 2009 10:02
<br>
<blockquote type="cite">Hi Jens,
<br>
<br>
De/serializing objects that require some sort of context (which is not
appropriately reconstructable) is difficult. One thing that you could
do is to create a customized AbstractRienaSerializerFactory that could
handle the de/serialization for those kind of objects. Such factories
can be contributed with the extension point "
org.eclipse.riena.communication.hessian.AbstractSerializerFa ctory ".
<br>
However, writing such factories requires some insight into the hessian
de/serialization mechanism.
<br>
<br>
I would propose to introduce ´data transfer´ objects (pojos) within
your service signature and map them to the hibernate-proxy objects.
<br>
<br>
Tschüß,
<br>
Stefan
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jens.mayer1@gmx.de">jens.mayer1@gmx.de</a> wrote:
<br>
> Hi,
<br>
> > actually i'm writing a small example-app with riena remote
services and > hibernate as ORM-Framework on the serverside.
<br>
> > My first approach was to reuse the entity-classes on
client-side (making > hibernate-dependencies optional). Seems not to
be a good idea - the > hessian deserializer throws an
LayzyInitializationException when it > tries to deserialize
hibernate-proxy-classes, because there's no > PersistenceContext
available on the client-side. :?
<br>
> What might be the best practice for this case ?
<br>
> > Thanks in advance,
<br>
> > Jens
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<p style="margin-bottom: 0cm;"> <font ,="" color="#808080"
face="Verdana, sans-serif"> <font size="4">ekke (ekkehard gentz)<br>
</font> <font size="3"> independent software-architect<br>
senior erp-consultant<br>
</font> <font size="2">eclipse | osgi | equinox | mdsd | oaw | emf |
uml<br>
max-josefs-platz 30, D-83022 rosenheim, germany<br>
<a class="moz-txt-link-freetext" href="mailto:ekke@ekkes-corner.org">mailto:ekke@ekkes-corner.org</a><br>
homepage (de): <a class="moz-txt-link-freetext" href="http://gentz-software.de">http://gentz-software.de</a><br>
blog (en): <a class="moz-txt-link-freetext" href="http://ekkes-corner.org">http://ekkes-corner.org</a><br>
twitter: @ekkescorner<br>
skype: ekkes-corner<br>
</font> <font size="1"> Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID:
DE189929490<br>
</font> </font> </p>
</div>
</body>
</html>
--------------050003070701000207080702--
ekke
independent software architect
blog: http://ekkes-corner.org
twitter: @ekkescorner
|
|
|
| Re: Riena with Hibernate on serverside [message #585479 is a reply to message #489268] |
Wed, 12 May 2010 07:37 |
Uwe Hehn
Messages: 7
Registered: May 2010 |
Junior Member |
|
|
Hi Ekke,
thanks for the valuable hint!
However, I would like to ask you about some clarifications on the issue.
Let's say I have an example of a Riena App where in the client I have the application and all the SubModlueViews and Controllers.
In the "Common" part I have the entities Person and Address, where Person has List<Address> adresses and the interaces IPersons and IPersonSearch.
In the "Server" part I have a PersonService, which implements IPersons and IPersonSearch.
So far so simple.
Now I want to add HibernateJPA to make Persons persistent.
What would be the best approach using Gilead?
Do I have to Persons extends LightEntity?
Should the entities (Person and Address) be @Entity in the same time and still reside in "Common"? That would mean, that they are send over to the client by the service. What is the purpose of Gilead then?
Sorry, I'm confused....
I would be gratefull if you could shed some light here or point me to right direction. Thanx.
Greets,
Uwe
ekke (ekkehard gentz) wrote on Fri, 02 October 2009 03:52
> This is a multi-part message in MIME format.
> --------------050003070701000207080702
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Content-Transfer-Encoding: 8bit
>
> jens,
>
> you should take a look at Gilead:
>
> Gilead stands for Generic Light Entity Adapter
> It permits you to send Persistent entities (and especially the partially
> loaded ones) outside the JVM (GWT, Flex, Web-Services, Google AppEngine
> ....) without pain.
> No LazyInitialisationException. No DTO mapping. Just POJO and Domain
> Driven Design :)
>
> http://noon.gilead.free.fr/gilead/
>
> ekke
> --------------050003070701000207080702--
|
|
|
Goto Forum:
Current Time: Tue Apr 23 16:13:45 GMT 2024
Powered by FUDForum. Page generated in 0.05153 seconds |
] 
Search
Help
Register
Login
Home
