• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6775
  • Last Modified:

Deploying EAR versus exploded EAR

We are developing an application which stands at around 40Mb when packaged into an EAR. We are finding the hot-deploy of the application to be very slow and I've suggested that we start deploying the application as an exploded EAR.

I *think* this would be qukcker as it means we dont have to wait for the application to be packaged by our IDE, then unpackaged by JBoss before being deployed.

The only question I have is if there is any difference with classloading when deploying an EAR either as a jar, or in exploded format? Or are there any other differences to note?
0
colr__
Asked:
colr__
1 Solution
 
KuldeepchaturvediCommented:
to the best of my knowledge.. it does not make a difference in class loading or any other thing like url mapping etc..

EAR file is nothing but a mechanism to package the contenet in a format that app server understands & can explod on its own.
0
 
mbvvsatishCommented:
As kuldeep said there is absolutely no difference in classloading for ear and exploded ear deployment.
as far as i know, both are one and the same.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now