Re: [WDSCI-L] JSF and App Servers

["colin williams" <colin.williams@xxxxxxxxxxxx>]

Mike,

I think it really depends on your environment. if you have a good
configuration management tool then you could probably get away with
everything in one EAR.

But for ease of managing your applications you would probably want to group
discreet applications into different EARs.

What we tend to do is drop minor changes straight into the deployed live
environment, and let the application automatically reload (this only works
if you have reloading on in live).

If we are making a major change, then we will redeploy the whole
applications EAR. You can redeploy everything in one EAR without affecting
any others. So to update, we stop that application, update the EAR, and
restart the application. When you stop the application, every application
under that EAR is stopped.

So if you group related applications into one EAR, or have one application
for one EAR, yes you may have some duplication, but deployment is going to
be less of an issue. Removing that duplication is likely to bring its own
problems.

cheers
Colin.W

----- Original Message ----- 
From: "Mike Eovino" <meovino@xxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, November 01, 2004 7:58 PM
Subject: Re: [WDSCI-L] JSF and App Servers


> Aaron,
>
> Bring this up on the Ignite list and watch Cancilla blow a gasket!  We
> get our 520 with WAS-E in a week or so; I'm already worrying about
> this one.  From what I've been told, it sounds like web assets (like
> images and such) can't really be reused easily.  You stick them in the
> EAR, and that's where they live.
>
> My question (sort of in the same vein) is should I have different
> EAR's for the different "applications" on my site (shipment tracking,
> transit time lookup, rate quote), or should all of my interactive apps
> be in one EAR?
>
> Mike E.
>
>
> On Mon, 1 Nov 2004 11:10:10 -0600, Bartell, Aaron L. (TC)
> <albartell@xxxxxxxxxxxxxx> wrote:
> > >(one of the mixed benefits of J2EE is that everything gets encapsulated
> > and can stand on its own)
> >
> > Glad you brought this up, because I have been wondering about it for
> > some time.  In the RPG world we can bind a component (say service
> > program) by reference and as long as the bound component is on the
> > machine and in the current library list, it can then be used by the
> > consuming app.  How would one do this in Java?
> >
> > What are the packaging practices others use for doing J2EE development?
> > Does a whole application get put into an EAR or does each component have
> > it's own EAR file (one could describe component as a business logic
> > class or a jsp page)? Is it possible to share an object across EAR's
> > without that object being duplicated?
> >
> > I can definitely see the benefits to having and EAR file that is
> > independent from anything else, but that also creates a maintenance
> > nightmare if you have a lot of reusable code.
> >
> > Thoughts?
> > Aaron Bartell
> >
> >
> >
> >
> > -----Original Message-----
> > From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
> >
> > Sent: Monday, November 01, 2004 9:27 AM
> > To: Websphere Development Studio Client for iSeries
> > Subject: RE: [WDSCI-L] JSF and App Servers
> >
> > WDSC by default puts all the JARs required by the web module into the
> > WEB-INF/lib directory (one of the mixed benefits of J2EE is that
> > everything gets encapsulated and can stand on its own).  You can
> > identify any non-standard (or not-standard-yet) classes because the
> > packages wil start with com.ibm.
> >
> > -----Original Message-----
> > From: wdsci-l-bounces+rdean=landstar.com@xxxxxxxxxxxx
> > [mailto:wdsci-l-bounces+rdean=landstar.com@xxxxxxxxxxxx] On Behalf Of
> > Bartell, Aaron L. (TC)
> > Sent: Friday, October 29, 2004 6:17 PM
> > To: Websphere Development Studio Client for iSeries
> > Subject: [WDSCI-L] JSF and App Servers
> >
> > As I read different groups implementation of JSF (IBM, Sun, etc) I am
> > finding that they all have their own custom JSP tag lib for the JSF
> > components.
> >
> > My question is specifically this.  What do I need to watch out for if I
> > develop my JSF in WDSc using jsf-ibm.jar and deploy that to Tomcat 5?
> > Note that I am not using WDO which I have heard is IBM specific (for
> > now).
> >
> > Thanks in advance,
> > Aaron Bartell
> >
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.
>

This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.