Changes for page WO 5.4 Getting Started

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.probert
	1	+XWiki.timcu

Content

...	...	@@ -1,83 +1,42 @@
1		-{{toc}}{{/toc}}
	1	+{{toc maxLevel="1"}}{{/toc}}
2	2
3		-= Installing WebObjects and WOLips =
	3	+= ProjectBuilder and XCode =
4	4
5		-Download Xcode 3 from [[ADC>>http://developer.apple.com/leopard/devcenter/]], the WebObjects frameworks are included in this package. You will have to make a custom install and select //WebObjects// in the package list since WebObjects is not part of the default installation.
	5	+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>>WOL:XcodeMigration]]. It isn't as hard as you might think, and WOLips is a much more powerful WebObjects IDE.
6	6
7		-Install [[Eclipse 3.3.1.1>>http://www.eclipse.org/downloads/download.php?file=//eclipse/downloads/drops/R-3.3.1.1-200710231652/eclipse-SDK-3.3.1.1-macosx-carbon.tar.gz]] (yes that's an extra .1) which fixes the permgen space bug from 3.3.1
	7	+= Installing WebObjects and WOLips =
8	8
9		-[[Install>>WOL:Install WOLips with Eclipse Update Manager]] WOLips from the [[nightly>>http://webobjects.mdimension.com/wolips/nightly]] build server
	9	+1. h6. Download Golipse
	10	+[[Golipse>>https://github.com/downloads/rebeld/Golipse/Golipse.app_build_13.zip]] ([[source>>https://github.com/rebeld/Golipse]]) will fetch the needed version of Eclipse, WOLips and other tools for WebObjects development.
10	10
11		-Start Eclipse and switch to the WOLips perspective. To achieve this, open the //Window// menu, select //Open Perspective// and select //Other...//.
	12	+{{note title="32-bit computers"}}
	13	+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"
	14	+{{/note}}
12	12
	16	+1. h6. Install the WebObjects
	17	+The best way to install the WebObjects frameworks is according to [[these instructions>>WOL:Using WOLips With Multiple Versions of WebObjects]].
	18	+1. h6. Start Eclipse and switch to the WOLips perspective.
	19	+1*. Under the //Window// menu, select //Open Perspective > Other...//.
13	13	[[image:PerpectiveMenu.png]]
14		-
15		-In the perspective choices, select //WOLips// and click //Ok//.
16		-
	21	+1*. h6. Select //WOLips// and click //Ok//.
17	17	[[image:PerspectiveChoices.png]]
18	18
	24	+{{note title="WOLips Perspective"}}
19	19	If you don't switch to the WOLips perspective, you won't be able to create new WebObjects projects.
	26	+{{/note}}
20	20
21		-You are now ready to create projects or importing the examples. 
	28	+{{info title="Xcode & WebObjects"}}
22	22
23		-= Running the examples =
	30	+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.
	31	+* Apple Developer Site (Free): [http://developer.apple.com/xcode/]
	32	+* Mac OS X App Store (Free): [http://itunes.apple.com/us/app/xcode/id448457090]
24	24
25		-Apple has converted their WebObjects examples in the Eclipse format, but no documentation is provided on how to import them into Eclipse.  The examples are in ///Developer/Examples/JavaWebObjects//.
	34	+{{/info}}
26	26
27		-The first step is: install Eclipse and WOLips :-)  
	36	+{{id value="javamonitor"}}{{/id}}
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:
	38	+= Running Monitor and wotaskd on Mac OS X =
30	30
31		-{{code}}
32		-
33		-cd /Developer/Examples/JavaWebObjects/
34		-sudo sh installDatabases.sh <yourusername>
35		-
36		-{{/code}}
37		-
38		-Now, you can import the examples into Eclipse. Start Eclipse, select //File// > //Import//,
39		-
40		-[[image:ImportMenu.png]]
41		-
42		-and select //General// > //Existing Projects// into Workplace.
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.&nbsp; 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.&nbsp; 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.&nbsp; 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		-&nbsp;
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//.&nbsp; The build path should look like this:
74		-
75		-[[image:GoodDerbyPath.png]]
76		-
77		-Voilà&nbsp; You finally can run the examples.&nbsp;
78		-
79		-= Running Monitor and wotaskd on Mac OS X 10.5 "client" =
80		-
81	81	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.
82	82
83	83	Make sure //Web Sharing// is enabled in the //Sharing// panel in //System Preferences// (note: 10.5 comes with Apache 2.2 as the default).
...	...	@@ -124,6 +124,7 @@
124	124	If you run //ps auxw grep httpd// you should see apache now running
125	125
126	126	Create ///Library/LaunchDaemons/com.apple.webobjects.wotaskd.plist// with:
	86	+(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)
127	127
128	128	{{code}}
129	129
...	...	@@ -157,6 +157,7 @@
157	157	{{/code}}
158	158
159	159	Create ///Library/LaunchDaemons/com.apple.webobjects.womonitor.plist// with:
	120	+(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)
160	160
161	161	{{code}}
162	162
...	...	@@ -190,6 +190,7 @@
190	190	{{/code}}
191	191
192	192	Start the launchd daemons :
	154	+(you may need to sudo here)
193	193
194	194	{{code}}
195	195
...	...	@@ -205,85 +205,3 @@
205	205	http://localhost:56789
206	206
207	207	{{/code}}
208		-
209		-= Developing with both WebObjects 5.4 and 5.3 =
210		-
211		-(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):
212		-
213		-Make a ///System/Library/Frameworks/WebObjects54// folder, and move the following frameworks from the 5.4 install into it:
214		-
215		-{{code}}
216		-
217		-JavaDTWGeneration.framework
218		-JavaDirectToWeb.framework
219		-JavaEOAccess.framework
220		-JavaEOApplication.framework
221		-JavaEOControl.framework
222		-JavaEODistribution.framework
223		-JavaEOGeneration.framework
224		-JavaEOInterface.framework
225		-JavaEOInterfaceCocoa.framework
226		-JavaEOInterfaceSwing.framework
227		-JavaEOProject.framework
228		-JavaEORuleSystem.framework
229		-JavaEOTool.framework
230		-JavaFoundation.framework
231		-JavaJDBCAdaptor.framework
232		-JavaJNDIAdaptor.framework
233		-JavaWOExtensions.framework
234		-JavaWOJSPServlet.framework
235		-JavaWebObjects.framework
236		-JavaWebServicesClient.framework
237		-JavaWebServicesGeneration.framework
238		-JavaWebServicesSupport.framework
239		-JavaXML.framework
240		-
241		-{{/code}}
242		-
243		-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)
244		-
245		-{{code}}
246		-
247		-JavaDTWGeneration.framework
248		-JavaDirectToWeb.framework
249		-JavaEOAccess.framework
250		-JavaEOApplication.framework
251		-JavaEOCocoa.framework
252		-JavaEOControl.framework
253		-JavaEODistribution.framework
254		-JavaEOGeneration.framework
255		-JavaEOInterface.framework
256		-JavaEOInterfaceCocoa.framework
257		-JavaEOInterfaceSwing.framework
258		-JavaEOProject.framework
259		-JavaEORuleSystem.framework
260		-JavaEOTool.framework
261		-JavaFoundation.framework
262		-JavaJDBCAdaptor.framework
263		-JavaJNDIAdaptor.framework
264		-JavaWOExtensions.framework
265		-JavaWOJSPServlet.framework
266		-JavaWebObjects.framework
267		-JavaWebServicesClient.framework
268		-JavaWebServicesGeneration.framework
269		-JavaWebServicesSupport.framework
270		-JavaXML.framework
271		-
272		-{{/code}}
273		-
274		-I then use the following two scripts to be able to switch between using 5.3 and 5.4 system wide:
275		-
276		-{{code}}
277		-
278		-bash-3.2# cat wo53
279		-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
280		-bash-3.2# cat wo54
281		-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
282		-
283		-{{/code}}
284		-
285		-At this point, you should have NO WO frameworks in /System/Library/Frameworks they should be in subfolders.
286		-
287		-Now go ahead and run wo53, which should now give you WO 5.3 framework symlinks.
288		-
289		-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.