![]() There you can see where the problem really is in this case and that you can avoid it. A single JSF hello world with db access sucked up more than one gig. However I gave recently the Studio Creator a try and that one is using the Sun app server. For a standard installation use: disk1setupsetup.exe -silent For a responsefile installation use disk1setupsetup.exe -silent -options 'pathresponsefile. ![]() Go for a plain Tomcat or Resin, ass spring to the mix, JSF or whatever and you are perfectly happy. 118 Command Line You will need to copy the first three CDs into directories naming them disk1 through disk3 in order for the silent install to recognize them. The main culprit of those tools usually is the J2EE EJB container, I do not know why they suck up ram like hell, but they do. The trick is I do not go to a bloated EJB container but go for a plain servlet runner and use libs which deliver the functionality. My dev machine has 1 gig of ram, and I usually run 1-2 eclipse parallel and 3 app servers and usually a db server and do not have any swapping at all. I do server side dev for a living and I am using eclipse in combination mostly with myeclipse or exadel.Īnd while these tools need ram (every IDE does) it is not that exaggerated. The funny thing is in this case probably WS6.0 is to blame. It seems to be a common trend, once a java program is sluggish or comsumes lots of ram, automatically java is to blame not the program. IBM® Rational® Application Developer for WebSphere® Software V8 is the full-function Eclipse 3.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |