Hey
Bill Pfeiffer wrote:
> OK, I finally got Tomcat 3.2 b4+ and JBoss bp3 configured to work together
> in harmony. I've also got my webapp (jsp and servlets) working just as it
> did in Tomcat alone. I've also got my 2 Entity Beans working. I can call
> one the entity beans from a servlet. My servlet are utilizing the jBoss
> connection cache as I had planned. Everything is packaged up in an EAR file
> and deploys, and works fine together.
>
> So far this is all very cool.
>
> Now, I need to know how to do ongoing development in such an environment.
>
> When doing Tomcat dev alone, I just worked out of the dir where my jsp's and
> servlet were to be deployed, no need to restart the server (which if I did
> have to, if wasn't very expensive, time-wise).
>
> When doing JBoss dev alone, I could compile and hot deploy, which was also
> fairly cheap time-wise.
>
> Now it seems I've got to package up all my stuff in an ear file and deploy
> for every change I make. Deployment seems to take about a minute or more.
> Productivity killer.
>
> Is there a better approach to ongoing development? For now I'm going to
> drop back to running the two seperatly and then do some occasional
> integration testing to make sure things still work together. I'm hoping
> there's a better way.
>
> I'd appreciate some input from the other Tomcat-JBoss experimentors out
> there.
I personally run Tomcat and jBoss separate during development, and let
Tomcat work from the compilation output directory, while I jar and copy
the EJB's to jBoss's deploy directory. This is rather arbitrary: I could
just as well let jBoss AutoDeployer work from the development
compilation directory just as Tomcat.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
