How can i enable the "autodeployer" in a production
system?
--- marc fleury <[EMAIL PROTECTED]> wrote:
> For production systems (as opposed to development
> system) we dissable the
> "autodeployer" and instead configure a JMX enabled
> deployer that can take
> URLs to deploy tomcat and jboss. (BTW we are almost
> done with the inVM
> tomcat version).
>
> The prod system will only use deploy on command and
> it takes care of
> removing all the files and such.
>
> Stay tuned and we hope that fills your need
>
> marc
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf
> Of Wes Mckean
> > Sent: Tuesday, October 03, 2000 3:16 PM
> > To: 'jBoss'
> > Subject: RE: [jBoss-User] Intense Jboss use
> >
> >
> > Fransisco is reporting things that I have observed
> on and commented in the
> > past. When I update my jar files and copy them
> into the deploy
> > directory of
> > jBoss, my changes don't get put in until I stop
> and restart the jBoss
> > server.
> >
> > Over the past week, I set up some build.xml files
> for ant, and in order to
> > have the builds go through 100%, I had to extract
> all the ejb-jar.xml and
> > jboss.xml files from my bean jar files and save
> them, so I could have ant
> > build the entire bean. After building a bean and
> restarting jBoss, I was
> > suprised to see jboss deploying all my jar files
> with the same bean
> > information! It was reading the XML files from my
> "build" directory's
> > META-INF sub-directory, because it was on my class
> path. I
> > simply modified
> > ant to delete the XML files when it is done, and
> everything is fine now.
> >
> > The hot deploy issue is definitely serious, but
> the XML file problem is a
> > gnat.
> >
> > Wes
> >
> > -----Original Message-----
> > From: Francisco Andrades
> [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, October 03, 2000 6:07 PM
> > To: jBoss
> > Subject: Re: [jBoss-User] Intense Jboss use
> >
> >
> > Tomcat may crate jars in the \temp dir, but i�m
> not
> > using it right now, and every time i deploy a
> bean, a
> > jar file appears there, even if i�m updating.
> >
> > --- Charles Crain <[EMAIL PROTECTED]> wrote:
> > > Correct me if I'm wrong anyone...but the .jar
> files
> > > in the temp
> > > directory are actually generated by Tomcat when
> a
> > > JSP is compiled, not
> > > by jBoss proper, am I correct?
> > >
> > > -Charles
> > >
> > > Francisco Andrades wrote:
> > >
> > > > Hi, i have used jboss quite intensively and
> have
> > > > managed to create incredible things, but i
> have
> > > also
> > > > found some details that i think must be
> corrected
> > > in
> > > > order to jump to the next level of
> development.
> > > >
> > > > I�m using jboss as the j2ee container for the
> > > beans
> > > > we�re developing. One of the main goals of the
> > > > application we�re working on is to create all
> the
> > > > beans the user wants, and store them in the
> j2ee
> > > > container. The end users access the beans
> using a
> > > > jakarta-tomcat managed servlet.
> > > >
> > > > The system runs pretty good when working in a
> > > > non-intensive mood, but when it comes to
> > > > deploy/undeploy/redeploy/run/deploy again the
> > > beans,
> > > > the system starts to behave in an unusual way.
> The
> > > > main problem we�re facing is that the beans
> are
> > > not
> > > > fully undeployed or redeployed, because after
> > > having
> > > > updated a bean several times (i mean
> > > > undeploy/deploy/undeploy/deploy) and having
> > > accessed
> > > > it, it comes to a point when no updates are
> seen
> > > by
> > > > the container (even if it tells through the
> > > console
> > > > that an update has been made). The problem
> seems
> > > > worse, because restarting jboss (and even
> > > unistalling
> > > > and reinstalling it) doesn�t help. If you want
> to
> > > work
> > > > again you have to stop jboss, delete all the
> .jar
> > > that
> > > > lay in c:\temp (assuming NT) and restart
> jboss.
> > > >
> > > > Another issue (because i don�t know if it�s a
> > > feature)
> > > > is that when deploying the beans there can�t
> be
> > > any
> > > > jboss.xml and ejb-jar.xml files in a directory
> > > named
> > > > META-INF in the classpath, because jboss will
> use
> > > them
> > > > more likely than the ones inside the bean�s
> jar
> > > (which
> > > > in most cases messes up all the beans and
> forces
> > > you
> > > > to start over).
> > > >
> > > > There�s also the problem with the
> conf\jboss.jcml
> > > > file. I have solved it modifying the run.bat
> > > script to
> > > > regenerate it every time jboss starts.
> > > >
> > > > At last, but not least, i�d like to apologize
> if
> > > these
> > > > issues are not actually a problem, or have
> already
> > > > been reported.
> > > >
> > > > Thanks
> > > > Francisco
> > > >
> > > > P.D.: JBoss rules !!!!!!!!!!!!!!!!
> > > >
> > > > =====
> > > > One ring to rule them all, one ring to find
> them
> > > > one ring to bring them all and in the darkness
> > > bind them
> > > >
> > > > ... in the land of Mordor where the
> > > shadows lie
> > > >
> > > >
> __________________________________________________
> > > > Do You Yahoo!?
> > > > Yahoo! Photos - 35mm Quality Prints, Now Get
> 15
> > > Free!
> > > > http://photos.yahoo.com/
> > > >
> > > > --
> > > >
> > >
> >
>
--------------------------------------------------------------
> > > > To subscribe:
> > > [EMAIL PROTECTED]
> > > > To unsubscribe:
>
=== message truncated ===
=====
One ring to rule them all, one ring to find them
one ring to bring them all and in the darkness bind them
... in the land of Mordor where the shadows lie
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
