Rick,
Thanks for that response.
Rick.Wellman wrote:
>
> I am not even sure this is worth two-cents but:
> What (for lack of a better word) confuses me is the phrase "generate a
> jar file that will pull out some of the data..."
>
What I'm trying to say is that in the ideal world, application 1 would have
a dependency on a specific jar (let's call it db-access-scope1) and
application 2 would have a similar dependency on a different jar (let's call
that one db-access-scope2). The two jars (db-access-scope{1,2}) would be
generated from a single common code base but with subtley different
configurations.
Rick.Wellman wrote:
>
> From what I can decipher, I would handle it like this. As you say, your
> data model itself is identical but the second application needs extra
> constraints. I would simply use iBatis' dynamic SQL features to write
> the additional constraints into your sqlmaps. Only your second
> application would "trigger" the additional constraints. I would imagine
> that you would somehow encapsulate this into some class (or classes)
> that the second application uses and the first does not. While I could
> have missed something, it just seems like you might be looking for a
> solution that is more complicated than it needs to be.
>
I think that we may end up with a variation of this post-compilation
configuration. The niggle that I have is the potential to misconfigure, but
I think that with sufficient counselling I may be able to get over that :o}
Thanks again.
Later,
Andy
--
View this message in context:
http://old.nabble.com/How-would-you---the-experts---design-this--tp27304322p27319887.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org
For additional commands, e-mail: user-java-h...@ibatis.apache.org
