Re: java heap trouble after 5.4.1 upgrade, opensnoop to the rescue
Re: java heap trouble after 5.4.1 upgrade, opensnoop to the rescue
- Subject: Re: java heap trouble after 5.4.1 upgrade, opensnoop to the rescue
- From: Gavin Eadie <email@hidden>
- Date: Fri, 22 Feb 2008 19:33:42 -0500
One of the aspects of WebObjects it took me a long time to figure out was that it's a lot more amenable to being deployed in various different ways than I first thought. The 'out of the box' method has been as Guido suggests with sets of frameworks ("Apple" and "local") shared by multiple applications -- that was our environment for a few years. Then our development team divided responsibilities and our "local" frameworks forked, so it made sense to embed them so each applications would be self-sufficient. Recently, I've taken one application to WO 5.4.1 and it makes sense for me to deploy it with Apple's frameworks embedded.
I guess my point is there is no right way to do this -- I'm just thankful that the veterans who created all this were smart enough to leave us this flexibility, and hope that today's equally wise providers of WOGoodness keep that in mind .. Gav
On Feb 22, 2008, at 6:53 PM, Guido Neitzer wrote: I disagree on this one. Embedding frameworks enables you to be independent of the version of WebObjects installed on the target machine. Considering the cost of disk drive (<1$/Gb) 10Mb is a negligible it is save you debug time. Even the upload time is very small if you tar your application before uploading.
Let's put it that way: there might be situations where it makes sense, but I doubt that these situations are very common.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden