Is Java EE really enterprise?
I really didnt know where to post to this topic, so I thought this forum seems to be most approriate to share some frustration with Java EE.
I have been being doing java ee for fairly a small amount of time which is three years for mission critical applications, specifically in the financial sector.
Due to nature of the business, small changes are required every now and then which are a nightmare for us developers and the entire IT department.
In order to add a simple IF condition in a plain java class or a session bean the application has to be undeployed, deployed and in most cases the container requires a restart because the undeployer usually leaves some hanging files which we have to delete manually from the application before deploying, this process in best case scenario requires about 15 minutes, which I think totally condradicts the concept of high availabilty.
Someone might suggest clustering, well clustering is not mandatory in the j2ee specification and requires alot of effort and doesnt make much sense when you have a good piece of hard ware server which can survive almost any hardware failure and by far exceeds your hardware requirements and you ask your management for another server just because when you redeploy you dont want to bring the system to halt.
This doesnt convey anyone, sounds like a limitation in the Java EE I have once read the following post in a Hot deployment thread "In Oracle, you can change 99.9% of the settings without shutting down anything or even interrupting a single transaction. Ask any DBA what he would think about a DBMS that had to be shut down to add a security role or a stored procedure." Apparantly someone think that all this javaEE deployment is a hassel.
Regards,
Hussam Galal
