Skip to Content

Changes for page Overview

Last modified by Pascal Robert on 2012/12/05 12:01
From version 21.1
edited by David Avendasora
on 2010/11/30 06:48
Change comment: There is no comment for this version
To version 22.1
edited by smmccraw
on 2007/07/08 09:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Overview
1 +Programming__WebObjects-Web Applications-Deployment-Overview
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.smmccraw
Content
... ... @@ -1,7 +5,3 @@
1 -//(Note that this content is from 2007 and may no longer be correct or necessary. See links below and use the site search for finding info on deployment issues.)//
2 -
3 -//(Note that the following links to the most up to date Mac Deployment information - [[Deploying on Mac OS X Server]])//
4 -
5 5  Xcode expects to take a given set of files, as listed in your Groups & Files pane and from them build a finished product or set of products such as an application, a framework, a library or a command line tool.
6 6  
7 7  It's worth noting here that the items represented in this pane are of four types: files, directories, packages and groups. Files are just that, files of various types with extensions indicating the type, such as .java, .jpg, .gif, .html. Directories represent real directories somewhere in your file system and are represented with a blue folder icon. Package is a Mac OX X term for a directory of files and subdirectories that are to be recognized as a unit both by the Finder and by Xcode. They are often represented with an icon that is indistinguishable from a file icon. If Xcode isn't familiar with the kind of package represented, it displays them as blue folders. Groups are the strange items in this categorization and are pictured as yellow folders. THEY DON'T EXIST AT ALL in the file system. They are purely organizing entities for your use in Xcode. You can group files together in an Xcode Group in the Groups and Files pane that are actually distributed all over the file system of your computer. You use them in the Groups & Files pane simply to group together those items of any of the four types just described that you feel are related somehow.
... ... @@ -16,44 +16,38 @@
16 16  
17 17  For the application server:
18 18  
19 -{{code}}
15 +{{panel}}
20 20  
21 -MyProject.woa
22 - MyProject - a Unix shell script to which control is initially passed and which sets up the execution environment under Unix
23 - MyProject.CMD - a DOS command script to which control is initially passed and which sets up the execution environment under DOS/Windows
24 - WOBootstrap.jar - a jar file containing a single class called JavaArchiveFilter that implements the java.io.FilenameFilter interface
25 - Contents - a directory containing all of the files necessary to support the execution of the WO app
26 - Info.plist - a property list file for the application
27 - MacOS/
28 - MyProject - a Unix shell script identical to that of the same name at the top level of the project directory
29 - MacOSClassPath.txt - text file containing the derived Java ClassPath for the project
30 - PkgInfo - a text file containing the four letter package type (APPL = application) and the application's four letter file types
31 - Resources/ - a directory containing the WOComponents and other resources in the Resources group of the Groups & Files pane
32 - UNIX/ - a directory similar to the MacOS directory but used for deployment on Unix systems
33 - Windows/ - a directory similar to the MacOS directory but used for deployment on Windows systems
34 - pbdevelopment.plist - an XML file with a single element whose key is PBXProjectSourcePath and whose value is implied by the name.
17 + MyProject.woa
18 + MyProject - a Unix shell script to which control is initially passed and which sets up the execution environment under Unix
19 + MyProject.CMD - a DOS command script to which control is initially passed and which sets up the execution environment under DOS/Windows
20 + WOBootstrap.jar - a jar file containing a single class called JavaArchiveFilter that implements the java.io.FilenameFilter interface
21 + Contents - a directory containing all of the files necessary to support the execution of the WO app
22 + Info.plist - a property list file for the application
23 + MacOS/
24 + MyProject - a Unix shell script identical to that of the same name at the top level of the project directory
25 + MacOSClassPath.txt - text file containing the derived Java ClassPath for the project
26 + PkgInfo - a text file containing the four letter package type (APPL = application) and the application's four letter file types
27 + Resources/ - a directory containing the WOComponents and other resources in the Resources group of the Groups & Files pane
28 + UNIX/ - a directory similar to the MacOS directory but used for deployment on Unix systems
29 + Windows/ - a directory similar to the MacOS directory but used for deployment on Windows systems
30 + pbdevelopment.plist - an XML file with a single element whose key is PBXProjectSourcePath and whose value is implied by the name.
35 35  
36 -{{/code}}
32 +{{/panel}}
37 37  
38 38  For the Web Server:
39 39  
40 -{{code}}
36 +{{panel}}
41 41  
42 -MyProject.woa
43 - Contents - a directory containing all of the files necessary to support the execution of the WO app
44 - WebServerResources/
45 - Hierarchy of files and folders containing static web resources.
38 + MyProject.woa
39 + Contents - a directory containing all of the files necessary to support the execution of the WO app
40 + WebServerResources/
41 + Hierarchy of files and folders containing static web resources.
46 46  
47 -{{/code}}
43 +{{/panel}}
48 48  
49 49  Although the packages are very different, they are identically named, have similar structures and are merged in development. They are typically ONLY separated like this for a split install. You typically put the application server package in /Library/WebObjects/Applications (or a local equivalent) and you typically put the WebServer package in /Library/WebServer/Documents/WebObjects.
50 50  
51 51  You can create these packages independently in various ways. I've found it easier, recently (because of various examples of Xcode intransigence) to simply build the project as I would for development and physically separate the two for deployment. Other people have various incantations to make a split install work reliably and I'm sure they will chime in here.
52 52  
53 -=== Other Links: ===
54 -
55 -* [[Standard Deployment>>Deployment-Standard Deployment]]
56 -* [[Tomcat Deployment>>Deploying with Tomcat]]
57 -* [[Split Install Deployment>>WOL:Split Install Deployment]]
58 -* [[Remote deployment with Ant and ssh>>WOL:Remote deployment with Ant and ssh]]
59 -* [[Logging>>Log Rotation]]
49 +Category:WebObjects