Le 2011-07-27 à 10:04, Jon Kleiser a écrit : > Thanks, Pascal. > > When I ceated the new WO Application, I left the package fields empty, and > under Sources I now have a "(default package)". Should all my .java files go > into that one?
If your Java classes are not in a package, yes they go there. You can easily package them after, but beware of your variables in your components. If they are protected instead of public, moving to packages will throw errors because the variables/methodes have to be public, but Xcode/WOBuilder were creating them as protected. > In build.properties, I have entered > "wolips.properties=/Users/<me>/Library/Application > Support/WOLips/wolips.543.properties". Do I have to do anything else for > WOLips to find the WebObjects frameworks during 'build' and 'run'? > > /Jon > > On 27-07-11 15:13 , Pascal Robert wrote: >> Hi Jon, >> >> Yes, in fact the tutorial you see is the old project structure, before >> "Fluffly Bunny" came into action. >> >> I strongly suggest that you follow the current WOLips structure, so that you >> don't have problems in the future. In the new (well, new for the last 3 >> years), you will find the following folders: >> >> Components : this is where your WO components goes. You can create >> sub-folders in there. >> Libraries : this is your jar files goes (the "lib" folder you currently >> have) >> Resources : this is where the Properties file and your EO models goes >> Sources : same as the "src" folder >> WebServerResources : this is where, you can guess it, the Web server >> resources (.js, .css, etc.) goes >> >> Really, you should move to that structure, or else you will have to fight >> with WOLips and Ant so that they can find your files elsewhere. >> >> Also, you will find that WOLips will probably throw out a lot of validation >> errors or warnings. WOLips is a hell better that Xcode to find Java and >> WO-specific errors, by fixing those errors, you will probably make your >> project better. It can take some time, but it's worth it. >> >>> Hi, >>> >>> I want to migrate an old WO project (in CVS) from Xcode to WOLips on OSX >>> 10.6.8 (unless there should be better alternatives than WOLips). I have >>> installed Eclipse Helios (3.6.2) and WOLips, and the WebObjects frameworks >>> (533 and 543). >>> >>> Following this tutorial ... >>> http://wiki.objectstyle.org/confluence/display/WOL/Import+an+Xcode+project+into+WOLips >>> ... I have created a new WO Application, but what I get differs in several >>> ways from what I see in the tutorial. The reason may be that the tutorial >>> is from 2007. Is there a newer tutorial somewhere? >>> >>> If possible I want a WOLips project that has a folder structure that is >>> similar to what I have in my Xcode project, and I would also prefer to make >>> as few changes to existing files as possible. In my Xcode project, all >>> .java files are located in a 'src' folder, all .jar files are located in a >>> 'lib' folder, components (.html, .wod, .woo) are organized as .wo folders, >>> and other files (.api, .gif, .css, .js, ...) are scattered at the top >>> level. There is no 'package' structure or details. >>> >>> What are my prospects for a successful migration? Which changes (to files, >>> or folder structure) will be hard to avoid? I look forward to some helpful >>> info on these matters ... >>> >>> Sincerely, >>> >>> Jon K. > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
