Marc,
Sorry, I'm a little trigger-happy and I deleted your mesage before
I realized I should reply. The update to the web site didn't update the
jboss.dtd file.
I just checked out "newsite" again, and the correct DTD is under
newsite/documentation/jboss.dtd. The way I can tell is that at the very
end, It has a container-pool-conf entry with *both* MinimumSize and
MaximumSize children (the entire end of the file is quoted below). You
just said you synced the site, but when I go to
http://www.jboss.org/documentation/jboss.dtd I get the old version with
only a MaximumSize child. I tried reloading. What's up?
Aaron
<!ELEMENT container-pool-conf (MaximumSize, MinimumSize)>
<!--
This element is only valid if the instance pool is a subclass of
AbstractInstancePool.
The MaximumSize element gives the maximum number of instance to
keep in the pool. Its value must be an integer.
Used in: container-pool-conf for AbstractInstancePool subclasses
-->
<!ELEMENT MaximumSize (#PCDATA)>
<!--
This element is only valid if the instance pool is a subclass of
AbstractInstancePool.
The MinimumSize element gives the minimum number of instance to
keep in the pool. Its value must be an integer.
Used in: container-pool-conf for AbstractInstancePool subclasses
-->
<!ELEMENT MinimumSize (#PCDATA)>
<!--
This option is only used for entity container configurations.
The commit-option element tells the container which option to use
for transactions.
Its value must be A, B or C.
- option A: the entiry instance has exclusive access to the
database. The instance
stays ready after a transaction.
- option B: the entity instance does not have exclusive access to
the database.
The state is loaded before the next transaction.
- option C: same as B, except the container does not keep the
instance after commit:
a passivate is immediately performed after the commit.
See ejb1.1 specification for details (p118).
Used in: container-configuration
-->
<!ELEMENT commit-option (#PCDATA)>
