|
»
« Return to Thread: Accessing pre-existing data
Re: Accessing pre-existing data
by Alejandro Scandroli
::
Rate this Message:
Hi Daniel
Pre-existing data is not an issue.
On the other hand working with two data sources can be tricky.
If you can trick hibernate to manage two or more different db
connections at hibernate level Trails won't notice it, and it will
work without problems.
If that's not possible and you only need the second connection to
validate your users, you can create your own UserDetailsService to
serve your user credentials.
If that's not enough you can use two persistence services but that
means that you will have to duplicate quite a lot of configuration,
and I haven't tried it with Trails 1.2
Please if you are just starting with java web frameworks, take a look
at: http://www.trailsframework.org/Read+me+first
Regards.
Alejandro.
--
Alejandro Scandroli - http://weblog.amneris.es/
Amneris: We build process-driven web applications.
http://www.amneris.es
On Thu, Apr 17, 2008 at 11:31 AM, Daniel Lauk <daniel.lauk@...> wrote:
> Hi list.
>
> The next problem I have to face in evaluating the frameworks, is: "How
> do I access pre-existing data?"
> In my special case, we have a centralized data store for "personnel
> master data", that I need to access. This resides on a database server
> that won't necessarily be the one that the app is running on.
>
> I am sure, I can figure out how to fine tune hibernate to manage two
> connections, but how much does this impact the remaining Trails stack?
>
> Another application area would be, to use Trails to re-write existing
> web-applications (e.g. because the code is *so* old or messed up).
> The only approach that comes to my mind (I am not into java frameworks
> yet -- just starting) is, create the new business logic from scratch
> with trails and then (backup and) migrate the existing data (similar
> to the model evolution problem discussed before).
>
> Kind regards,
> Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Pre-existing data is not an issue.
On the other hand working with two data sources can be tricky.
If you can trick hibernate to manage two or more different db
connections at hibernate level Trails won't notice it, and it will
work without problems.
If that's not possible and you only need the second connection to
validate your users, you can create your own UserDetailsService to
serve your user credentials.
If that's not enough you can use two persistence services but that
means that you will have to duplicate quite a lot of configuration,
and I haven't tried it with Trails 1.2
Please if you are just starting with java web frameworks, take a look
at: http://www.trailsframework.org/Read+me+first
Regards.
Alejandro.
--
Alejandro Scandroli - http://weblog.amneris.es/
Amneris: We build process-driven web applications.
http://www.amneris.es
On Thu, Apr 17, 2008 at 11:31 AM, Daniel Lauk <daniel.lauk@...> wrote:
> Hi list.
>
> The next problem I have to face in evaluating the frameworks, is: "How
> do I access pre-existing data?"
> In my special case, we have a centralized data store for "personnel
> master data", that I need to access. This resides on a database server
> that won't necessarily be the one that the app is running on.
>
> I am sure, I can figure out how to fine tune hibernate to manage two
> connections, but how much does this impact the remaining Trails stack?
>
> Another application area would be, to use Trails to re-write existing
> web-applications (e.g. because the code is *so* old or messed up).
> The only approach that comes to my mind (I am not into java frameworks
> yet -- just starting) is, create the new business logic from scratch
> with trails and then (backup and) migrate the existing data (similar
> to the model evolution problem discussed before).
>
> Kind regards,
> Daniel
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: Accessing pre-existing data
| Free embeddable forum powered by Nabble | Forum Help |
