Hey marc!
If you like, I will make up an little script that will export the
website each time someone checks in something to "newsite" cvs. How many
access right do you have on the cvs server ?
We already have something similar here to generate up-to-date javadocs
each time a new class gets checked in. The javadocs then get exposed to
the internal intranet. Nice thingy ...
C ya,
Tobias
marc fleury wrote:
>
> Nope, no cvs... I will try to contact them for an install of that, nice try
> though, I am still stuck with FTP to update the website. <sigh>
>
> marc
>
> |-----Original Message-----
> |From: marc fleury [mailto:[EMAIL PROTECTED]]
> |Sent: Friday, December 01, 2000 2:05 PM
> |To: jBoss Developer
> |Subject: RE: [jBoss-Dev] Web Site Updates
> |
> |
> |hm let me check if the target machine has cvs... never though of
> |that (silly me)... be right back
> |
> |marc
> |
> ||-----Original Message-----
> ||From: [EMAIL PROTECTED]
> ||[mailto:[EMAIL PROTECTED]]On Behalf Of Tobias Frech
> ||Sent: Friday, December 01, 2000 11:00 AM
> ||To: jBoss Developer
> ||Subject: Re: [jBoss-Dev] Web Site Updates
> ||
> ||
> ||Hi Marc!
> ||Isn't there the possibility to do something like:
> ||
> ||rm -rf webdir
> ||cvs checkout newsite
> ||mv newsite webdir
> ||
> ||That should take care of everything. Or do I miss something ?
> ||
> ||Ciao,
> ||Tobias
> ||
> ||Aaron Mulder wrote:
> ||>
> ||> 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)>
> ||
> ||
