This content has been marked as final.
Show 2 replies
-
1. Re: PAR and EAR granularity / deployment best practice?
triathlon98 Oct 17, 2005 10:53 AM (in response to rdewell)I think you have two choices :
- make sure you are not using a scoped classloader and use a separate archive for the shared code
- put all in on big ear
I think having the shared code in both archives can cause problems, especially if the shared code would itself be different versions at some point.
Hope this helps,
Joachim -
2. Re: PAR and EAR granularity / deployment best practice?
bill.burke Oct 17, 2005 12:04 PM (in response to rdewell)I think you can have a .jar (if not, then definately a .sar) with:
all.jar/
A.ear
B.ear
stuff.par