You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reporter: Martin Ellis
Originally reported here:
http://www.mail-archive.com/user-java@ibatis.apache.org/msg14963.html
The iBATIS configuration file allows a number of different
environments (including database names and credentials) to be
specified. These are identified by environment name. The
configuration file is parsed by the XMLConfigBuilder class.
The XMLConfigBuilder constructor (the class that parses the config
file) creates a new Configuration instance per XMLConfigBuilder
instance, and it's only possible to specify a single Reader for a
given XMLConfigBuilder.
It'd be good to be able to separate out environment specific config
data from other ibatis config.
This means that it's not possible to keep the type aliases in an XML file
in a library, and the environments in a separate XML file in applications
using that library, and have the two combined at runtime.
Original issue reported on code.google.com by clinton....@gmail.com on 17 May 2010 at 1:41
The text was updated successfully, but these errors were encountered:
I think this issue and issue #3 could both be solved by a general include
mechanism in the config builders.
Would it be enough to have a separate config file for each environment that
includes a common set of type aliases (or other elements)?
Original comment by hpresnall@gmail.com on 15 Oct 2010 at 3:48
Please, implement this feature. I don't understand why it was not made in the
very first version of mybatis since all aliases and type handlers moved from
mapper to configuration (since ibatis 2.x) and could not be shared by related
project unless configurations can be combined.
Original comment by chpa...@gmail.com on 3 Jan 2011 at 3:01
Original issue reported on code.google.com by
clinton....@gmail.com
on 17 May 2010 at 1:41The text was updated successfully, but these errors were encountered: