das/hibernate service design question

[Abraham Washington <ab...@yahoo.com>]

hi all..
  if this is not an appropriate question for this forum, my apologies (just disregard).   i tried using das for my persistence layer.  i need a mechanism to persist information to multiple schemas and i'm already using sca, so das seems like a logic choice.  unfortunately i couldn't get it to work (i created a jira issue, but it could be user error).  
 so, i decided to try hibernate to persist.  since this is a service, i create a new session for each request, passing in the schema information to the service operation.  opening and closing the connection/session for each request.  works fine (from my local testing).  i don't think a connection pool would be beneficial, since the service is not maining a connection (just persist and done, ie..a service operation).
  i'm wondering if there are other options that would be better with sca, since that's our preferred architecture?
thx abe


      

Re: das/hibernate service design question

[Jean Madson <je...@gmail.com>]

Hello, Abraham,

I think if you want to follow the SCA approach, it's strong recomended that
you make use of DAS with SDO.  Running out of DAS/SDO, besides Hibernate
that you has mentioned, there are a lot of persistence frameworks that could
be used
to the job.  But I think that all of these frameworks are out of the
SCA/SDO/DAS scope.

-- 
Jean Madson
http://bit-zen.blogspot.com/
http://www.plurk.com/user/jeanmadson
MSN/GTalk: jeanmadson@gmail.com
-----
HI LI KO KEN TEN
Be grass, don't eat grass
"É preciso esvaziar a xícara para ver o fundo tal como ele é, caso
contrário,
o fundo parecerá turvo, e idéias precipitadas acerca do que seja o
fundo límpido emergirão."




2008/8/8 Abraham Washington <ab...@yahoo.com>

> hi all..
>
>   if this is not an appropriate question for this forum, my apologies (just
> disregard).   i tried using das for my persistence layer.  i need a
> mechanism to persist information to multiple schemas and i'm already using
> sca, so das seems like a logic choice.  unfortunately i couldn't get it to
> work (i created a jira issue, but it could be user error).
>  so, i decided to try hibernate to persist.  since this is a service, i
> create a new session for each request, passing in the schema information to
> the service operation.  opening and closing the connection/session for each
> request.  works fine (from my local testing).  i don't think a connection
> pool would be beneficial, since the service is not maining a connection
> (just persist and done, ie..a service operation).
>   i'm wondering if there are other options that would be better with sca,
> since that's our preferred architecture?
>
> thx abe
>
>
>