At 01:49 AM 07/31/03, Vikram Naik wrote:
>But still I have a query regarding the packaging for an enterprise
>application.

Deployed only within the enterprise, or sold as a commercial product? The two have different requirements.

>Should the ear file contain only the ejbs and a war file with only web
>resources with jsp,servlets , htmls and images, and the libs say a jar doing
>some xml parsing be placed in system lib.Can it also help as far as
>maintainence is cconcerned.

For a commercial product, I'd start with the complete list of components of your product. You have full rights over those components. To make it explicit, put those in the application .ear. For 3rd-party libs, there's a tradeoff. You can distribute (if the license allows it) those libs in another .jar with your app. But then that locks the user into using those libs in order to get support.

If you don't want to, or can't, distribute the libs, then you just certify the app. with specific versions of the 3rd-party libs, and require users to install those versions themselves. This is safer and more supportable all around, because you can continue to test against newer lib versions and certify on those, so you keep up with the 3rd-party changes. This approach also lets you treat a commercial product and an internal app. more similarly. You can help users obtain the proper versions of 3rd-party libs by including a list of recommended links plus MD5s for the versions you certify against, so users can get the proper ones. If the 3rd-party libs aren't freely available, then you have to work out the costs of using them....

HTH,
TW

===========================================================================
To unsubscribe, send email to listserv@(protected)
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected)".