Re: Side effect of OSX on Intel announcement

On Jun 9, 2005, at 5:45 AM, Giulio Cesare Solaroli wrote:

> Hi Pierce,
>
> we are still using WebObjects 4.5.1 (objective-C), and we are stuck
> with Jaguar (MacOS 10.2.x).
>
> Have you been able to run any WebObjects-ObjC applications on  
> Panther/Tiger too?

  Yes. Doing it right now on Tiger!
>
> I would be very interested in knowing how did you achieve that, as we
> are worried abount the current Apple hardware not beeing able to run
> MacOS 10.2.

   Well, we buy G5 XServes all the time, so here goes.

   At this point, we have this all in a giant tgz file we just  
extract, so this is off the top of my head.

   Basically, starting from a working 10.x install of WO4.5.1P4, tar  
up the following files/directories:

Developer/Applications/EOModeler.app/
Developer/Applications/WebObjects Builder.app/
System/Library/Frameworks/EOAccess.framework/
System/Library/Frameworks/EOControl.framework/
System/Library/Frameworks/EOInterface.framework/
System/Library/Frameworks/EOModeler.framework/
System/Library/Frameworks/Plot.framework/
System/Library/Frameworks/WebObjects.framework/
System/Library/Frameworks/WOExtensions.framework/
System/Library/PrivateFrameworks/MultiScript.framework/
System/Library/PrivateFrameworks/XML.framework/
System/Library/StartupItems/WebObjects/
System/Library/StartupItems/WebObjects/StartupParameters.plist
System/Library/StartupItems/WebObjects/WebObjects
System/Library/WebObjects/Adaptors/
System/Library/WebObjects/Applications/
System/Library/WebObjects/Executables/

Basically, you need to get the two PrivateFrameworks above, and there  
are a couple of .plist files in WebObjects that were missing a  
trailing ';'. The 10.0 .plist parser was more flexible, the 10.1+  
complains. You can fix it by just opening it in a text editor and  
adding a ; to the end of the file.

  Though if you're running on 10.2, you've probably fixed all that  
already.

  Repeat for a deployment install instead of a developer install,  
though in that case you don't need some of the above stuff.

  That's pretty much it. WO is basically a command line process, so  
it doesn't depend on stuff.

  Then in your xcode projects (after upgrading them):

    The new KVC stuff ends up overriding the old WO KVC stuff, so you  
have to include Foundation.framework LAST, after all the WO EOF stuff  
so that WO uses the old KVC stuff instead of the new KVC stuff. I  
think that happened in Panther? so that may be your problem.


  The newer operating systems are also more fussy about if  
"application"includes framework1, but not framework2, but framework1  
included framework2, it used to be ok. Now "application" has to  
include framework2 as well if it uses it.

>
> For the definitive "exit" strategy we are closely looking at SOPE
> (http://sope.opengroupware.org/en/), that seems to be able to easily
> replace the WebObject.framework. For the EOF stuff things are more
> complex, but it looks like GDL2 is still under active (but not
> astonishing fast) development.

   Yeah, that's about where I was at too, its just that sope uses  
GDL1...

  Pierce

_______________________________________________
WebObjects-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-talk