Tracy: It does appear that using a relative path will not work... At least not in the .CFC files... (It does appear to work if I specify the relative-path in the Flex .AS component, and the full-path in the .CFC files, however...) So apparently CF is looking for the path relative to the web-root, not to the .SWF's path... If anyone knows how to change this behavior, I'd be very happy to hear it.
Valdhor: I need a separate working folder so that when I'm making changes, people can still use the app (in the "live" folder) for testing purposes without receiving silly errors that will pop up from time-to-time because I'm in the middle of editing something... It's caused confusion before, and I'm simply trying to make it so the testers see as few errors as possible... Of course, we have a completely separate server for our actual web-site, so it doesn't affect end-users... But on the test-server, this issue has cropped up more than once, so I keep a separate working-folder and live-folder on the development server. L. --- In [email protected], "valdhor" <valdhorli...@...> wrote: > > What I generally do is not use a "Working Folder" on the server. I use the > "Live" folder for everything. > > Is there any specific reason you need a "Working Folder"? If this is new > code, don't you need new ValueObjects? If this is existing code and you need > to add new properties to a ValueObject, (I don't know if ColdFusion does, but > PHP does) you can subclass the existing ValueObject and add properties to the > new class. Either way, there is a new ValueObject class that will not affect > existing code. > > > > --- In [email protected], "Tracy Spratt" <tracy@> wrote: > > > > I have not used Remote object enough to be an authority on your specific > > issue, but that looks like a package path and typically package paths are > > relative, starting at the project root, (in my setups, this is "src") , so > > the deployment location is never an issue. Are yo sure you need to specify > > "MyworkingFolder"? > > > > > > > > Tracy Spratt, > > > > Lariat Services, development services available > > > > _____ > > > > From: [email protected] [mailto:[email protected]] On > > Behalf Of Ivan Wang > > Sent: Saturday, March 13, 2010 7:46 PM > > To: [email protected] > > Subject: Re: [flexcoders] Automatically update ValueObjects... > > > > > > > > > > > > But In what case do you have to change a package name? If you really did, > > the Flex Builder has some refactor feature, but not too much. You can try > > it, I'm not sure. > > > > > > > > > > > > ----- Original Message ----- > > > > From: Laurence <mailto:LMacNeill@> > > > > To: flexcod...@yahoogro <mailto:[email protected]> ups.com > > > > Sent: Saturday, March 13, 2010 6:46 AM > > > > Subject: [flexcoders] Automatically update ValueObjects... > > > > > > > > > > > > I have several ValueObjects in my app... When I work with them in my test > > website, everything's fine. But when I want to export a release build, the > > ValueObjects no longer work because the folder-name is different... > > > > All my VO's have the following type of declaration at the top: > > [RemoteClass(alias="MyWorkingFolder.cfcs.vo.MyValueObjectVO")] > > > > And on the ColdFusion9 side it's: > > <cfcomponent output="false" alias="MyWorkingFolder.cfcs.vo.MyValueObjectVO"> > > > > Thus, when I export the release-build from MyWorkingFolder to MyLiveFolder > > (for example) all of the VOs stop working -- they're still looking for > > MyWorkingFolder. > > > > How do I get FlexBuilder to change the names inside the VOs automatically to > > match the release-build destination? So far, I've been doing it manually, > > but what a pain that is -- my patience is wearing thin, having to manually > > update a bunch of damn VOs, then change them back, every time I want to > > export a release build... There has to be a better way that I'm just not > > aware of... > > > > Thanks, > > Laurence MacNeill > > Mableton, Georgia, USA > > >
