On 12/4/06, Jamie O <[EMAIL PROTECTED]> wrote: > Hello, > > After a laborious day of uninstalling, re-installing, washing, > rinsing, repeating, I finally have my eclipse environment setup with > WTP, Java 1.5 and the FDS Plugin Project Peter Martin created. The > directory structure seems to make more sense to me, but have raised a > couple of questions in my brain - some of which are general Flex / > FDS, others are specific to WTP / Tomcat implementation: > > 1) Without using Peter's FDS Plugin, what is the easiest way to deploy > a FDS-enabled project as http://localhost:8080/ or > http://localhost:8080/ProjectName/? Every example I've been able to > find has it coming out of the flex.war as > http://localhost:8080/Flex/ProjectName/ >
This is, in my opnion, an incredible error in design that I would hope that they fix. When building on your development environment, as opposed to on the server, there is no way to get it to automatically put the index.html and your swf at the root of your webapp. It will always be at webappname/flexappname a.k.a localhost:8080/flexappname. What I actually do when I am deploying to my server is to copy all the files from webappname/flexappname to the webappname directory. Its ugly but several others on the list have said that they have encountered the same problem and there is no good solution. I *have* heard that it is possible to do this if you compile on the server, but since I was never interested in this I have no idea if this is true. > > 2) When deploying using FDS compile on server option, how can you > configure your server to acknowledge > http://localhost:8080/HelloWorld/Main.mxml when > http://localhost:8080/HelloWorld/ is accessed? Default .mxml > parameters? I'd figure to use the index.htm with presentation similar > to the template when using a non-FDS enabled version but unclear where > to point the embed items to. > > > 3) FDS Plugin Specific - How *should* one break down their content > w.r.t the directory structure provided? I was able to create a simple > sample (one event class, one valueobject, two component .mxml views > called from the Main.mxml. The only way I was able to get any to work > was with everything nested within sub-directories of the WebContent > folder. I'd expect I could use the [source_path]user_classes for .swc > but it didn't seem to play nice with pure .as files. > I have been able to use the source path thing but at this point all of my code is in my project so I cant tell you if there are any tricks to getting it to work because I cant remember. But at least I can tell you that it does work. > 4) Same question as #3 but expand your example answer for a > Cairngorm-ified project. > I dont quite understand this question because the cairngorm directory structure is pretty clear. Are you asking how you store your cairngorm files outside what you called your webContent folder? If that is the question, I would not suggest it. One thing I do though, to modularize my work is that my project is made up of a collection of smaller cairngorm based projects that link to one another. The only issue is that the services.mxml cant be shared. But this allows me to look at small nuggets of my app rather than a huge common structure. It also allows me to create swc's that can be shared with other projects. For example I have created a login system that I can drop into other apps fairly easily. > 5) How to turn all this into a deployable .war or .ear file on a > non-development machine? This is more a general java question but > figured I'd press my luck like that old tv show and make it a 5 pack > o' questions. > I dont use WTP because it just seemed to complicated. I didnt want to spend the more than a day I guessed it would take to figure out how to work throught the horrendous documentation. As a result I use the sysdeo tomcat plugin which works like a charm. I right click on my project and say "build war" and it does it. I would imagine WTP has something like this but it was just so ugly I couldnt bear it. But in any case a WAR is nothing more than a compressed (zip?) of the webapp directory structure with your app in it. So it shouldnt be too hard to get that from eclipse to deployment. But if you are committed to WTP I am sure (hope?) there is some option for this. Regards, Hank
