Changes for page WO 5.4 Getting Started
Last modified by D Tim Cummings on 2013/06/14 16:27
From version 31.1
edited by David Holt
on 2008/10/29 12:31
on 2008/10/29 12:31
Change comment:
There is no comment for this version
To version 30.1
edited by Timothy Worman
on 2013/05/01 19:19
on 2013/05/01 19:19
Change comment:
Migrated to Confluence 4.0
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dholt1 +XWiki.tworman - Content
-
... ... @@ -1,92 +1,66 @@ 1 -{{toc}}{{/toc}} 1 +{{warning}} 2 +This is deprecated information! 3 +{{/warning}} 2 2 3 - = Installing WebObjectsand WOLips=5 +{{toc maxLevel="1"/}} 4 4 5 - DownloadXcode 3 from [[ADC>>http://developer.apple.com/leopard/devcenter/]], the WebObjects frameworks areincludedin this package. You will have to make a custom install andselect //WebObjects// in the package list since WebObjects is not part of thedefaultinstallation.7 += ProjectBuilder and XCode = 6 6 7 - Install[[Eclipse3.3.2>>http://download.eclipse.org/eclipse/downloads/drops/R-3.3.2-200802211800/index.php]]9 +ProjectBuilder and Xcode are no longer supported IDEs for WebObjects development or deployment. While legacy projects may still use it there is little, if any, support available for it. Existing projects (except Objective-C WebObjects projects, of course) should be [[migrated to WOLips>>doc:WOL.XcodeMigration]]. It isn't as hard as you might think, and WOLips is a much more powerful WebObjects IDE. 8 8 9 - [[Install>>WOL:Install WOLips with Eclipse Update Manager]]WOLips from the[[stable>>http://webobjects.mdimension.com/wolips/stable]]build server. ([[nightly>>http://webobjects.mdimension.com/wolips/nightly]]only works with Eclipse3.4, not recommended yet).11 += Installing WebObjects and WOLips = 10 10 11 -Start Eclipse and switch to the WOLips perspective. To achieve this, open the //Window// menu, select //Open Perspective// and select //Other...//. 13 +1. ((( 14 +====== Download Golipse ====== 12 12 13 -[[image:PerpectiveMenu.png]] 16 +[[Golipse>>url:http://wocommunity.org/documents/tools/Golipse.app_build_14.zip||shape="rect"]]Â ([[source>>url:https://github.com/wocommunity/Golipse||shape="rect"]]) will fetch the needed version of Eclipse, WOLips and other tools for WebObjects development. 17 +))) 14 14 15 -In the perspective choices, select //WOLips// and click //Ok//. 19 +{{note title="32-bit computers"}} 20 +By default Golipse will download and install a 64-bit version of Eclipse. If you have an older 32-bit machine you can specify the download URL for the Eclipse package in 'Golipse > Preferences'. The latest 32-bit package is "http:~/~/ftp.osuosl.org/pub/eclipse/eclipse/downloads/drops/R-3.6.2-201102101200/eclipse-SDK-3.6.2-macosx-cocoa.tar.gz" 21 +{{/note}} 16 16 17 -[[image:PerspectiveChoices.png]] 23 +1. ((( 24 +====== Install the WebObjects ====== 18 18 19 -If you don't switch to the WOLips perspective, you won't be able to create new WebObjects projects. 26 +The best way to install the WebObjects frameworks is according to [[these instructions>>doc:WOL.Using WOLips With Multiple Versions of WebObjects]]. 27 +))) 28 +1. ((( 29 +====== Start Eclipse and switch to the WOLips perspective. ====== 20 20 21 -You are now ready to create projects or importing the examples. 31 +* Under the //Window// menu, select //Open Perspective > Other...//. 32 +[[image:attach:PerpectiveMenu.png]] 33 +* 22 22 23 -= Running theexamples =35 +====== Select //WOLips// and click //Ok//. ====== 24 24 25 - Apple has convertedtheirWebObjectsexamples in the Eclipse format, but no documentation is provided onhow toimport them into Eclipse. The examples are in///Developer/Examples/JavaWebObjects//.37 +[[image:attach:PerspectiveChoices.png]] 26 26 27 -The first step is: install Eclipse and WOLips :-) 39 +{{note title="WOLips Perspective"}} 40 +If you don't switch to the WOLips perspective, you won't be able to create new WebObjects projects. 41 +{{/note}} 42 +))) 28 28 29 -Some examples needs Derby, an embedded Java database (OpenBase is not included with WO anymore). To install the databases, you have to do: 44 +{{info title="Xcode & WebObjects"}} 45 +Xcode is no longer the supported IDE for WebObjects development or deployment. However, downloading it and installing it will install tools debugging tools that you might find useful. 30 30 31 -{{code}} 47 +* Apple Developer Site (Free): [[http:~~/~~/developer.apple.com/xcode/>>url:http://developer.apple.com/xcode/||shape="rect"]] 48 +* Mac OS X App Store (Free): [[http:~~/~~/itunes.apple.com/us/app/xcode/id448457090>>url:http://itunes.apple.com/us/app/xcode/id448457090||shape="rect"]] 49 +{{/info}} 32 32 33 -cd /Developer/Examples/JavaWebObjects/ 34 -sudo sh installDatabases.sh <yourusername> 35 35 36 -{{/code}} 37 37 38 - Now,you canimport theexamples intoEclipse. Start Eclipse, select //File// > //Import//,53 +{{id name="javamonitor"/}} 39 39 40 - [[image:ImportMenu.png]]55 += Running Monitor and wotaskd on Mac OS X = 41 41 42 -and sele ct//General//>//ExistingProjects//intoWorkplace.57 +Monitor and wotaskd are installed, but the launchd scripts to start them are not installed. You can grab them from a 10.5 Server installation, or follow those instructions. 43 43 44 -[[image:ImportGeneral.png]] 45 - 46 -On the next page, select //Select root directory// and browse your disk to ///Developer/Examples/JavaWebObjects//. You should see a list of projects to import. Deselect the second //javaeoutil// project, or else you won't be able to import the projects. 47 - 48 -[[image:ImportProjectsList.png]] 49 - 50 -After the importation is done, you should see the projects in the WO Package Explorer. If you see the projects in Package Explorer (without "WO" in the name), that means that you are using the Java perpective instead of the WOLips perpective. Switch the perpective to WOLips. 51 - 52 -[[image:PackageExplorer.png]] 53 - 54 -Now, you need to fix the examples, because the build path is pointing to the source projects of the WO frameworks, source that nobody outside Apple has access to :-)For each project, right-click on each project, select //Build Path// > //Configure Build Path...// 55 - 56 -[[image:BuildPathMenu.png]] 57 - 58 -Click on the //Projects// tab, select the references to the WO frameworks that have the Warning icon and click //Remove//. 59 - 60 -[[image:ConfigureBuildPath.png]] 61 - 62 -Click on the //Libraries// tab, click the //Add Library// button. Select //WebObjects Frameworks// and click //Next//. 63 - 64 -[[image:AddLibrary.png]] 65 - 66 -Click //System//, open the triangle next to //System// and make sure that //JavaEOAccess//, //JavaEOControl//, //JavaFoundation//, //JavaWebObjects//, //JavaWOExtensions// and //JavaXML// are selected. For //SchoolToolsClient//, you also need to add //JavaWebServicesSupport// and //JavaWebServicesClient// to the build path. For the //SchoolToolsServer//, you need to add //JavaWebServicesSupport//. 67 - 68 -[[image:WOSystemLibs.png]] 69 - 70 - 71 -After you corrected the build path on a project, the project will rebuild itself and the errors shoud dissapear. 72 - 73 -//JavaBusinessLogic// and //RelatedLinks// requires Apache Derby, but the path to Derby's JAR is wrong. Remove the JAR from the build path, click //Add External JARs...//, browse your disk up to ///Developer/Examples/JavaWebObjects/Databases/db-derby-10.2.2.0-bin/lib// and select //derby.jar//. The build path should look like this: 74 - 75 -[[image:GoodDerbyPath.png]] 76 - 77 -VoilĂ You finally can run the examples. 78 - 79 -{{id value="javamonitor"}}{{/id}} 80 - 81 -= Running Monitor and wotaskd on Mac OS X 10.5 "client" = 82 - 83 -Monitor and wotaskd are installed, but the launchd scripts to start them are not installed. You can grab them from a 10.5 Server installation, or follow those instructions. 84 - 85 85 Make sure //Web Sharing// is enabled in the //Sharing// panel in //System Preferences// (note: 10.5 comes with Apache 2.2 as the default). 86 86 87 87 Edit ///etc/apache2/httpd.conf// (if you did a fresh install, you may already have these - search httpd.conf first) 88 88 89 -Search for rewrite //module, and above it, add this line~://63 +Search for rewrite_module, and above it, add this line: 90 90 91 91 {{code}} 92 92 ... ... @@ -123,10 +123,10 @@ 123 123 124 124 {{/code}} 125 125 126 -If you run //ps auxw grep httpd// you should see apache now running 100 +If you run //ps auxw | grep httpd// you should see apache now running 127 127 128 128 Create ///Library/LaunchDaemons/com.apple.webobjects.wotaskd.plist// with: 129 -(for OSX 10.5 make sure the permissions of this file are 644 system/wheel/everyone otherwise launchctl will throw a "dubious permissions" error when you try to load the plist with the commands that follow) 103 + (for OSX 10.5 make sure the permissions of this file are 644 system/wheel/everyone otherwise launchctl will throw a "dubious permissions" error when you try to load the plist with the commands that follow) 130 130 131 131 {{code}} 132 132 ... ... @@ -160,7 +160,7 @@ 160 160 {{/code}} 161 161 162 162 Create ///Library/LaunchDaemons/com.apple.webobjects.womonitor.plist// with: 163 -(for OSX 10.5 make sure the permissions of this file are 644 system/wheel/everyone otherwise launchctl will throw a "dubious permissions" error when you try to load the plist with the commands that follow) 137 + (for OSX 10.5 make sure the permissions of this file are 644 system/wheel/everyone otherwise launchctl will throw a "dubious permissions" error when you try to load the plist with the commands that follow) 164 164 165 165 {{code}} 166 166 ... ... @@ -194,7 +194,7 @@ 194 194 {{/code}} 195 195 196 196 Start the launchd daemons : 197 -(you may need to sudo here) 171 + (you may need to sudo here) 198 198 199 199 {{code}} 200 200 ... ... @@ -203,7 +203,7 @@ 203 203 204 204 {{/code}} 205 205 206 -If you run "ps auxw grep java" you should see wotaskd and java monitor now running. 180 +If you run "ps auxw | grep java" you should see wotaskd and java monitor now running. You should be able to connect to Monitor by this URL: 207 207 208 208 {{code}} 209 209 ... ... @@ -210,119 +210,3 @@ 210 210 http://localhost:56789 211 211 212 212 {{/code}} 213 - 214 -= Developing with both WebObjects 5.4 and 5.3 = 215 - 216 -(Mike Schrag) 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): 217 - 218 -Make a ///System/Library/Frameworks/WebObjects54// folder, and move the following frameworks from the 5.4 install into it: 219 - 220 -{{code}} 221 - 222 -JavaDTWGeneration.framework 223 -JavaDirectToWeb.framework 224 -JavaEOAccess.framework 225 -JavaEOApplication.framework 226 -JavaEOControl.framework 227 -JavaEODistribution.framework 228 -JavaEOGeneration.framework 229 -JavaEOInterface.framework 230 -JavaEOInterfaceCocoa.framework 231 -JavaEOInterfaceSwing.framework 232 -JavaEOProject.framework 233 -JavaEORuleSystem.framework 234 -JavaEOTool.framework 235 -JavaFoundation.framework 236 -JavaJDBCAdaptor.framework 237 -JavaJNDIAdaptor.framework 238 -JavaWOExtensions.framework 239 -JavaWOJSPServlet.framework 240 -JavaWebObjects.framework 241 -JavaWebServicesClient.framework 242 -JavaWebServicesGeneration.framework 243 -JavaWebServicesSupport.framework 244 -JavaXML.framework 245 - 246 -{{/code}} 247 - 248 -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) 249 - 250 -{{code}} 251 - 252 -JavaDTWGeneration.framework 253 -JavaDirectToWeb.framework 254 -JavaEOAccess.framework 255 -JavaEOApplication.framework 256 -JavaEOCocoa.framework 257 -JavaEOControl.framework 258 -JavaEODistribution.framework 259 -JavaEOGeneration.framework 260 -JavaEOInterface.framework 261 -JavaEOInterfaceCocoa.framework 262 -JavaEOInterfaceSwing.framework 263 -JavaEOProject.framework 264 -JavaEORuleSystem.framework 265 -JavaEOTool.framework 266 -JavaFoundation.framework 267 -JavaJDBCAdaptor.framework 268 -JavaJNDIAdaptor.framework 269 -JavaWOExtensions.framework 270 -JavaWOJSPServlet.framework 271 -JavaWebObjects.framework 272 -JavaWebServicesClient.framework 273 -JavaWebServicesGeneration.framework 274 -JavaWebServicesSupport.framework 275 -JavaXML.framework 276 - 277 -{{/code}} 278 - 279 -I then use the following two scripts to be able to switch between using 5.3 and 5.4 system wide: 280 - 281 -{{code}} 282 - 283 -bash-3.2# cat wo53 284 -for framework in `ls /System/Library/Frameworks/WebObjects53`; do rm /System/Library/Frameworks/$framework; \ 285 -ln -sf /System/Library/Frameworks/WebObjects53/$framework /System/Library/Frameworks/$framework; done 286 -bash-3.2# cat wo54 287 -for framework in `ls /System/Library/Frameworks/WebObjects54`; do rm /System/Library/Frameworks/$framework; \ 288 -ln -sf /System/Library/Frameworks/WebObjects54/$framework /System/Library/Frameworks/$framework; done 289 - 290 -{{/code}} 291 - 292 -At this point, you should have NO WO frameworks in /System/Library/Frameworks they should be in subfolders. 293 - 294 -Now go ahead and run wo53, which should now give you WO 5.3 framework symlinks. 295 - 296 -You may need to do a clean build of your projects in Eclipse If things are setup properly, you should not get any Java errors you didn't already have. 297 - 298 -== Alternative 5.3 / 5.4 development method == 299 - 300 -The [[^woswitch]] script can be used as an alternative method to installing and using WO 5.3 for development, without the need to touch or move any of the installed WO 5.4 frameworks. This script will download and install the WebObjects 5.3.3 runtime into /Developer/WebObjects53 and maintain two copies of your ,,/Library/wobuild.properties so you can quickly switch WOLips development between the two different runtime versions.,, 301 - 302 -To use the script for the first time, ensure that you have WebObjects 5.4 installed, and have run WOLips at least once to create your ,,/Library/wobuild.properties file. Also ensure that the script has been set executable with ##chmod __x woswitch__##,, 303 - 304 -Then run it like this: 305 - 306 -{{noformat}} 307 - 308 -# ./woswitch.sh 53 309 - 310 -{{/noformat}} 311 - 312 -This can take quite some time the first time as it downloads, extracts and sets the WO 5.3 runtime up. After this is done, switching between the two runtimes is almost instant. 313 - 314 -To switch between the two runtimes, quit WOLips and run 315 - 316 -{{noformat}} 317 - 318 -# ./woswitch.sh 54 319 -or 320 -# ./woswitch.sh 53 321 - 322 -{{/noformat}} 323 - 324 -Then run WOLips again. 325 - 326 -One thing to remember is that when you are installing frameworks they need to be installed into the appropriate location for the runtime you are targeting. For WO 5.4 you need to install them into ##/Library/WebObjects/Frameworks## and for WO 5.3 they need to go into ##/Developer/WebObjects53/Library/Frameworks##. 327 - 328 -Keep in mind that these changes are specific to WOLips and woproject only. If you run anything outside of WOLips you will also need to manually set ##NEXT//ROOT//##// appropriately.//