I assume the "Run Middlegen" ist the interesting part in build.xml. I've understood that that's where changes are made...hmm.
<!-- =================================================================== -->
<!-- Run Middlegen -->
<!-- =================================================================== -->
<target
name="middlegen"
description="Run Middlegen"
unless="middlegen.skip"
depends="init,fail-if-no-xdoclet-1.2,check-driver-present,panic-if-driver-not-present"
>
<mkdir dir="${build.gen-src.dir}"/>
<taskdef
name="middlegen"
classname="middlegen.MiddlegenTask"
classpathref="lib.class.path"
/>
<!--
<middlegen
appname="${name}"
prefsdir="${src.dir}"
gui="${gui}"
databaseurl="${database.url}"
initialContextFactory="${java.naming.factory.initial}"
providerURL="${java.naming.provider.url}"
datasourceJNDIName="${datasource.jndi.name}"
driver="${database.driver}"
username="${database.userid}"
password="${database.password}"
schema="${database.schema}"
catalog="${database.catalog}"
>
-->
<middlegen
appname="${name}"
prefsdir="${src.dir}"
gui="${gui}"
databaseurl="something"
initialContextFactory="${java.naming.factory.initial}"
providerURL="${java.naming.provider.url}"
datasourceJNDIName="${datasource.jndi.name}"
driver="oracle.jdbc.driver.OracleDriver"
username="whatever"
password="whatever"
schema="database.schema"
catalog="${database.catalog}"
>
<!--
We can specify what tables we want EJBs generated for.
If none are specified, EJBs will be generated for all tables.
Comment out the <table> elements if you want to generate for all tables.
Also note that table names are CASE SENSITIVE for certain databases,
so on e.g. Oracle you should specify table names in upper case.
The sequencename attribute is optional and will be used from
the oraclesequence extension. If no sequencename is present
it will be the name attribute suffixed by _SEQ.
-->
<!--table generate="true" name="persons" pktable="persons_pk"
sequencename="my_persons_sequence" />
<table generate="true" name="flights" pktable="flights_pk"/>
<table name="reservations"/-->
<!--
If you want m:n relations, they must be specified like this.
Note that tables declare in multiple locations must all have
the same value of the generate attribute.
-->
<!--many2many>
<tablea generate="true" name="persons"/>
<jointable name="reservations" generate="false"/>
<tableb generate="true" name="flights"/>
</many2many-->
<!--table name="PERSON" pktable="id" singular="person" plural="persons" />
<table name="ADDRESS" pktable="id" singular="address" plural="addresses" />
<many2many>
<tablea generate="true" name="PERSON" />
<jointable name="EMPLOYMENT" generate="false" />
<tableb generate="true" name="PERSON" />
</many2many-->
<cmp20
destination="${build.gen-src.dir}"
package="${name}.ejb"
interfacepackage="${name}.interfaces"
jndiprefix="${unique.name}"
pkclass="false"
dataobject="false"
valueobject="true"
sessionfacade="true"
viewtype="local"
mergedir="${basedir}/src/middlegen"
readonly="false"
fkcmp="true"
guid="true"
>
<!-- Let the EJBs use The portable Sequence Block PK generation pattern -->
<sequenceblock
blocksize="5"
retrycount="2"
table="SEQ_BLOCK"
/>
<!--
Alternatively to the sequenceblock you may use
Oracle-Sequences if you have an Oracle RDBMS.
You must use the table element in the middlegen-task if
you want to provide the sequencename (see above). If you
do not enter a sequencename the sequencename will be
assumed to be like 'TABLE_NAME'_SEQ. (e.g. Table FOO will
use the Sequence FOO_SEQ)
Be sure that the datasource entry matches the entry from
the ejbdoclet applicationserver element (e.g. <jboss/>)
Additional attributes are interfacepackage and package. If
these values are not provided they will be superseded by
the plugin's attributes.
-->
<!--oraclesequence
datasource="java:/OracleDS"
/-->
<!-- We can use predicates to specify what columns we want finders for -->
<!--finders>
<and>
<indexed/>
<notkey/>
</and>
</finders-->
<!--
EJB containers can be specified here. They add aditional
features and perform additional validations. You don't have to
add them, they just provide "goodies".
-->
<!--weblogic pkgen="VENDOR_SEQ" generatorName="my_sequence" keyCacheSize="20"/-->
<weblogic/>
<jboss/>
<!-- options for mvcsoft listed in cmp20 docs -->
<!--<mvcsoft/>-->
</cmp20>
<!-- generate som read-only beans too -->
<!--cmp20
name="cmp20_ro"
destination="${build.gen-src.dir}"
package="${name}.ejb"
interfacepackage="${name}.interfaces"
jndiprefix="${unique.name}"
generatepk="false"
dataobject="false"
viewtype="local"
mergedir="${basedir}/src/middlegen"
readonly="true"
fkcmp="true"
suffix="RO"
>
<jboss/>
<mvcsoft/>
</cmp20-->
<sunjdo10
destination="${build.gen-src.dir}"
package="${name}.jdo"
/>
<html destination="${build.html.dir}">
<!--
We can override the plugin's templates
by specifying the id of the original template
and providing a new one from the file system.
Uncomment the line below to see it in action.
(This technique can be used for all plugins).
-->
<!--fileproducer
id="single-table"
template="${basedir}/src/templates/single-table.vm"
/-->
</html>
<!--
This illustrates the use of custom templates without the need to write
a custom plugin. Just use the <plugin> task directly and specify as many
<fileproducers> as you like. If the filename attribute contains a {0},
one file will be generated per table, and the {0} will be substituted by
the table name in the generated files. If there is no {0}, only one file
will be generated. You can also narrow down the number of tables by
explicitly specifying nested <table> elements. If you don't specify
nested <table> elements, all tables will be used.
-->
<simple
destination="${basedir}"
>
<fileproducer
destination="${basedir}/build"
filename="toto-{0}.txt"
template="${basedir}/src/templates/simple.vm"
>
<table name="RESERVATIONS"/>
<table name="PERSONS"/>
</fileproducer>
</simple>
<!-- Plugins "under construction" -->
<!--xmi
destination="${build.xmi.dir}"
/-->
<struts
destination="${build.gen-src.dir}"
package="${name}.web.struts"
>
<jsp
name="myjsp"
destination="${build.gen-webui.dir}"
/>
</struts>
<hibernate
destination="${build.gen-src.dir}"
package="${name}.hibernate" javaTypeMapper="middlegen.plugins.hibernate.HibernateJavaTypeMapper"
/>
</middlegen>
<mkdir dir="${build.classes.dir}"/>
</target>
Login
FAQ
Search
