OK, after a frustrating afternoon, I've nailed it in typical "10 minutes
after
final act of desparation mailing flexcoders"
fashion....
If you profile your application as follows it won't
work:
However if you do the following:
and instead ensure that you have
the following entry in flex-config.xml
<!-- generate swfs and swfs for
profiling -->
<!-- query parameter override - ?asprofile=true/?asprofile=false -->
<generate-profile-swfs>true</generate-profile-swfs>
<!-- query parameter override - ?asprofile=true/?asprofile=false -->
<generate-profile-swfs>true</generate-profile-swfs>
then everything works as advertised.....
The reason for this I'm afraid, is that the profiler.war app has a
bug,
and isn't encoding the URLs properly - ie if you have a query
parameter
appended to your URL, it's not encoding the ?asprofile=true
correctly,
and then to drill down, is trying to open a URL like:
See how that URL has a double "?" in it (the latter ? should have
been
encoded) ... that's enough to cause the profiler
to bug out I'm afraid.
So -- Macromedia, it's a bug with a workaround I'm afraid; should I
raise
this somewhere ?
Hope this helps,
Steven
--
Steven Webster
Technical Director
iteration::two
