Re: Deployment performance
Alex Bairov wrote: > > Hello, > > We are deploying .ear containing 12 ejb .jars and 1 .war. It > takes 3 minutes to deploy, even if I have changed only one .jar. > Could I speed this up somehow? > > -- > Best regards, > Alex Bairov Hi Alex. When you do your builds, make sure that your unchanged jars are not touched. I have my Ant script check to see if the files in a particular Jar have been updated before it builds that jar. If it doesn't need to be rebuilt, the Ant script skips on to the next jar. -Steve -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208
RE: Deployment performance
Try with jikes it will be help u speed up deployement. -Original Message- From: Alex Bairov [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 9:36 AM To: Orion-Interest Subject: Deployment performance Hello, We are deploying .ear containing 12 ejb .jars and 1 .war. It takes 3 minutes to deploy, even if I have changed only one .jar. Could I speed this up somehow? -- Best regards, Alex Bairov
Deployment performance
Hello, We are deploying .ear containing 12 ejb .jars and 1 .war. It takes 3 minutes to deploy, even if I have changed only one .jar. Could I speed this up somehow? -- Best regards, Alex Bairov
Re: deployment performance
At 17:00 22.01.00 , you wrote: >Are you using jikes? yes >I'm using JDK1.3beta, and Jikes, and the compile time is quite fast. >With JSP pages you hardly even notice the compile time for most pages. it all depends on the size of the project. I'm talking about approx. 2 lines of EJB code that take ages to deploy even with jikes (in fact the compilation part is not the problem as I can see jikes output when it starts to compile and that's only a fraction of the total time it takes). I'm not saying it's unacceptable for deploying it the first time but what I think is unacceptable, is the fact that one simple code change (not even changing an interface) forces me to go through the entire process for all of the beans again and that makes development with large projects VERY slow. I couldn't think of a reason why wrapper code would have to be regenerated if I modify the implementation of a bean method. It just seems that orion's policy for deployment is "see if anything has changed and then redo the whole thing", which has become a development bottleneck for the project I'm currently working on. I think with just a little more housekeeping it should be possible to significantly reduce deployment time for large projects. robert >Noah Nordrum >Hyperride Technologies > (-) Robert Krüger (-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH (-) Brüder-Knauß-Str. 79 - 64285 Darmstadt, (-) Tel: 06151 665401, Fax: 06151 665373 (-) [EMAIL PROTECTED], www.signal7.de
deployment performance
Hi, in case you're counting votes for possible improvements I would like to ask for something being done about the deployment performance. is it possible to restrict wrapper generation and everything to ejbs that have changed? if I recompile one bean in an application all others get redeployed too including the code generation. this takes ages if your application has lots of ejbs and makes develoment quite slow. thanks, robert (-) Robert Krüger (-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH (-) Brüder-Knauß-Str. 79 - 64285 Darmstadt, (-) Tel: 06151 665401, Fax: 06151 665373 (-) [EMAIL PROTECTED], www.signal7.de