Em Sex, 2002-03-15 �s 12:25, [EMAIL PROTECTED] escreveu:
> Hi,
>
> after turning on logging for the merge handlers I noticed XDoclet searching
> for JBoss merge files of the patterns jbosscmp-jdbc-db-settings-{0}.xml,
> jbosscmp-jdbc-{0}.xml and jbosscmp-jdbc-load-{0}.xml.
> As especially the first and second one are not explained in the docs I was
> wondering about their purpose. What can go into those?
I hope you know {0} means the class name of the bean. So, if you're
using the tags on a class named com.mycompany.ejb.MyBean, the file
should be named jbosscmp-jdbc-load-MyBean.xml and should be put in a
com/mycompany/ejb directory under your mergedir.
As what jboss-cmp-jdbc-{0}.xml and jbosscmp-jdbc-db-settings-{0}.xml
does, I recommend you to take a look at the template file for more info.
Anyway, here's a quickie:
jbosscmp-jdbc-db-settings-{0}.xml: should be used to configure database
parameters for the bean. Most of what can go into it can also be
configured using @jboss tags. You should write it if you want to
configure read-ahead and list-cache-max.
Note that if you choose to write this merge file, you should write at
least the ejb-name as it is mandatory according to the DTD. Also, if you
choose to write it, @jboss:table-name, @jboss:create-table etc. tags are
ignored. You're on your own.
Here is the DTD fragment:
<!ELEMENT ejb-name (#PCDATA)>
<!ELEMENT create-table (#PCDATA)> <!-- true/false -->
<!ELEMENT remove-table (#PCDATA)> <!-- true/false -->
<!ELEMENT read-only (#PCDATA)> <!-- true/false -->
<!ELEMENT time-out (#PCDATA)> <!-- miliseconds -->
<!ELEMENT row-locking (#PCADATA)> <!-- true/false -->
<!ELEMENT pk-constraint (#PCDATA)> <!-- true/false -->
<!ELEMENT table-name (#PCDATA)>
<!-- These are currently not configurable using xDoclet tags -->
<!ELEMENT read-ahead (strategy, page-size?, eager-load-group?)>
<!ELEMENT strategy (#PCDATA)> <!-- none/on-load/on-find -->
<!ELEMENT page-size (#PCDATA)>
<!ELEMENT eager-load-group (#PCDATA)>
<!ELEMENT list-cache-max (#PCDATA)>
jbosscmp-jdbc-{0}.xml: should be used if you want to define all
persistent fields for your bean. You should only write this merge file
if you don't trust xDoclet @ejb:persistent-field and friends, if you're
somewhat crazy of if you have a pretty damn complex bean.
Here is the DTD fragment:
<!ELEMENT cmp-field (field-name, read-only?, time-out?,
column-name?, not-null?, ((jdbc-type, sql-type) | (property+))? )>
<!ELEMENT field-name (#PCDATA)>
<!ELEMENT read-only (#PCDATA)> <!-- true/false -->
<!ELEMENT time-out (#PCDATA)> <!-- miliseconds -->
<!ELEMENT column-name (#PCDATA)>
<!ELEMENT not-null EMPTY>
<!ELEMENT jdbc-type (#PCDATA)>
<!ELEMENT sql-type (#PCDATA)>
<!ELEMENT property (property-name, column-name?, not-null?,
(jdbc-type, sql-type)?)>
<!ELEMENT property-name (#PCDATA)>
If you're unsure about any of the above tags, please look at the DTD.
> Second question is, where should jboss-resource-managers.xml,
> jboss-security.xml and jboss-container.xml be placed, so the jboss subtask
> can find them. The root of my mergedir or where?
Yes, the root of mergedir.
--
Ja ne,
Pazu
mailto: [EMAIL PROTECTED]
Anime Gaiden: de f�s para f�s, sempre.
signature.asc
Description: This is a digitally signed message part
