Hi!  
  I'm trying to update the timezone list of the JVM using  
tzupdater-1_3_21, but when I run it, I get this message: 

  java -jar tzupdater.jar -u -v
 java.home: /usr/local/diablo-jdk1.6.0/jre
 java.vendor: The FreeBSD Foundation
 java.version: 1.6. [...]

Hi Chuck    Excellent, thanks!   Regards  Mikkel Eide Eriksen Basepoint Media 
   On Fri, Nov 6, 2009 at 6:38 PM, Chuck Hill <email@hidden> wrote: 

The mod_webobjects adaptor is C code, it does not use any of the Java frameworks. 


Chuck  


On Nov 6, 2009, at 1:47 AM, Mikkel Eide Eriksen wrote:

[ [...]

The mod_webobjects adaptor is C code, it does not use any of the Java  
frameworks. 

  Chuck  
  On Nov 6, 2009, at 1:47 AM, Mikkel Eide Eriksen wrote:

[...]

Chuck Hill             Senior Consultant / VP Development  
Practical WebObjects - for developers who want to increase their   [...]

Sorry, I think I was unclear.    Wotask/monitor/etc will all be running on application servers.     The image I'm making will *only* be running the webserver with the adaptor, and will communicate with external wotaskdaemons. So the question is, which of the frameworks - if any - does the adaptor require to run. 

  Regards  Mikkel Eide Eriksen Basepoint Media 
   On Fri, Nov 6, 2009 at 1:46 PM, Kieran Kelleher <email@hidden> wrote: 

Open the *.woa/Contents/MacOS/MacOSClassPath.txt files inside wotaskd,woa and WOMonitor.woa to see their dependencies and decide what's needed where if there any any non APPROOT (APPROOT = embedded) dependencies. 



On Nov 6, 2009, at 4:47 AM, Mikkel Eide Eriksen wrote:

[...]

Open the *.woa/Contents/MacOS/MacOSClassPath.txt files inside  
wotaskd,woa and WOMonitor.woa to see their dependencies and decide  
what's needed where if there any any non APPROOT (APPROOT = embedded)  
dependencies. 

 On Nov 6, 2009, at 4:47 AM, Mikkel Eide Eriksen wrote:

[...] [...]

Hi    I'm creating an image that's as bare-bones as possible to serve as front-end for a number of app-servers. It'll be running on Debian with the Wonder adaptor for Apache 2. The wotaskdaemons & javamonitor will be running on the appservers. 

    Does this require any of the frameworks? [...]

[...]

Ute, if you follow Mike's advice to fully embed all necessary  
frameworks in each app you won't need to downgrade the server. i.e.,  
5.3 apps with fully embedded frameworks will run just fine under a 5.4  
installation. 

 with regards,






  References:   

[...]

Re: WebObjects on 10. [...]

Ute, please see the front page of one of the links I sent you  
previously "A statement about Snow Leopard and WebObjects": http://www.wocommnity.org 
. 

 Clark.  
 On 2009-11-04, at 9:25 AM, ute Hoffmann wrote:

[...]

Hi,
another one (Problems seem to arise in fast sequence now):  
 I would like to install WebObjects on a fresh Mac OS X 10.6 Server.  
I looked into Developer.apple.com for a WebObjects Version, but found  
only Update 
versions for 5.4, but no full standalone version. [...]

You can simply specify -DWORootDirectory="/some/place/5.3" as a launch  
arg and install the frameworks there. 

 Cheers, Anjo  

 Am 04.11.2009 um 10:23 schrieb Clark Mueller:  
I cannot speak to what Xcode supports in this area and how to do it  
(it's been way too long since I used Xcode to remember), but you  
really need to take this opportunity to move to Eclipse and WOLips.  
You are going to be in for a world of pain when you get around to  
moving to Snow Leopard in the future. Eclipse/WOLips/WOProject will  
greatly simplify your build process in the long run as far as  
juggling multiple versions of the frameworks. You can find lots of  
documentation about this migration in the list archives, the wocommunity.org 
 site, and on the ObjectStyle wiki here: http://wiki.objectstyle.org/confluence/display/WOL/Home 
. Some topics that pertain directly to your situation are: 

 http://wiki.objectstyle.org/confluence/display/WOL/Migrating+from+XCode+to+WOLips
http://wiki.objectstyle.org/confluence/display/WOL/Import+an+Xcode+project+into+WOLips
http://wiki.objectstyle.org/confluence/display/WOL/Embedding+WOFrameworks
http://wiki.objectstyle.org/confluence/display/WOL/Using+WOLips+With+Multiple+Versions+of+WebObjects  
With respect to your other two threads and downgrading your server,  
this is an option if you reallllly want to do it (do JavaMonitor and  
wotaskd also, and ensure that all of your permissions are proper),  
but you'll be a happier person if you go with the embedded solution. 

You can also use the WO 5.4 versions of JavaMonitor and wotaskd, but  
create a new directory inside your deployed .woa of Foo.woa/Contents/ 
Library/Frameworks that contains all of your dependencies, and then  
manually edit the MacOSClassPath.txt file to reference APPROOT/ 
Library/Frameworks for each framework instead of wherever it's  
pointing now. This is essentially what an embedded build is, but  
this manual workaround is absolutely a sub-optimal approach to  
having it done automagically for you. 

 Clark  
 On 2009-11-03, at 11:16 PM, ute Hoffmann wrote:  
Can I build fully embedded with xcode, as that is my development  
tool? 

 If yes, how?  
 Am 04.11.2009 um 01:32 schrieb Mike Schrag:  
build fully embedded .. avoid this entire mess. just build with WO  
5.3 in the app. 

 On Nov 3, 2009, at 7:28 PM, ute Hoffmann wrote:

[...]

Hi Ute    On 4 Nov 2009, at 09:55, ute Hoffmann wrote:  > quoted text
   Yes - that's basically what we did - we did set up the 'swap' scripts because we were doing that on the development machine anyway.  That list of WO frameworks is very useful - stick to that and don't just swap over *all* 'Java*' frameworks. > quoted text
    I believe we carried on using the 5.4 versions that came with the Leopard server.  I do recall we got into some issues with actually accessing the app through Apache - everything started up ok but attempts to use the app frequently got 'server busy' alerts.  We had to change something completely non-obvious in the Apache config.  Perhaps you won't encounter this issue!     Liz       Regards,     Ute     Am 04.11.2009 um 10:22 schrieb Elizabeth Lynch:  Hi Ute       On 4 Nov 2009, at 08:17, ute Hoffmann wrote:  > quoted text
   Yes, we have done this and it seems to work OK using the 5.3 frameworks.  However, the installation on which we did this is not using Wonder.   Have a look at this extract from a post to the WO-Dev list from Mike Schrag in October 2007.  The thread is titled:  'The Official What-I-Did-To-Run-5.3-On-Leopard Post'.      * The following can be done a couple ways, but this is just how I happened to have things setup in betas, so I kept it (it worked for me):   ** Make a /System/Library/Frameworks/WebObjects54 folder, and move the following frameworks from the 5.4 install into it:  	JavaDTWGeneration.framework  	JavaDirectToWeb.framework  	JavaEOAccess.framework  	JavaEOApplication.framework  	JavaEOControl.framework  	JavaEODistribution.framework  	JavaEOGeneration.framework  	JavaEOInterface.framework  	JavaEOInterfaceCocoa.framework  	JavaEOInterfaceSwing.framework  	JavaEOProject.framework  	JavaEORuleSystem.framework  	JavaEOTool.framework  	JavaFoundation.framework  	JavaJDBCAdaptor.framework  	JavaJNDIAdaptor.framework  	JavaWOExtensions.framework  	JavaWOJSPServlet.framework  	JavaWebObjects.framework  	JavaWebServicesClient.framework  	JavaWebServicesGeneration.framework  	JavaWebServicesSupport.framework  	JavaXML.framework     ** Make a /System/Library/Frameworks/WebObjects53 folder, and move the following frameworks from your old 5.3 install into it (I tar'd these up from 5.3 before upgrading, but you can download 5.3 and extract these from the pkg, or POSSIBLY install them with the actually installer ... YMMV on that one)  	JavaDTWGeneration.framework  	JavaDirectToWeb.framework  	JavaEOAccess.framework  	JavaEOApplication.framework  	JavaEOCocoa.framework  	JavaEOControl.framework  	JavaEODistribution.framework  	JavaEOGeneration.framework  	JavaEOInterface.framework  	JavaEOInterfaceCocoa.framework  	JavaEOInterfaceSwing.framework  	JavaEOProject.framework  	JavaEORuleSystem.framework  	JavaEOTool.framework  	JavaFoundation.framework  	JavaJDBCAdaptor.framework  	JavaJNDIAdaptor.framework  	JavaWOExtensions.framework  	JavaWOJSPServlet.framework  	JavaWebObjects.framework  	JavaWebServicesClient.framework  	JavaWebServicesGeneration.framework  	JavaWebServicesSupport.framework  	JavaXML.framework     ** I then use the following two scripts to be able to switch between using 5.3 and 5.4 system wide:   bash-3.2# cat wo53   for framework in `ls /System/Library/Frameworks/WebObjects53`; do rm /System/Library/Frameworks/$framework; ln -sf /System/Library/Frameworks/WebObjects53/$framework /System/Library/Frameworks/$framework; done     bash-3.2# cat wo54   for framework in `ls /System/Library/Frameworks/WebObjects54`; do rm /System/Library/Frameworks/$framework; ln -sf /System/Library/Frameworks/WebObjects54/$framework /System/Library/Frameworks/$framework; done     ** At this point, you should have NO WO frameworks in /System/Library/Frameworks -- they should be in subfolders.     ** Now go ahead and run wo53, which should now give you WO 5.3 framework symlinks      > quoted text
        

I cannot speak to what Xcode supports in this area and how to do it (it's been way too long since I used Xcode to remember), but you really need to take this opportunity to move to Eclipse and WOLips. You are going to be in for a world of pain when you get around to moving to Snow Leopard in the future. Eclipse/WOLips/WOProject will greatly simplify your build process in the long run as far as juggling multiple versions of the frameworks. You can find lots of documentation about this migration in the list archives, the wocommunity.org site, and on the ObjectStyle wiki here: http://wiki.objectstyle.org/confluence/display/WOL/Home. Some topics that pertain directly to your situation are:     http://wiki.objectstyle.org/confluence/display/WOL/Migrating+from+XCode+to+WOLips  http://wiki.objectstyle.org/confluence/display/WOL/Import+an+Xcode+project+into+WOLips  http://wiki.objectstyle.org/confluence/display/WOL/Embedding+WOFrameworks  http://wiki.objectstyle.org/confluence/display/WOL/Using+WOLips+With+Multiple+Versions+of+WebObjects     With respect to your other two threads and downgrading your server, this is an option if you reallllly want to do it (do JavaMonitor and wotaskd also, and ensure that all of your permissions are proper), but you'll be a happier person if you go with the embedded solution.      You can also use the WO 5.4 versions of JavaMonitor and wotaskd, but create a new directory inside your deployed .woa of Foo.woa/Contents/Library/Frameworks that contains all of your dependencies, and then manually edit the MacOSClassPath.txt file to reference APPROOT/Library/Frameworks for each framework instead of wherever it's pointing now. This is essentially what an embedded build is, but this manual workaround is absolutely a sub-optimal approach to having it done automagically for you.       Clark     On 2009-11-03, at 11:16 PM, ute Hoffmann wrote:   Can I build fully embedded with xcode, as that is my development tool?  If yes, how?  Am 04.11.2009 um 01:32 schrieb Mike Schrag:  > quoted text

[...]

Hi Ute       On 4 Nov 2009, at 08:17, ute Hoffmann wrote:  > quoted text
   Yes, we have done this and it seems to work OK using the 5.3 frameworks.  However, the installation on which we did this is not using Wonder.   Have a look at this extract from a post to the WO-Dev list from Mike Schrag in October 2007.  The thread is titled:  'The Official What-I-Did-To-Run-5.3-On-Leopard Post'.      * The following can be done a couple ways, but this is just how I happened to have things setup in betas, so I kept it (it worked for me):   ** Make a /System/Library/Frameworks/WebObjects54 folder, and move the following frameworks from the 5.4 install into it:  	JavaDTWGeneration.framework  	JavaDirectToWeb.framework  	JavaEOAccess.framework  	JavaEOApplication.framework  	JavaEOControl.framework  	JavaEODistribution.framework  	JavaEOGeneration.framework  	JavaEOInterface.framework  	JavaEOInterfaceCocoa.framework  	JavaEOInterfaceSwing.framework  	JavaEOProject.framework  	JavaEORuleSystem.framework  	JavaEOTool.framework  	JavaFoundation.framework  	JavaJDBCAdaptor.framework  	JavaJNDIAdaptor.framework  	JavaWOExtensions.framework  	JavaWOJSPServlet.framework  	JavaWebObjects.framework  	JavaWebServicesClient.framework  	JavaWebServicesGeneration.framework  	JavaWebServicesSupport.framework  	JavaXML.framework     ** Make a /System/Library/Frameworks/WebObjects53 folder, and move the following frameworks from your old 5.3 install into it (I tar'd these up from 5.3 before upgrading, but you can download 5.3 and extract these from the pkg, or POSSIBLY install them with the actually installer ... YMMV on that one)  	JavaDTWGeneration.framework  	JavaDirectToWeb.framework  	JavaEOAccess.framework  	JavaEOApplication.framework  	JavaEOCocoa.framework  	JavaEOControl.framework  	JavaEODistribution.framework  	JavaEOGeneration.framework  	JavaEOInterface.framework  	JavaEOInterfaceCocoa.framework  	JavaEOInterfaceSwing.framework  	JavaEOProject.framework  	JavaEORuleSystem.framework  	JavaEOTool.framework  	JavaFoundation.framework  	JavaJDBCAdaptor.framework  	JavaJNDIAdaptor.framework  	JavaWOExtensions.framework  	JavaWOJSPServlet.framework  	JavaWebObjects.framework  	JavaWebServicesClient.framework  	JavaWebServicesGeneration.framework  	JavaWebServicesSupport.framework  	JavaXML.framework     ** I then use the following two scripts to be able to switch between using 5.3 and 5.4 system wide:   bash-3.2# cat wo53   for framework in `ls /System/Library/Frameworks/WebObjects53`; do rm /System/Library/Frameworks/$framework; ln -sf /System/Library/Frameworks/WebObjects53/$framework /System/Library/Frameworks/$framework; done     bash-3.2# cat wo54   for framework in `ls /System/Library/Frameworks/WebObjects54`; do rm /System/Library/Frameworks/$framework; ln -sf /System/Library/Frameworks/WebObjects54/$framework /System/Library/Frameworks/$framework; done     ** At this point, you should have NO WO frameworks in /System/Library/Frameworks -- they should be in subfolders.     ** Now go ahead and run wo53, which should now give you WO 5.3 framework symlinks      > quoted text
        

Hi,
is it possible to  
a) put the WebObjects 5.4 Frameworks into another folder 
b) put the WebObjects 5.3 Frameworks from another server into the  
default folder 

and thus run WebObjects 5.3 on this server without any reinstall and  
being able to switch 
back to WO 5. [...]

Hi, 
As I'm not an eclipse user and will not change to Eclipse with  
several frameworks and apps with about one day 
to get everythink running and built correctly (and then no longer  
being able to use WebObjects builder in future and being thrown back  
to code Html/and the wod  [...]

Can I build fully embedded with xcode, as that is my development tool?  
 If yes, how?  
 Am 04.11.2009 um 01:32 schrieb Mike Schrag:  
build fully embedded .. avoid this entire mess. just build with WO  
5.3 in the app. 

 On Nov 3, 2009, at 7:28 PM, ute Hoffmann wrote:

[...] [...]

build fully embedded .. avoid this entire mess. just build with WO 5.3  
in the app. 

 On Nov 3, 2009, at 7:28 PM, ute Hoffmann wrote:

[...]

hi, 
i have this scenario: 
i have a new leopard 10.5 server, i have webobjects 5.3 applications  
with wonder compiled under java 1.4. 

now 
1. is there a way to downgrade the server to use wo 5.3 in place of  
wo 5.4 which comes preinstalled 
2. in case i keep wo 5. [...]