[ https://issues.apache.org/jira/browse/IBATIS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Butler closed IBATIS-507. ------------------------------ Resolution: Won't Fix This seems like an unusual request to me, so I don't think we should include it in the base ibator code. However, I have made some recent improvements to the extensibility of ibator that will enable you to easily implement this for your needs: <ibatorContext introspectedTableImplementation="com.foo.Bar" > ... </ibatorContext> Then Java code like this: package com.foo; import org.apache.ibatis.ibator.internal.db.IntrospectedTableDefaultImpl; public class Bar extends IntrospectedTableDefaultImpl { @Override public String getJavaModelPackage() { ... } @Override public String getDAOPackage() { ... } @Override public String getSqlMapPackage() { ... } } > Ibator support for table defined subpackage > ------------------------------------------- > > Key: IBATIS-507 > URL: https://issues.apache.org/jira/browse/IBATIS-507 > Project: iBatis for Java > Issue Type: New Feature > Components: Tools > Affects Versions: 2.3.3 > Environment: N/A > Reporter: Dan Turkenkopf > Priority: Minor > Attachments: ibator_subpackage.patch > > > It would be helpful to be able to specify a subpackage for any given table > when using Ibator to generate the code. > For example, I might want to put table X in com.test.foo and table Y in > com.test.bar. > I've added the property "subPackage" to the table definition which overrides > the schema based subpackage fragment if set. > Using the above example, I'd add <property name="subPackage" value="foo"/> to > the defintion for table X. > Patch is attached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.