The worst part of J2EE in general,not only jboss specific, is debugging and testing. It is so difficult to set up environment in which you could change a line, hit compile and test it, and the whole process would take say 10 seconds. Impossilble. I believe this is due to compressed jars,wars, and ears. I believe eclipse has now a option of debugging ejbs the way we are used from other IDEs, like in dotnet. The second slowdown in my opinion is container itself. It "contains" beans. Windows com+ components are just dlls. You deploy it one time, and then you just copy new dll over it. I am so missing standard way of full development circle.
And about that opinion that websphere is even slower. This is nonsense. Why compare to a slower product, why not compare to faster, robuster and better.
Also I was using Ant for compile, and another IDE for development. When I put compiling in IDE, the things were much better.
Also I agree to certain degree that it is better to fix a lot of stuff in one compile step,but it is also more demanding and so should not be mandatory. Some people are used to take one step at the time.
Bye,ivan
-----Original Message-----
From: Clover, James [mailto:[EMAIL PROTECTED]]
Sent: 18. junij 2003 20:59
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Developing and debuging
Shouldn't this type of testing (i.e., it requires the app server to be
running for the test) be 5-10% of your overall testing? You may want to
investigate things like Junit and debugging under JUnit for 90% of your
testing needs - you can get much faster turn around time for the vast
majority of your testing. Then you only need to do this slower testing
for a very short amount of time.
James
------------
James Clover
Lead Engineer, Disney Enterprise Portal
james -dot- clover -at- disney -dot- com
-----Original Message-----
From: Peng Zhao [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 17, 2003 2:40 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Developing and debuging
I met a big problem when developing and debuging.
If I deploy the application as a "war" file, the jboss needs about 30
seconds to deploy it. Although it is not too long, for developing and
debuging it is not affordable! The time for waiting is longer than the
time for fixxing the bug!
If I deploy the application as a directory (e.g. "app.war"), the .jsp
can be reloaded when I replace a .jsp file in the directory. But the
.class file can not be updated once it has run. It seems the jboss has a
cache for the loaded .class file.
Because the debuging<->deploying is so slow, I wasted a lot of time for
even fixxing a small bug. Furthermore, the .jsp is so slow when first
loaded from the web-client. Is that usual?
Thanks!
Peng
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
