Personally, I have my flash and my java in the same workspace but not in the same project. They are built into the same directory for deployment. This provides all the benefit I think you need. As far as I can tell, so long as they are available to me at the same workspace (which is quite useful) I dont see much benefit to being in the same project.
Now, I dont know what the issues are as far as asdt. I actually dont use it. The reasons are purely historical. I found a way that works and I am sticking with it. I use flex2 to edit my source. I use an expired version of FDT to build as2 apps with mtasc, but soon I will switch to ant. Due to the fundamentally customer hostile behavior at FDT I will not pay for their product. This is particularly true now that I am going to need flex2 anyway. Regards Hank On 12/14/05, Steve Canny (scanny) <[EMAIL PROTECTED]> wrote: > I am wondering if there is any existing wisdom on how to structure the > build/project directory of an Eclipse-based Rich Internet Application > (RIA) that includes both J2EE elements as well as Flash elements? > > I'm developing a Flash application that is integrated within a J2EE > application via web services (via SOAP). The user initially interacts > with the JSP-based web application to authenticate and to select among a > saved set of customer scenarios. Once they have arrived at the desired > customer scenario web page (JSP), they click on a link to initiate the > Flash application in a popup window. The Flash application retrieves the > customer scenario dataset via web service and saves it the same way. > Then the user returns to the JSP pages until the next Flash launch. > > The question I'm wrestling with is how to integrate the Flash > application elements with the broader J2EE elements in the Eclipse > project directory structure. > > I've organized the J2EE application build structure roughly along the > lines recommended by the Java community, roughly as follows: > build/ > build/conf > build/dist/app.war, etc. > build/build.xml > flashapp/ (proposed) > flashapp/assets > flashapp/com/.../*.as > flashapp/app.fla > src/ > src/java > web/ > web/WEB-INF > web/WEB-INF/classes > web/WEB-INF/images > web/WEB-INF/jsp > web/WEB-INF/swf > ... etc. > > I think it would be the most handy to be able to build the entire > project from scratch (assuming javac and mtasc were available on path) > within a single Eclipse project. At the same time, I suspect from > initial evidence that ASDT does not necessarily "play-nice" with the > other members of an Eclipse Java project. (Perhaps AS "Nature" is not > compatible with Eclipse Java Nature?) > > Should I just give up and declare the flash portion of the overall > project as a separate Eclipse project and attempt to integrate across > projects? Or has someone succeeded in integrating an AS "sub-project" > into an Eclipse Java Project and lived to tell the tale? > > I will be grateful for any guidance you can offer, as will the > osflash.org record, I'm sure. > > Best, > Steve > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
