Jay,
I don't know about your development environment, but I require all
developers to install the free version of JRUN on their local development
machines. Everyone is also required to update their local source code from
source safe upon notice, so that every developer has the same product
framework to work with. This way, each individual can work on his segment
of the product using his local copy of JRUN and IIS as the server on his
local machine. Upon completion of development and local testing by the
individual developer, his source code is uploaded to both source safe and to
a development server upon approval of his lead. This is usually done on a
weekly basis. This way, our testing department can test the entire product
on a development server that every developer is mapped to. We can also use
the development server to discuss and view code during meetings.
I do not advocate using a development server for a large group of developers
to actually develop on together. It's too easy for one person to make a
change that subsequently "breaks" the product for everyone else, and brings
the development process to a halt. By having a "development" environment
installed on each persons computer, every programmer can proceed at his/her
pace, and we can control when "changes" are uploaded to the development
server. This way, the entire development server rarely goes down, and
development process can proceed on schedule.
I would be interested in any input from anyone else out there that has come
up with a better software management/development process for web
applications than the one I outlined above.
Celeste
-----Original Message-----
From: Jay [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 02, 2001 12:51 PM
To: JRun-Talk
Subject: Re: bean newbie question
Its a terrible thing. Imagine in a multi-developer environment how all of
this can have an effect on productivity - restarting all the time...
It ought to automatically recognize a modified bean - just like a modified
JSP, and recompile and create a new class file.
Can someone from Macromedia comment???
----- Original Message -----
From: "Jackie Comeau" <[EMAIL PROTECTED]>
To: "JRun-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, August 02, 2001 7:05 AM
Subject: RE: bean newbie question
> So, you recommend every time you make a JSP change to stop and restart the
> server to make sure JRun recognizes the change? I have not run into this
> yet, but I'm just playing around with JSP and actually developing anything
> serious yet.
>
> This is not a good thing! Is this a possible bug with JRun and has it been
> reported?
>
> I think I would test my JSP's changes anyways before putting them into
> production, so hopefully I won't come up with problems of new class files
> not replacing old automatically. But yeah, I see the problem if your
> copying your changes over assuming the production server is going to
> recompile.
>
> Hmmm, not good!
>
> Jackie
>
> On Wednesday, August 01, 2001 6:00 PM, Haseltine, Celeste
> [SMTP:[EMAIL PROTECTED]] wrote:
> > Jay,
> >
> > To answer your question, I don't think you can. The server loads all
> your
> > classes into memory, along with your compiled JSP pages. If your in a
> > development mode, JRUN will compile your JSP's to servlets the first
time
> > you request the JSP, and subsequently when it see's that the "saved"
date
> is
> > newer than the compile date. But not so for class files. In order to
> > replace an old class file with a new class file in memory, you have to
> stop
> > and restart the server. Although this is not usually required for JSP
> > pages, but I have had times where minor changes in a JSP did NOT cause
> JRUN
> > to recompile the JSP to a servlet, and I had to stop/restart the server
> in
> > order to reflect the changes in the JSP page also.
> >
> > If you are using JRUN studio as your IDE, you can stop and restart the
> > server from within the IDE using hotkeys. If not, you can assign a
> shortcut
> > to your desktop and stop/restart the server from the shortcut.
> >
> > Celeste
> >
> > -----Original Message-----
> > From: Jay [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, August 01, 2001 7:45 PM
> > To: JRun-Talk
> > Subject: bean newbie question
> >
> >
> > This should be simple. I have created a bean, the first time I execute
a
> > JSP page that calls the bean, a class file is created for the bean and
> the
> > jsp page in C:\test\WEB-INF\jsp. I then have to move the bean.class
> file
> > into the C:\test\WEB-INF\classes directory for my code to
> execute.(because I
> > get a java.lang.NoClassDefFoundError: getmov)
> > However, if I make a change to the source code of the bean and
> reexecute,
> > it appears that the original class is still in memory and manifests it
> self
> > when the JSP is executed thereby not reflecting the new changes. I have
> > remove all traces of the .java and .class files ( ie delete them) and
to
> > restart the default server inorder to create new classes.
> >
> > 1.How can I clear the old code and create a new class that reflects the
> > changes to the source without restarting the server everytime
> > 2. Where exactly should the .class file reside in the
> > C:\test\WEB-INF\classes or in C:\test\WEB-INF\classes\beans
> >
> > //HERE IS THE BEAN
> > import java.lang.* ;
> > public class getmov {
> >
> > private String convert,clipnumber ;
> >
> > public void setConvert (String convert)
> > {this.convert = convert ; }
> >
> > public String getConvert()
> > { return convert ; }
> >
> > public String getClipnumber()
> > { return clipnumber ; }
> >
> > public void setClipnumber(String clipnumber)
> > {
> >
> > if (this.convert != "TRUE")
> > { this.clipnumber = "TRUE" ; }
> > else
> > { this.clipnumber = "FALSE" ; }
> >
> > }
> >
> > }
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
