I had to add a MIME type to my server to be able to use the SWZ. I can't recall exactly what it is but the actual mime type was the same for SWZ as it was for SWF. Otherwise my server itself didn't know how to "serve" the file and it would roll over to the SWF.
As for your first question, how to dictate where to look for RSLs - in FB3, go to the panel where you can select to use RSLs rather than Merged into Code. (Project->Preferences->Flex Build Path - Library Path tab) - There's a list of build path libraries. For the framework rsl, you'd dive into the first (Flex 3.0.0 - or whatever framework you're using), and open the framework.swc dropdown. Select the "RSL URL". On the right hand side there's an "Edit" button you need to click next. It'll open up a panel to be able to choose where to find the RSL from! And you'd do the same for the rest of your RSLs. It should be noted however, changing the path of the framework RSLs seems to have an "issue" if you choose the option to "Copy to deployment path". It DOES put a SWZ & and a SWF to your deployment path, and also both in the root of where your main SWF is (when building). The SWZ/SWF from your deployment path will NOT match your main SWF - those output in the same folder as your main SWF DO match. So an additional step you'll need to do is move these files to the correct location. One sure way to verify this is to see when the SWZ/SWFs were created. If they're "created" at the same time as your main SWF, they're good, if the date is one from several months ago - it's the actual file used to deploy off of. It's kind of a pain and may possibly be a bug or some other issue - not real sure. Hopefully this helps get everything straightened out! :D -Nathan D. --- In flexcoders@yahoogroups.com, Alex Harui <[EMAIL PROTECTED]> wrote: > > You said you build the framework into an RSL, so I thought that meant you built a new RSL. > > The way you set up the options in MXMLC dictate the location of the RSLs and the order it will look for them. > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of whatabrain > Sent: Thursday, September 04, 2008 3:00 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Re: Help with runtime shared libraries > > > It is signed by Adobe. This is the standard framework swz that > FlexBuilder creates when you tell it to use an RSL. > > --- In flexcoders@yahoogroups.com<mailto:flexcoders% 40yahoogroups.com>, Alex Harui <aharui@> wrote: > > > > You won't be able to publish a SWZ only Adobe can do that. They > have to be signed by Adobe. > > > > From: flexcoders@yahoogroups.com<mailto:flexcoders% 40yahoogroups.com> > [mailto:flexcoders@yahoogroups.com<mailto:flexcoders% 40yahoogroups.com>] On Behalf Of whatabrain > > Sent: Thursday, September 04, 2008 2:32 PM > > To: flexcoders@yahoogroups.com<mailto:flexcoders% 40yahoogroups.com> > > Subject: [flexcoders] Help with runtime shared libraries > > > > > > I made the flex framework into an RSL, and I put both the swf and > swz > > versions in servername.com/subdir/. This is the same location where > the > > Flex app itself is located. Then I load the page, using the latest > > version of Flash 9. I get the following error: > > > > Error #2032: Steam Error. URL: > > http://servername.com/framework_3_0_0.477.swf > > > > Now I can obviously fix this by putting the swf in the root htdocs > > directory, but I have two questions: > > > > 1) How can I get Flash to look in the app's subdirectory for the > > framework files? I'm using FlexBuilder 3, if that helps. > > > > 2) Why is the browser requesting the swf instead of the swz? > > > > Thanks. > > >
