Re: Witango-Talk: Non-notable product
That's OK. They have right. Original Phil, wroten on 29.04.2008: Hi all, Before this thread gets a life of its own let me just say that there is more to this release as we move to commercial open source model than just software. We have basically finished the engineering but there are still some legal and business issues we are continuing to work through. It all takes time and we are not just sitting here idly. While we have been waiting for these issue to be resolved we have been adding extra features to the studio. As soon as I can release v6 I will. Regards Phil Also, Phil have writen on 11.02.2008 WITANGO COMMUNITY UPDATE Th Witango 6 development project is now drawing to a close and in the coming weeks a full public beta of both studio and server will be released. The full release of Witango 6 will be accompanied by significant changes to both pricing and licensing, we therefore take this opportunity to update the community as we move forward. New Licensing - Once the beta testing has been completed and version 6 goes into release, the source code for both the server and studio will be open sourced under its own license. Witango will continue to be a commercial product and a license will need to be purchased. There will be 3 editions of the Server: The Lite edition - no change to current license conditions The Developer edition - no change to current license conditions. The Professional edition - single machine license, with no limitation on number of processes or CPUs. New Pricing --- Witango Studio v6 US$199 Witango Studio upgrade - US$99 Witango Server Lite - Free Witango Server Developer Edition - Free with studio Witango Server Professional - US$1499 Witango Server Upgrade from v5.5 - US$999 Witango Server Upgrade from pre v5.5 - US$1299 Those customers who own Witango 5.5 professional edition servers will have the option at the time of upgrade to upgrade their server to two (2) Witango 6 Professional edition licenses for US$1499. Witango licenses will only be available direct from Witango Technologies and no further discount will apply. Your Enquiries --- A comprehensive outline of new features will be available on release of the beta. We understand many of you will have questions, please direct them off list to [EMAIL PROTECTED] We will compile a FAQ and post back to the list. It has been a long term goal for Witango Technologies to move Witango to an Open Source product, with simplified and affordable licensing. Witango v6 therefore represents a major milestone for us. We would also take his opportunity to thank our development team who have worked with consistent enthusiasm and considerable effort in preparing the code for open source. Sophie Wade have wrote me on 18.10.2006 Daniel That is correct. Regards Sophie Wade Witango Technologies Pty Ltd 44 Miller St, North Sydney NSW, 2060, Australia phone: +61 2 9460 0500 fax: +61 2 9460 0502 http://www.witango.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, 18 October 2006 10:32 PM To: [EMAIL PROTECTED] Subject: Re: Hello from Europe - I have a Order... Sophie, in others words: I'm not able to order the upgrade with a discount for the reseller ? Regards Daniel - Original Message - From: Sophie Wade To: '[EMAIL PROTECTED]' Sent: Wednesday, October 18, 2006 1:53 PM Subject: RE: Hello from Europe - I have a Order... Daniel We have not ‘dropped’ the distribution agreements, they have all expired and we have chosen not to renew them. We do not have distributors any more. Regards Sophie Wade Witango Technologies Pty Ltd 44 Miller St, North Sydney NSW, 2060, Australia phone: +61 2 9460 0500 fax: +61 2 9460 0502 http://www.witango.com They have kill the market and the product by himself. R.I.P Daniel Richardy - Original Message - From: Anthony M. Humphreys To: witango-talk@witango.com Sent: Sunday, October 19, 2008 5:13 AM Subject: Witango-Talk: Non-notable product Deleted from Wiki because it's been deemed to have become a non-notable product. Ouch. http://en.wikipedia.org/wiki/Witango TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Witango-Talk: Non-notable product
Deleted from Wiki because it's been deemed to have become a non-notable product. Ouch. http://en.wikipedia.org/wiki/Witango TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
Re: Witango-Talk: error on install - How to fix for Mac OS X, INTEL
So lipo doesn't help? It changes the Apache executable so that it'll allow a 32bit module (which Witango is) to run... On [Oct 18 -2008 ], at 7:15 PM, Jon van der Raadt wrote: Graham, Thanks for this excellent summary but it appears as if the Apache 2 plugin is what is the wrong architecture (perhaps intel when I need ppc)... Jon On Oct 18, 2008, at 1:20 PM, Graham Dale wrote: You need to "lipo" Apache, etc. Here are instructions (again) ... Note that this works for both Server and Client, but the absolute addresses given here are for CLIENT. You need to ensure that you are using the right addresses for SERVER. WitangoServer for Intel Macs requires Apache 2.2+, but Leopard uses Apache 2.2.6+ and that version does not support the Witango module, which is designed for earlier versions of 2.2. Furthermore, I couldn't get earlier 2.2 versions of Apache to run on Leopard. (Stole some ideas from http://www.fatcatsoftware.com/blog/2007/running-fogbugz-on-leopard and then modified as needed for Witango) The problem was that I was getting a "module" error, and an indication that it needed to be re-worked - apparently for 64- bit. ... this method strips 64-bit-ness from Apache 2.2.6 1] Workaround for 64 bit ***server note: be sure that httpd is IN / usr/sbin - might have a different location *** cd /usr/sbin sudo cp httpd httpd-fat<=== (creates httpd backup) sudo lipo httpd -thin i386 -output httpd Quote from website above: "After making a backup of the httpd executable for safety purposes, the lipo commands sucks out all of the architectures included in the universal binary except the 32-bit Intel one (specified by “i386″). Apache can’t run as 64-bit if it doesn’t have a 64- bit binary!" Note from DEG: I presume this would also (??) work for PPC machines, but a different code (possibly PPC or ppc) would need to be substituted for the i386 in the "lipo" command above. 2] Install Create the witango user Then install WitangoServer. Get usual install error (caused by Apache in wrong location ... see below) 3] Workaround for non-standard location of Apache in Leopard (/etc/ apache2) *** Fix as needed for server *** In Terminal --> sudo cp /Applications/WitangoServer/5.5/install/Plug-Ins/ mod_witango55_apache22.so /usr/libexec/apache2/ mod_witango55_apache22.so (copies module to the right place for Apache2 to see it) note, no line break should be in the line above, even if there appears to be one after going through email Create backup of /etc/apache2/httpd.conf cd /etc/apache2 sudo cp httpd.conf httpd-back.conf cp httpd.conf /Users//httpd.conf <=== I prefer editing outside of the /etc directory. This is the copy I can fool with Edit httpd.conf, adding THIS edited information instead of the provided mod_witango55_apache22.so.httpd (to account for new location for modules) I just added this as the last part of the httpd.conf file # LOAD WITANGO MODULE # This loads the Witango 5.5 client for Apache 2.2 to enable # communication with the Witango Application Server LoadModule WitangoModule libexec/apache2/mod_witango55_apache22.so WitangoModule mod_witango55_apache22.so AddType application/witango-application-file taf tml thtml tcf wws If you wish, change httpd.conf for location of web pages. In my case I just deleted the Library/WebServer directory and aliased in my working one, which is on an entirely different partition. sudo cp /Users//httpd.conf /etc/apache2/ httpd.conf <=== Returns the edited copy to /etc/apache2 BTW, copy over old WitangoServer/5.5/configuration files from Tiger config for WitangoServer, for quickest switchover. 4] Workaround for starting up WitangoServer due to incomplete installer script --- Witango startup unlikely to work, so I didn't bother with that (I am on a development server, so I am not concerned with automatic startups) However, we now use a script startup for our servers to ensure automatic startups. Let us know if you need that ... In Terminal ---> cd /Applications/WitangoServer/5.5 ./witangod -uo 5] If you get an error message for clients.ini Change permissions (and path to permissions) so that these are wide open (because I wasn't sure who the "owner" was for the http process - system? wheel? root?) This is NOT the best solution, but it was good for checking that there was ANY situation in which I could start up. The more experienced among you can tackle that. Start up Apache webserver using Preferences --> Sharing ---> Web sharing. If you had already started it, shut it down, restart. Start up WitangoServer as indicated above. (Note that if this start up of the Web sharing process "hangs", it means that you've done something wrong with the httpd.conf file - check the console application to find out
Re: Witango-Talk: error on install - How to fix for Mac OS X, INTEL
Graham, Thanks for this excellent summary but it appears as if the Apache 2 plugin is what is the wrong architecture (perhaps intel when I need ppc)... Jon On Oct 18, 2008, at 1:20 PM, Graham Dale wrote: You need to "lipo" Apache, etc. Here are instructions (again) ... Note that this works for both Server and Client, but the absolute addresses given here are for CLIENT. You need to ensure that you are using the right addresses for SERVER. WitangoServer for Intel Macs requires Apache 2.2+, but Leopard uses Apache 2.2.6+ and that version does not support the Witango module, which is designed for earlier versions of 2.2. Furthermore, I couldn't get earlier 2.2 versions of Apache to run on Leopard. (Stole some ideas from http://www.fatcatsoftware.com/blog/2007/running-fogbugz-on-leopard and then modified as needed for Witango) The problem was that I was getting a "module" error, and an indication that it needed to be re-worked - apparently for 64- bit. ... this method strips 64-bit-ness from Apache 2.2.6 1] Workaround for 64 bit ***server note: be sure that httpd is IN / usr/sbin - might have a different location *** cd /usr/sbin sudo cp httpd httpd-fat<=== (creates httpd backup) sudo lipo httpd -thin i386 -output httpd Quote from website above: "After making a backup of the httpd executable for safety purposes, the lipo commands sucks out all of the architectures included in the universal binary except the 32-bit Intel one (specified by “i386″). Apache can’t run as 64-bit if it doesn’t have a 64- bit binary!" Note from DEG: I presume this would also (??) work for PPC machines, but a different code (possibly PPC or ppc) would need to be substituted for the i386 in the "lipo" command above. 2] Install Create the witango user Then install WitangoServer. Get usual install error (caused by Apache in wrong location ... see below) 3] Workaround for non-standard location of Apache in Leopard (/etc/ apache2) *** Fix as needed for server *** In Terminal --> sudo cp /Applications/WitangoServer/5.5/install/Plug-Ins/ mod_witango55_apache22.so /usr/libexec/apache2/ mod_witango55_apache22.so (copies module to the right place for Apache2 to see it) note, no line break should be in the line above, even if there appears to be one after going through email Create backup of /etc/apache2/httpd.conf cd /etc/apache2 sudo cp httpd.conf httpd-back.conf cp httpd.conf /Users//httpd.conf <=== I prefer editing outside of the /etc directory. This is the copy I can fool with Edit httpd.conf, adding THIS edited information instead of the provided mod_witango55_apache22.so.httpd (to account for new location for modules) I just added this as the last part of the httpd.conf file # LOAD WITANGO MODULE # This loads the Witango 5.5 client for Apache 2.2 to enable # communication with the Witango Application Server LoadModule WitangoModule libexec/apache2/mod_witango55_apache22.so WitangoModule mod_witango55_apache22.so AddType application/witango-application-file taf tml thtml tcf wws If you wish, change httpd.conf for location of web pages. In my case I just deleted the Library/WebServer directory and aliased in my working one, which is on an entirely different partition. sudo cp /Users//httpd.conf /etc/apache2/ httpd.conf <=== Returns the edited copy to /etc/apache2 BTW, copy over old WitangoServer/5.5/configuration files from Tiger config for WitangoServer, for quickest switchover. 4] Workaround for starting up WitangoServer due to incomplete installer script --- Witango startup unlikely to work, so I didn't bother with that (I am on a development server, so I am not concerned with automatic startups) However, we now use a script startup for our servers to ensure automatic startups. Let us know if you need that ... In Terminal ---> cd /Applications/WitangoServer/5.5 ./witangod -uo 5] If you get an error message for clients.ini Change permissions (and path to permissions) so that these are wide open (because I wasn't sure who the "owner" was for the http process - system? wheel? root?) This is NOT the best solution, but it was good for checking that there was ANY situation in which I could start up. The more experienced among you can tackle that. Start up Apache webserver using Preferences --> Sharing ---> Web sharing. If you had already started it, shut it down, restart. Start up WitangoServer as indicated above. (Note that if this start up of the Web sharing process "hangs", it means that you've done something wrong with the httpd.conf file - check the console application to find out where the problem was.) This looks complicated, but it took far longer for me to tweak around and test at each point get it running. If you follow this (AND if I didn't leave s
Re: Witango-Talk: error on install - How to fix for Mac OS X, INTEL
You need to "lipo" Apache, etc. Here are instructions (again) ... Note that this works for both Server and Client, but the absolute addresses given here are for CLIENT. You need to ensure that you are using the right addresses for SERVER. WitangoServer for Intel Macs requires Apache 2.2+, but Leopard uses Apache 2.2.6+ and that version does not support the Witango module, which is designed for earlier versions of 2.2. Furthermore, I couldn't get earlier 2.2 versions of Apache to run on Leopard. (Stole some ideas from http://www.fatcatsoftware.com/blog/2007/running-fogbugz-on-leopard and then modified as needed for Witango) The problem was that I was getting a "module" error, and an indication that it needed to be re-worked - apparently for 64-bit. ... this method strips 64-bit-ness from Apache 2.2.6 1] Workaround for 64 bit ***server note: be sure that httpd is IN / usr/sbin - might have a different location *** cd /usr/sbin sudo cp httpd httpd-fat<=== (creates httpd backup) sudo lipo httpd -thin i386 -output httpd Quote from website above: "After making a backup of the httpd executable for safety purposes, the lipo commands sucks out all of the architectures included in the universal binary except the 32-bit Intel one (specified by “i386″). Apache can’t run as 64-bit if it doesn’t have a 64-bit binary!" Note from DEG: I presume this would also (??) work for PPC machines, but a different code (possibly PPC or ppc) would need to be substituted for the i386 in the "lipo" command above. 2] Install Create the witango user Then install WitangoServer. Get usual install error (caused by Apache in wrong location ... see below) 3] Workaround for non-standard location of Apache in Leopard (/etc/ apache2) *** Fix as needed for server *** In Terminal --> sudo cp /Applications/WitangoServer/5.5/install/Plug-Ins/ mod_witango55_apache22.so /usr/libexec/apache2/ mod_witango55_apache22.so (copies module to the right place for Apache2 to see it) note, no line break should be in the line above, even if there appears to be one after going through email Create backup of /etc/apache2/httpd.conf cd /etc/apache2 sudo cp httpd.conf httpd-back.conf cp httpd.conf /Users//httpd.conf <=== I prefer editing outside of the /etc directory. This is the copy I can fool with Edit httpd.conf, adding THIS edited information instead of the provided mod_witango55_apache22.so.httpd (to account for new location for modules) I just added this as the last part of the httpd.conf file # LOAD WITANGO MODULE # This loads the Witango 5.5 client for Apache 2.2 to enable # communication with the Witango Application Server LoadModule WitangoModule libexec/apache2/mod_witango55_apache22.so WitangoModule mod_witango55_apache22.so AddType application/witango-application-file taf tml thtml tcf wws If you wish, change httpd.conf for location of web pages. In my case I just deleted the Library/WebServer directory and aliased in my working one, which is on an entirely different partition. sudo cp /Users//httpd.conf /etc/apache2/httpd.conf <=== Returns the edited copy to /etc/apache2 BTW, copy over old WitangoServer/5.5/configuration files from Tiger config for WitangoServer, for quickest switchover. 4] Workaround for starting up WitangoServer due to incomplete installer script --- Witango startup unlikely to work, so I didn't bother with that (I am on a development server, so I am not concerned with automatic startups) However, we now use a script startup for our servers to ensure automatic startups. Let us know if you need that ... In Terminal ---> cd /Applications/WitangoServer/5.5 ./witangod -uo 5] If you get an error message for clients.ini Change permissions (and path to permissions) so that these are wide open (because I wasn't sure who the "owner" was for the http process - system? wheel? root?) This is NOT the best solution, but it was good for checking that there was ANY situation in which I could start up. The more experienced among you can tackle that. Start up Apache webserver using Preferences --> Sharing ---> Web sharing. If you had already started it, shut it down, restart. Start up WitangoServer as indicated above. (Note that if this start up of the Web sharing process "hangs", it means that you've done something wrong with the httpd.conf file - check the console application to find out where the problem was.) This looks complicated, but it took far longer for me to tweak around and test at each point get it running. If you follow this (AND if I didn't leave some critical bit out), it should take you less than 5 minutes to get the Witango Server running. and, lastly, be sure to put your JDBC drivers here, if you're running JDBC. Library/Java/Extensions On [Oct 1
Witango-Talk: error on install
Has someone seen this problem? Is there a fix? Witango 5.509 Apache 2.2.8 Max OSX Server 10.5.5 10/5/08 5:31:35 PM org.apache.httpd[973] httpd: Syntax error on line 1459 of /private/etc/apache2/httpd.conf: Cannot load /usr/libexec/ apache2/mod_witango55_apache2.so into server: dlopen(/usr/libexec/ apache2/mod_witango55_apache2.so, 10): no suitable image found. Did find:\n\t/usr/libexec/apache2/mod_witango55_apache2.so: mach-o, but wrong architecture Thanks in advance TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
