This looks correct. You don't need -target-player=9.0.60 but it is 
not hurting anything.

-Darrell

--- In flexcoders@yahoogroups.com, "danielvlopes" <[EMAIL PROTECTED]> 
wrote:
>
> The correct way is this:
> -runtime-shared-library-path=C:\3.0.0
\frameworks\libs\framework.swc,C:\3.0.0
\frameworks\rsls\framework_3.0.183453.swz,,framework_3.0.183453.swf
> -target-player=9.0.60 ?
> 
> 
> --- In flexcoders@yahoogroups.com, "danielvlopes" <danielvlopes@>
> wrote:
> >
> > Hello Darrell, i trying to do this:
> >
> -runtime-shared-library-path=C:\3.0.0
\frameworks\rsls\framework_3.0.183453.swz,,framework_3.0.183453.swf
> > -target-player=9.0.60
> > 
> > like you said, but i getting error:
> > command line: Error: configuration variable
> > 'runtime-shared-library-path' requires a value for 'rsl-url'
> > 
> > --- In flexcoders@yahoogroups.com, "Darrell Loverin"
> > <darrell_loverin@> wrote:
> > >
> > > Yes, that is a correct way of using a swz (signed by Adobe) 
RSL. The 
> > > first URL is framework_3.0.183453.swz. Since there is no path, 
it 
> > > means you are deploying framework_3.0.183453.swz in the same 
> > > directory as your application. As was noted in a previous 
post, the 
> > > rsls are located in the frameworks/rsls subdirectory of the 
SDK. The 
> > > next parameter is the policy file URL which you have left 
blank 
> > > since a policy file not needed to read 
framework_3.0.183453.swz. The 
> > > next URL, framework_3.0.183453.swf, is the failover URL in 
case 
> > > there is a problem reading framework_3.0.183453.swz. One 
problem 
> > > could be the player trying to load framework_3.0.183453.swz is 
not 
> > > version 9.0.60 or greater. If that is the case then 
> > > framework_3.0.183453.swz will be skipped and 
> > > framework_3.0.183453.swf will be downloaded.
> > > 
> > > Since you have specified an unsigned swf RSL as a failover for 
the 
> > > swz RSL, you don't need the -target-player option, but it is 
not 
> > > hurting anything.
> > > 
> > > What -target-player=9.0.60 does is tell the compiler that you 
are 
> > > going to require player version 9.0.60 or higher in your html 
> > > wrapper. This will stop the compiler from complaining if you 
specify 
> > > a swz RSL without a swf RSL as a failover.
> > > 
> > > 
> > > -Darrell
> > > 
> > > 
> > > 
> > > --- In flexcoders@yahoogroups.com, "danielvlopes" 
<danielvlopes@> 
> > > wrote:
> > > >
> > > > Hello Alex,
> > > > 
> > > > Let me understand... the right way is using swz?
> > > > 
> > > > Like this?
> > > >                 <exec executable="${flex.mxmlc}" dir="." 
> > > failonerror="false"
> > > > failifexecutionfails="no">
> > > >                         
> > > >                         <arg line="PainelAdmApp.mxml
> > > > -runtime-shared-library-path=C:\3.0.0
> > > 
\frameworks\libs\framework.swc,framework_3.0.183453.swz,,framework_3.
> > > 0.183453.swf
> > > > -target-player=9.0.60 -services services-config.xml
> > > > -link-report=PainelAdmAppReport.xml -output
> > > > ${deploy.dir}/PainelAdmApp.swf" />
> > > >                 </exec> 
> > > > 
> > > > Why i`m use ANT the .swf and .swz of framework is not 
generated?
> > > > 
> > > > --- In flexcoders@yahoogroups.com, "Alex Harui" <aharui@> 
wrote:
> > > > >
> > > > > I think the rsl line is supposed to look like this:
> > > > >  
> > > > > -runtime-shared-library-
> > > path=C:\moxie\frameworks\libs\framework.swc,fram
> > > > > ework_3.0.183453.swz,,framework_3.0.183453.swf
> > > > >  
> > > > > This signifies the use of a digital signature for the rsl 
> > > which "turns
> > > > > on" the cross-domain rsl feature and requests that the 
rsl, if 
> > > the
> > > > > signature is verifed, be stored in a special cache.
> > > > >  
> > > > > Your syntax is used for regular rsls which are only stored 
in the
> > > > > browser cache.
> > > > >  
> > > > > -Alex
> > > > > 
> > > > > ________________________________
> > > > > 
> > > > > From: flexcoders@yahoogroups.com 
> > > [mailto:[EMAIL PROTECTED] On
> > > > > Behalf Of danielvlopes
> > > > > Sent: Saturday, October 06, 2007 4:29 PM
> > > > > To: flexcoders@yahoogroups.com
> > > > > Subject: [flexcoders] Re: Framework Caching not working
> > > > > 
> > > > > 
> > > > > 
> > > > > Thanks again alex. :-)
> > > > > 
> > > > > --- In flexcoders@yahoogroups.com <mailto:flexcoders%
> > > 40yahoogroups.com>
> > > > > , "Alex Harui" <aharui@> wrote:
> > > > > >
> > > > > > Sorry, I think the guy who owns this feature was on 
vacation 
> > > this past
> > > > > > week. I'll try to look at it if I get a chance.
> > > > > > 
> > > > > > -Alex
> > > > > > 
> > > > > > ________________________________
> > > > > > 
> > > > > > From: flexcoders@yahoogroups.com <mailto:flexcoders%
> > > 40yahoogroups.com>
> > > > > [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%
> > > 40yahoogroups.com>
> > > > > ] On
> > > > > > Behalf Of danielvlopes
> > > > > > Sent: Saturday, October 06, 2007 1:23 PM
> > > > > > To: flexcoders@yahoogroups.com <mailto:flexcoders%
> > > 40yahoogroups.com> 
> > > > > > Subject: [flexcoders] Re: Framework Caching not working
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Some one can help??
> > > > > > 
> > > > > > --- In flexcoders@yahoogroups.com
> > > > > <mailto:flexcoders%40yahoogroups.com>
> > > > > <mailto:flexcoders%40yahoogroups.com>
> > > > > > , "danielvlopes" <danielvlopes@>
> > > > > > wrote:
> > > > > > >
> > > > > > > My flash player is 9,0,60,235
> > > > > > > 
> > > > > > > Even i use Beta 2, caching still not working.
> > > > > > > I don't know why, some one can help?
> > > > > > > Something wrong with my buil.xml?
> > > > > > > 
> > > > > > > --- In flexcoders@yahoogroups.com
> > > > > <mailto:flexcoders%40yahoogroups.com> 
> > > > > > <mailto:flexcoders%40yahoogroups.com> , Tom Chiverton 
> > > <tom.chiverton@>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > On Wednesday 03 Oct 2007, danielvlopes@ wrote:
> > > > > > > > > I don't uderstand Alex, i not sure it is important 
but 
> > > i'm using
> > > > > > flex
> > > > > > > > > builder 3 beta 1.
> > > > > > > > 
> > > > > > > > Beta 2 is out now, try that.
> > > > > > > > Also, what Player version do you have ? Only 9.0.60 
or 
> > > better can
> > > > > > > make use of 
> > > > > > > > RSL.
> > > > > > > > It is my understanding that older players will fall 
back to
> > > > > > loading the 
> > > > > > > > framework every time.
> > > > > > > > 
> > > > > > > > -- 
> > > > > > > > Tom Chiverton
> > > > > > > > Helping to vitalistically establish bricks-and-clicks
> > > > > architectures
> > > > > > > > on: http://thefalken.livejournal.com
> > > > > <http://thefalken.livejournal.com> 
> > > > > > <http://thefalken.livejournal.com 
> > > <http://thefalken.livejournal.com> >
> > > > > 
> > > > > > > > 
> > > > > > > > ****************************************************
> > > > > > > > 
> > > > > > > > This email is sent for and on behalf of Halliwells 
LLP.
> > > > > > > > 
> > > > > > > > Halliwells LLP is a limited liability partnership 
> > > registered in
> > > > > > > England and Wales under registered number OC307980 
whose 
> > > registered
> > > > > > > office address is at St James's Court Brown Street 
> > > Manchester M2
> > > > > 2JF.
> > > > > > > A list of members is available for inspection at the 
> > > registered
> > > > > > > office. Any reference to a partner in relation to 
Halliwells 
> > > LLP
> > > > > > > means a member of Halliwells LLP. Regulated by The 
Solicitors
> > > > > > > Regulation Authority.
> > > > > > > > 
> > > > > > > > CONFIDENTIALITY
> > > > > > > > 
> > > > > > > > This email is intended only for the use of the 
addressee 
> > > named
> > > > > above
> > > > > > > and may be confidential or legally privileged. If you 
are 
> > > not the
> > > > > > > addressee you must not read it and must not use any 
> > > information
> > > > > > > contained in nor copy it nor inform any person other 
than 
> > > Halliwells
> > > > > > > LLP or the addressee of its existence or contents. If 
you 
> > > have
> > > > > > > received this email in error please delete it and 
notify 
> > > Halliwells
> > > > > > > LLP IT Department on 0870 365 8008.
> > > > > > > > 
> > > > > > > > For more information about Halliwells LLP visit
> > > > > www.halliwells.com.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


Reply via email to