QuickTime description in metadata

Hi,
I have currently my QuickTime videos (own recordings) with metadata such as title, description, genre, actors... These I can edit and view in various software, both for playback and file habdling. One of them is iTunes. This is very convenient to have these meta data when browsing in video library. Off course I would like to do this with LR.
This data is not read by LR. Why not?  Then it's easier to use LR to manage QuickTime movies.
Thanks
Olof

LR4 release. Looks like it still can't read and write video meta data

Similar Messages

  • [CS3 JS] Possible to Inspect Custom XMP Metadata With JavaScript?

    I am using custom XMP metadata in InCopy and InDesign docs in CS3 to hold custom metadata that can vary wildly. I know the full set of possible items but not what values will be in a particular document.
    Short of writing the XMP to a file and then processing that from my script, is there a way to inspect the custom properties from JavaScript. I didn't see a way to do it from the data model.
    Thanks,
    Eliot

    Here is another script to catch MetaData, some more than the basic:
    // metaDataOfLinks.jsx
    //DESCRIPTION: Catches MetaData of linked images and creates a report at the DeskTop.
    // Martin Fischer 10/2008
    var myLinkXmpArray = ["author", "copyrightInfoURL", "copyrightNotice", "copyrightStatus   ", "creationDate", "creator", "description", "documentTitle", "format", "jobName", "keywords", "modificationDate", "serverURL"];
    var myIPTCArray = ["CiAdrCity", "CiAdrCtry", "CiAdrExtadr", "CiAdrPcode", "CiAdrRegion", "CiEmailWork", "CiTelWork", "City", "CiUrlWork", "CopyrightNotice", "Country", "CountryCode", "Creator", "CreatorContactInfo", "CreatorJobtitle", "DateCreated", "Description", "DescriptionWriter", "Headline", "Instructions", "IntellectualGenre", "JobID", "Keywords", "Location", "Provider", "Province-State", "RightsUsageTerms", "Scene", "Source", "SubjectCode", "Title"];
    var myPSArray = ["photoshop:AuthorsPosition", "photoshop:CaptionWriter", "photoshop:Category", "photoshop:City", "photoshop:Country", "photoshop:Credit", "photoshop:DateCreated", "photoshop:Headline", "photoshop:Instructions", "photoshop:Source", "photoshop:State", "photoshop:SupplementalCategories", "photoshop:TransmissionReference", "photoshop:Urgency"];//var myPSArray = ["photoshop:AuthorsPosition", "CaptionWriter", "Category", "City", "Country", "Credit", "DateCreated", "Headline", "Instructions", "Source", "State", "SupplementalCategories", "TransmissionReference", "Urgency"];
    var myTiffArray = ["tiff:ImageWidth", "tiff:ImageLength", "tiff:BitsPerSample", "tiff:Compression", "tiff:PhotometricInterpretation", "tiff:Orientation", "tiff:SamplesPerPixel", "tiff:PlanarConfiguration", "tiff:YCbCrSubSampling", "tiff:YCbCrPositioning", "tiff:XResolution", "tiff:YResolution", "tiff:ResolutionUnit", "tiff:TransferFunction", "tiff:WhitePoint", "tiff:PrimaryChromaticities", "tiff:YCbCrCoefficients", "tiff:ReferenceBlackWhite", "tiff:DateTime", "tiff:ImageDescription", "tiff:MakeProperName", "tiff:Model", "tiff:Software", "tiff:Artist", "tiff:Copyright"];
    var myExifArray = ["exif:ExifVersion", "exif:FlashpixVersion", "exif:ColorSpace", "exif:ComponentsConfiguration", "exif:CompressedBitsPerPixel", "exif:PixelXDimension", "exif:PixelYDimension", "exif:UserComment", "exif:RelatedSoundFile", "exif:DateTimeOriginal", "exif:DateTimeDigitized", "exif:ExposureTime", "exif:FNumber", "exif:ExposureProgram", "exif:SpectralSensitivity", "exif:ISOSpeedRatings", "exif:OECF", "exif:ShutterSpeedValue", "exif:ApertureValue", "exif:BrightnessValue", "exif:ExposureBiasValue", "exif:MaxApertureValue", "exif:SubjectDistance", "exif:MeteringMode", "exif:LightSource", "exif:Flash", "exif:FocalLength", "exif:SubjectArea", "exif:FlashEnergy", "exif:SpatialFrequencyResponse", "exif:FocalPlaneXResolution", "exif:FocalPlaneYResolution", "exif:FocalPlaneResolutionUnit", "exif:SubjectLocation", "exif:ExposureIndex", "exif:SensingMethod", "exif:FileSource", "exif:SceneType", "exif:CFAPattern", "exif:CustomRendered", "exif:ExposureMode", "exif:WhiteBalance", "exif:DigitalZoomRatio", "exif:FocalLengthIn35mmFilm", "exif:SceneCaptureType", "exif:GainControl", "exif:Contrast", "exif:Saturation", "exif:Sharpness", "exif:DeviceSettingDescription", "exif:SubjectDistanceRange", "exif:ImageUniqueID", "exif:GPSVersionID", "exif:GPSLatitude", "exif:GPSLongitude", "exif:GPSAltitudeRef", "exif:GPSAltitude", "exif:GPSTimeStamp", "exif:DateTimeOriginal,", "exif:DateTimeDigitized.", "exif:GPSTimeStamp", "exif:GPSSatellites", "exif:GPSStatus", "exif:GPSMeasureMode", "exif:GPSDOP", "exif:GPSSpeedRef", "exif:GPSSpeed", "exif:GPSTrackRef", "exif:GPSTrack", "exif:GPSImgDirectionRef", "exif:GPSImgDirection", "exif:GPSMapDatum", "exif:GPSDestLatitude", "exif:GPSDestLongitude", "exif:GPSDestBearingRef", "exif:GPSDestBearing", "exif:GPSDestDistanceRef", "exif:GPSDestDistance", "exif:GPSProcessingMethod", "exif:GPSAreaInformation"];
    var myCameraRawArray = ["crs:AutoBrightness", "crs:AutoContrast", "crs:AutoExposure", "crs:AutoShadows", "crs:BlueHue", "crs:BlueSaturation", "crs:Brightness", "crs:CameraProfile", "crs:ChromaticAberrationB", "crs:ChromaticAberrationR", "crs:ColorNoiseReduction", "crs:Contrast", "crs:CropTop", "crs:CropLeft", "crs:CropBottom", "crs:CropRight", "crs:CropAngle", "crs:CropWidth", "crs:CropHeight", "crs:CropUnits", "crs:Exposure", "crs:GreenHue", "crs:GreenSaturation", "crs:HasCrop", "crs:HasSettings", "crs:LuminanceSmoothing", "crs:RawFileName", "crs:RedHue", "crs:RedSaturation", "crs:Saturation", "crs:Shadows", "crs:ShadowTint", "crs:Sharpness", "crs:Temperature", "crs:Tint", "crs:ToneCurve", "crs:ToneCurveName", "crs:Version", "crs:VignetteAmount", "crs:VignetteMidpoint", "crs:WhiteBalance"];
    var myInfo = new Array;
    var myDoc = app.activeDocument;
    var myLinks = app.documents[0].links;
    for ( i = 0; i < myLinks.length; i++)
       getMetaData ( myLinks[i] );
    writeData ( 'Metadaten zu ' + myDoc.name + '\r-----------\r\r' + myInfo.join ( '\r\r'), File ('~/Desktop/Metadaten_' + myDoc.name.replace(/.indd$/, '') + '.txt'));
    // ===============================================================
    //                                  Funktionen
    // ===============================================================
    function getMetaData ( aLink )
       var myLinkXmp = aLink.linkXmp.properties.toSource().replace( /^\(\{/,'' ).replace (/\)\}$/,'').replace( /parent.+$/,'').replace(/:/g, ':\t').split( ', ');
       var myString = aLink.name;
       myString += loopLinkXmp ( aLink, myLinkXmpArray );
       myString += loopArray ( aLink, "http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/",  "Iptc4xmpCore:CreatorContactInfo/Iptc4xmpCore:",  myIPTCArray);
       myString += loopArray ( aLink, "http://ns.adobe.com/photoshop/1.0/",  "", myPSArray );
       myString += loopArray ( aLink, "http://ns.adobe.com/tiff/1.0/", "", myTiffArray );
       myString += loopArray ( aLink, "http://ns.adobe.com/exif/1.0/", "", myExifArray );
       myString += loopArray ( aLink, "http://ns.adobe.com/camera-raw-settings/1.0/",  "", myCameraRawArray );
       myInfo.push( myString.replace( /, $/,'') );
    function loopArray( aLink, s1, s2, anArray )
       var temp = '\r\t--- ' + s1 + ' ---\r\t';
       for ( var a = 0; a < anArray.length; a++)
          try {
             var theEvalString = 'aLink.linkXmp.getProperty(\"' + s1 + '\", \"' + s2 + anArray[a] + '\")';
             var myCode = eval( theEvalString );
             if ( myCode != '' )
                temp += '[' + anArray[a] + ']\t' +  myCode + '\r\t'; 
          } catch (e){ //temp +=e + '\r'
       return temp;
    function loopLinkXmp( aLink, anArray )
       var temp = '\r\t--- LinkMetadata ---\r\t';
       for ( var a = 0; a < anArray.length; a++)
          try {
             var theEvalString = 'aLink.linkXmp.' + anArray[a] ;
             var myCode = eval( theEvalString );
             if ( myCode != '' )
                temp += '[' + anArray[a] + ']\t' +  myCode + '\r\t'; 
          } catch (e){ //temp +=e + '\r'
       return temp;
    function writeData ( aData, theFile )
       theFile.open ( 'w', 'Text', 'R*ch' );
       theFile.encoding = 'UTF-8';
       theFile.write ( aData );
       theFile.close ();
    Ressources:
    Adobe XMP Developer Center: http://www.adobe.com/devnet/xmp/
    XMP Specification: http://www.adobe.com/devnet/xmp/pdfs/xmp_specification.pdf
    Martin Fischer

  • How can I add metadata to iWeb pages hosted on .mac?

    How can I add title/description/keyword metadata to my website?
    Is there an easy solution?
    I publish my site to my .mac account.
    Any direction would be appreciated. I work in the web marketing industry, so it bugs me not being able to add metadata to my site.
    Thanks!
    Macbook   Mac OS X (10.4.7)  

    So I find the folder: Welcome_files for example
    Then do I open up the Welcome.js file using text
    editor?
    When I add the metadata, then do I Save As and put
    the file back into the Welcome_files folder?
    Actually every page like Welcome has a Welcome.html file and then a folder "Welcome_files". The file you want to edit is the Welcome.html file. Not anything in the folder.
    Do I need to Publish again, or is that process
    automatic since the site is pulling from down from my
    iDisk?
    Nope don't publish again. That would just overwrite you changes again. Just save the file in the same place and you're done.
    Will I have to re-enter metadata every time that the
    page changes, or every time the site changes?
    Anytime iWeb thinks the page needs to be republished, your edited file will be overwritten.

  • Photoshop: How to save as a pdf and display description?

    The only other Photoshop I ever used was CS3, and when I clicked "print" it saved as a pdf first, and I could choose to make it display different metadata. That feature has been removed for all newer versions for some reason, and I have no idea how to do what I want to do.
    I need to save it as a pdf, and display the description/subject metadata under the photo. I can't find anything online on how to do this.

    BlazeHeatnix,
    Due to the current unavailability of clairvoyants and mind-readers in the forum, we respectfully request you supply sensible, complete details.
    Please understand that "CS5" does not clear up the issue of what version of Photoshop you are using.  "Photoshop CS5 12.0.1" would.
    A screen capture would be very helpful.
    Also, have you trued the Print command, then Save As PDF?
    BOILERPLATE TEXT:
    Note that this is boilerplate text.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster, who is not a Windows user).
    a screen shot of your settings or of the image could be very helpful too.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • Metadata Presets... Erratic behavior and how to?

    I often struggle with the Import presets. Seemingly only during Import one can make a new preset, and I do have cases of more than one identical named preset, because LR does not ignore trailing blanks in preset names (Ouuuu! Woof Woof!)
    But, how can edit exiting preset of Metadata?
    When I have images without any EXIF in them, because come from celluloid old good film, how can declare a camera and lens? I tried to crack this, but neither experiments nor the manual were of help.
    Thomas

    "When I have images without any EXIF in them, because come from celluloid old good film, how can declare a camera and lens? I tried to crack this, but neither experiments nor the manual were of help."
    Metadata can contain many sections, where EXIF section is just one of them. Another one (you may be interested of) is Makernote section -here's where lens data is written.
    Now, you cannot just enter some lens data -Makernote section must be there (in image file) first. Bad news: Makernote is normally written into image file by camera only. Good news: it is possible to "copy" Makernote from one file to another. Once you have Makernote in your image file, you can edit lens data at will. I've tried that and it works.
    About camera description in metadata... just write/create "Model" tag in XMP section, where you describe your camera. If using ExifTool (which I highly recommend), you write:
    exiftool -xmp:model="My SLR Camera" MyScan.tif
    -simple as that.
    Bogdan

  • Keys and Join description at physical layer does not reflect in BI Answer?

    Hi All ,
    While creating a RPD , the description about keys and join information using
    description and hint property which we define at physical layer, those informations do not reflect BI Answer when i query to metadata dictionary.
    Any ideas in this regard?
    -- Ashish

    Hi All ,
    Here i give little bit more description what i did.
    (1) I created a RPD and gave some description about Foreign Keys and using hint a gave some description about Physical joins.
    (2) After then using utilities I generated the Metadata Dictionary.
    (3) Now after restarting of services when i query to Metadata Dictionary using BI Answer , i am not able to see those descriptions. Rest of the information like table level and column level descriptions i am able to see.
    Is there any way to get these descriptions or metadata dictionary does not keep descriptions for keys and joins?
    Any ideas in this regard??
    --Ashish                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • CS3 to CS4 Metadata population script incompatibility?

    Hello Ladies and Gentlemen,
    I was looking to probe your collective expertise on a question I have run across.  I have been notified of a, theoretically, wonderful script that promises to populate the title/description/keywords metadata info of a document with text from said document (based on paragraph styles applied to the text).  For reasons beyond my humble grasp this script seems to no longer function properly in CS4.  Perhaps a specific call's wording has changed between versions, or perhaps the entire syntax of the script no longer applies. 
    //Set to 4.0/CS2 scripting object model
    app.scriptPreferences.version = 4.0;
    myDocument = app.activeDocument; //work on active document
    //===== Remove/Replace certain characters such as paragraph markers =====\\
            function replaceByCode(myMetaIn, myTotalCharacters)
               myCharCodeList = new Array(
                    "13", // Paragraph Marker
                    "10", // Soft Return
                myCharReplacementList = new Array(
                   "", // Remove paragraph markers
                   "", // Remove soft returns
                  var myTotalSpecialCharacters = myCharCodeList.length;
                  var myMetaOut = myMetaIn;
                  for (z = myTotalSpecialCharacters; z >= 0; z--)
                        for (y = myTotalCharacters; y >= 0; y--)
                             myCharacterCode = myMetaIn.charCodeAt(y) + "";
                              if (myCharacterCode == myCharCodeList[z])
                                    myCharacter = myMetaIn.charAt(y);
                                     myMetaOut = myMetaOut.replace(myCharacter, myCharReplacementList[z]);
                            return (myMetaOut)
    //===== Search for text with the paragraph style "title" =====\\
    var myTitle = " ";
    try{
        app.findPreferences = null;
        app.changePreferences = null;
        var titleSearch = myDocument.search(undefined,false,false,undefined, {appliedParagraphStyle:'title'});
        for (i = 0; i < titleSearch.length; i++)
                myTitleParagraph = titleSearch[i];
        myTitle = myTitleParagraph.contents;
        myTitleTotalCharacters = myTitle.length;
        myTitle = replaceByCode(myTitle, myTitleTotalCharacters);
        catch(e){}
    //===== Search for text with the paragraph style "description" =====\\   
    var myDescription = " ";
    try{
        app.findPreferences = null;
        app.changePreferences = null;
        var descriptionSearch = myDocument.search(undefined,false,false,undefined, {appliedParagraphStyle:'description'});
        for (i = 0; i < descriptionSearch.length; i++)
                myDescriptionParagraph = descriptionSearch[i];
        myDescription = myDescriptionParagraph.contents;
        catch(e){}
    //===== Search for text with the paragraph style "keywords" =====\\       
    var myKeywords = " ";
    try{
        app.findPreferences = null;
        app.changePreferences = null;
        var keywordsSearch = myDocument.search(undefined,false,false,undefined, {appliedParagraphStyle:'keywords'});
        for (i = 0; i < keywordsSearch.length; i++)
                myKeywordsParagraph = keywordsSearch[i];
        myKeywords = myKeywordsParagraph.contents;
        myKeywords = myKeywords.split(","); // Create an array from the string. Keywords should be seperated by a comma.
        catch(e){}
    //===== Assign the text found from searching to XMP fields =====\\   
    myDocument.metadataPreferences.documentTitle = myTitle;
    myDocument.metadataPreferences.description = myDescription;
    myDocument.metadataPreferences.keywords = myKeywords;
    This error is returned when the script is run verbatim, but that seems to be solely because it thinks the "keywords" paragraph style is applied to no text.  Removing the keyword sections of the script causes it to run without error, but writes no data to the XMP fields.
    Any information you have or enlightenment you may provide would be helpful and appreciated.

    The script failed to find any paragraphs in the paragraph style "keywords" -- does your test document actually have any?
    Dave

  • BWF Import, not quite there yet...

    Hi there,
    I just downloaded the 5.1.2 update and was quite excited by the new (at last) BWF import feature. So the first thing I tried was to import some BWF files to see how it works. The files I have at hand are BWF, Polyphonic files, with 24fps Timecode. They were originated with an Aaton Cantar and polyphoniced' using Majax.
    I have to say that I'm not impressed:
    - The resulting Clip in the browser has a 25fps TimeCode. It cant' be changed.
    - The sc/take info, as well as the info typed in by the sound recordist don't appear in any of the columns.
    Am I doing anything wrong?
    Pierre

    Hi Pierre,
    I think unfortunately the BWF support announcement makes it sound a little better than it actually is. Its a good step, but there is by no means full BWF support in 5.1.2. For a really detailed intro to what's going on here is a post from Andreas Kiel (who develops BWF2XML):
    Hi all,
    One of the new features in Final Cut Pro 5.1.2 will be enhanced QT metadata support and
    support for the Broadcast Wave Format. (More informations about BWF can be found at the
    EBU Website.)
    As I did one of the (living) applications to integrate BWF into a FCP workflow I got a lot of
    questions from users and potential user about the "BWF compatibility" feature in FCP 5.1.2
    and how BWF2XML compares to the options in FCP.
    Some additional information about uncompressed/HD/film workflow and audio can be
    found at:
    http://www.apple.com/finalcutstudio/resources/white_papers/L328398A-
    USL328398A_HD_Workflow_FilmTV_FCPwp.pdf#search=%22L328398A-
    USL328398A_HD_Workflow_FilmTV_FCPwp.pdf%22
    Introduction:
    Beside all the other improvements with this new version of Final Cut Pro, one of the big
    improvements is that this new version makes extensive use of all the new QuickTime
    structures, allowing QuickTime metadata access and tc64 timecode (which is audio
    timecode). This last feature has been tested with a lot of different files, and nearly all files
    with tc64 information showed up correctly.
    The QuickTime metadata access will allow third parties to create QuickTime components
    with metadata - like the DPX/Cineon component from Bob Monaghan at GlueTools, the
    first of it's kind. This will also allow other companies to create a QuickTime components
    for MXF, IMX etc., and you'll be able to drag a MXF (or something like that) to the timeline
    with all the metadata included. So stay tuned for future announcements from third parties.
    tc64 audio timecode is something new in QuickTime:
    QuickTime is interpreting the BWAV header entry for the samples after midnight - most of
    you (at least those who are interested) can already check that: just open a BWF file in
    QuickTime Player Pro (7.1.3), press cmd-J and enable the TC track. You'll see the samples
    after midnight (don't save when closing the file).
    Final Cut Pro now makes use of this this QuickTime feature, and creates a timecode based
    on the tc64 samples after midnight and the sampling rate. This will result in seconds after
    midnight. The seconds can be converted to timecode by extracting hours, minutes,
    seconds and partial seconds, where partial seconds will be converted to frames based on
    the timecode base.
    The timecode base is complicated to figure out, since mostly it's not written to the header
    of the BWF file. And even if it is, QuickTime won't interpret it, since it is nearly impossible
    to automatically interpret all the ways the header is set up. There maybe other information
    in the header like reel, scene, take, note etc. However, this currently won't be interpreted
    by QuickTime as well. As opposed to a QuickTime timecode track, reel information is not
    kept in a tc64 track. So if QuickTime doesn't interpret it, Final Cut Pro can't either, and for
    the timecode, it will probably take the current timecode base of the project, which might
    differ from the original sound recording.
    With audio, there are also things like 29.97 NDF (which is not available in Final Cut Pro
    right now), and the samples after midnight also may be based on either real world seconds
    or NTSC seconds. Plus, there may be playback instructions in coding history. All of this is
    quite a complicated thing, and it will be left to the user to think about the setup in
    advance.
    File formating and appearance:
    BWF can show up in either polyphonic or multi-mono format. Both of these formats do
    have advantages and disadvantages.
    Polyphonic files are easy to handle. As all tracks are included in one file, they are faster on
    transfer from the audio harddisk recorder than mono files. Polyphonic files are also easy
    to import with the new Final Cut Pro feature. They have the disadvantage that removing
    unused tracks is difficult when it comes to exchange with other audio workstations or
    when using XML and reconnect, since they are interleaved.
    Mono files take longer when transfer from the audio harddisk recorder since the de-
    interleave has to be done prior to transfer. They also have the disadvantage that they can
    only be imported as discrete files, and need to be connected "channel by channel" within
    Final Cut Pro, which makes the process much more tedious. The big advantage of using
    mono files though is, that you can remove (or even add) channels and will have no
    problems when doing an interchange with DAWs, via XML, or with content management
    systems. The channel files can be handled by Media Manager up to a certain extent when
    left untouched, or fully when converted to a .mov format.
    More detail about the two kinds of timecode tracks:
    The QuickTime timecode tracks we are used to working with behave, let's say, just like
    another "movie" track, so you can step thru frames.
    tc64 reads the timestamp of an BWF audio file - this happens only once, so it behaves like
    a long frame, which can't be stepped thru by samples, frames, seconds etc. It's just one
    frame when activated - even though it shows the samples during playback.
    The QuickTime timecode track forces a file into a specified playback behavior, which is
    user-defined, and even can be changed within Final Cut Pro (within certain limits). It can
    also be used as AUX TC in synched clips.
    tc64, when used in QuickTime/Final Cut Pro, just gives a reference which relies on the
    sample rate to get the time. To change the playback behavior, you need to change the
    sample rate "virtually". This means that the file's samples are not changed but the "this file
    is sampled at" description will be changed. This can be done with a third party application
    outside of FCP (this is our current info about changing playback, and it might be wrong).
    As said above, with QuickTime timecode there is timecode timebase and reel info, with
    tc64 there can't be timecode timebase and reel info.
    What about bringing BWF2XML and the new QuickTime/Final Cut Pro features together?
    This should work cool, since Final Cut Pro 5.1.2 will accept the tc64 for first time ever, and
    BWF2XML can supply you or Final Cut Pro with the additional metadata without converting
    to QuickTime timecode (though there are still a lot of advantages doing that).
    But it needs some additional steps done with BWF2XML, like changing playback settings to
    apply pull-up or pull-down. If that's done, BWF support in Final Cut Pro will be exceptional
    compared to other NLEs, and conversion will be lightning fast - even if there is no direct
    import plug-in for this "combined" import. With the new XML version 3, things may
    become easier and BWF2XML may work as a pseudo importer plug-in.
    Conclusion:
    So why do I write all these mostly "negative" things (about FCP)?
    Pretty simple, since working with these relatively new formats and devices isn't that simple
    for most video and postpro people.
    Apple made another big step into the tapeless future, as well as some of you who made
    this step using "new" devices and formats. With new devices there is always the problem to
    establish something like a "common sense" for set up and workflow, which doesn't exist
    right now.
    So if a BWF import into Final Cut Pro would give you an erroneous result, don't blame
    Apple and don't start threads about blaming Apple, they made the above step, and they
    too will probably run into similar problems as any of the other companies - like me - who
    are dealing with BWF, machine setup, file setup and naming as well as user setups.
    Other companies just restrict, maybe by the amount of channels, maybe by the titles/
    names of metadata entries, maybe by kicking out metadata entries - and still the other
    companies look to be a little bit ahead.
    Regards
    Andreas
    http://www.spherico.com/filmtools
    Hope that helps,
    Mark

  • Adding a Service to CAF Tile

    I've followed the steps in the docs and even looked at the StockData example provided but cannot seem to get it working. I get the following error:
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/tiles/SnapshotTile/SnapshotTile.sw f
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/services/HistorianService/theHisto rianService.gxml
    Created url: http://localhost:4502/content/mosaic/catalogs/Historian/interfaces/HistorianInterfaceLibra ry/HistorianInterfaceLibrary.swf
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/tiles/SnapshotTile/SnapshotTile.sw f
    Before resolve: http://localhost:4502/content/mosaic/catalogs/Historian/tiles/SnapshotTile/SnapshotTile.sw f
    [SWF] /content/mosaic/catalogs/Historian/interfaces/HistorianInterfaceLibrary/HistorianInterfac eLibrary.swf - 2,497 bytes after decompression
    Failure in Loader: Error: Error #2036: Load Never Completed. URL: http://localhost:4502/Historian/interfaces/HistorianInterfaceLibrary/HistorianInterfaceLib rary.swf
    Failure in Loader: Error: Error #2036: Load Never Completed. URL: http://localhost:4502/Historian/interfaces/HistorianInterfaceLibrary/HistorianInterfaceLib rary.swf
    Below is the code as well as the configuration files:
    IHistorianService.as
    package cafe.historian.services
              import mx.collections.IList;
              [Expose]
              public interface IHistorianService
                        function getSnapshots(userid:String):IList;
    HistorianService.as
    package cafe.historian.services.impl
              import cafe.historian.services.IHistorianService;
              import mx.collections.ArrayCollection;
              import mx.collections.IList;
              [Expose(catalog="Historian", library="HistorianInterfaceLibrary", scope="singleton")]
              public class HistorianService implements IHistorianService
                        public function HistorianService()
                        public function getSnapshots(userid:String):IList{
                                  var test:ArrayCollection = new ArrayCollection();
                                  test.addItem("one");
                                  test.addItem("two");
                                  return test;
    Historian.axml
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <!-- Copyright 2011 Adobe Systems Incorporated. All rights reserved. The original
    version of this material may be obtained from Adobe Systems Incorporated. -->
    <app:Application xmlns:app="http://ns.adobe.com/Mosaic/Application/1.0/" xmlns:catalog="http://ns.adobe.com/Mosaic/Catalog/1.0/" xmlns:ct="http://ns.adobe.com/Mosaic/CommonTypes/1.0/" xmlns:tile="http://ns.adobe.com/Mosaic/Tile/1.0/" xmlns:view="http://ns.adobe.com/Mosaic/View/1.0/" label="EMS Historian" name="Historian">
        <ct:Metadata>
            <ct:Description/>
        </ct:Metadata>
        <!-- Specifies a default panel or view to use when a user adds a new panel or
        view to the composite application (if permitted). Specify a default directly,
        or reference one from a composite application catalog. Referenced default
        panels and views override the composite application defaults. Note: You can
        specify only one panel and view in the app:Defaults section, but you can
        specify any number of catalog:CatalogReference children. -->
        <app:Defaults>
            <view:Panels>
                <view:Panel allowContentDelete="true" height="100%" label="Default Panel" tileChrome="full" width="100%">
                    <view:Layout name="HorizontalLayout" numColumns="2"/>
                </view:Panel>
            </view:Panels>
        </app:Defaults>
        <!-- Provide a global context containing values for use across entire
        application.
        <ct:Context>
            <ct:Data key="myApplicationContext" type="string" value="default value" />
        </ct:Context>
        -->
        <!-- A named context is useful for partition of a set of context values
        to a subsection of the application.
        <app:NamedContexts>
            <ct:Context name="basictypes">
                <ct:Data key="aSimpleString" type="string" value="sample string"/>
                <ct:Data key="aBoolean" type="boolean" value="true"/>
                <ct:Data key="anInteger" type="number" value="2011"/>
                <ct:Data key="aDate" type="date" value="2011-11-01T19:00:00-05:00"/>
                <ct:Data key="aNull" type="null" />
            </ct:Context>
        </app:NamedContexts>
        -->
        <!-- Specifies the runtime content for a composite application. The order of
        the elements affects the appearance in the application user interface. You
        can specify only one app:Shell or app:ShellReference element as a child of
        app:Application. -->
        <app:Shell label="Sample Shell" name="SampleShell"><!-- ShellStyle -->
            <!-- Specifies a reference to a composite application catalog. Catalogs
            contain composite application assets. The name attribute creates a
            shorthand reference to the catalog, which is stored on the Experience
            Server. -->
            <catalog:CatalogReference name="${catalog}" uri="${catalog}"/>
            <!-- Specifies a container to display views in the application user
            interface. The order of elements affects the appearance of the user
            interface. You can include only one view:ViewManager element as a child
            of the app:Shell element. The default skin for the view:ViewManager
            element provides a set of tab buttons to switch between views in the
            application, as well as an Add button, and an option menu. -->
            <view:ViewManager height="100%" width="100%">
                <view:View name="Research"
                                              height="100%" width="100%"
                                              label="Research"
                                              allowContentDelete="false">
                    <view:Panel allowContentDelete="false"
                                                  label="Analysis"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" ><!-- FullPanelTileStyle -->
                     <view:Layout name="HorizontalLayout"/> 
                        <tile:TileReference catalog="${catalog}"
                                      name="ResearchTile" optional="false" width="100%" height="100%" /><!-- TileStyle -->
                    </view:Panel>
                </view:View>
                <view:View label="Snapshots" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Snapshots"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="SnapshotTile" optional="false" width="100%" height="100%">
                            <tile:Properties>
                                      <tile:Property name="historianService">
                                                <tile:ServiceReference catalog="${catalog}" library="HistorianService" name="theHistorianService"></tile:ServiceReference>
                                      </tile:Property>
                            </tile:Properties>
                     </tile:TileReference>
                          </view:Panel>
                </view:View>
                <view:View label="Views" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Views"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="ViewsTile" optional="false" width="100%" height="100%"/>
                          </view:Panel>
                </view:View>
                <view:View label="Reports" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Reports"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="ReportsTile" optional="false" width="100%" height="100%"/>
                          </view:Panel>
                </view:View>
                <view:View label="Admin" height="100%" width="100%">
                          <view:Panel allowContentDelete="false"
                                                  label="Admin"
                                                  height="100%" width="100%"
                                                  styleName="PanelInShellStyle" >
                     <view:Layout name="HorizontalLayout"/> 
                     <tile:TileReference catalog="${catalog}"
                            name="AdminTile" optional="false" width="100%" height="100%"/>
                          </view:Panel>
                </view:View>
            </view:ViewManager>
        </app:Shell>
    </app:Application>
    Historian.cxml
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <catalog:Catalog xmlns:catalog="http://ns.adobe.com/Mosaic/Catalog/1.0/" xmlns:ct="http://ns.adobe.com/Mosaic/CommonTypes/1.0/" xmlns:tile="http://ns.adobe.com/Mosaic/Tile/1.0/" xmlns:view="http://ns.adobe.com/Mosaic/View/1.0/" label="EMS Historian" name="Historian">
        <!-- Identifying description for this catalog. -->
        <ct:Metadata>
            <ct:Description>All content for the EMS Historian</ct:Description>
        </ct:Metadata>
        <!-- Specifies a list of tiles (tile:TileClass elements) contained within
        this catalog.  -->
        <tile:TileClassList>
                <!--  Remove the commenting from this tile:TileClass element to
                include a reference to a tile in this catalog. Within a tile:TileClass
                element, a tile:Content child element specifies tile content using the
                following attributes:
                    uri: A reference, either to absolute or relative, to the content's
                    location on a server.
                    contentType: The MIME type for the tile's content. For Flex tiles,
                    specify "application/x-shockwave-flash", and for HTML tiles
                    specify "text/html".
                    loadAs: For Flex tiles, if this value is "module", at run time the
                    tile loads as a Flex module. If the value is "default" or omitted,
                    at runtime the Flex tile loads as a SWF application. 
                    IMPORTANT: You must compile module tiles using one of the Flex SDKs
                    included in the Adobe Experience Services Tooling for Flash Builder
                    installation. Flex modules are similar to Flash Runtime Shared
                    Libraries (RSLs) in that they separate code from an application
                    into separately loaded SWFs. For more information on modular
                    applications, see "Modular applications overview" in the Flex
                    Developer's Guide.
            <tile:TileClass
                name="SampleTile"
                label="Sample Tile"
                width="600" height="400"
                fitContent="true">
                <ct:Metadata>
                    <ct:Description>sample description</ct:Description>
                </ct:Metadata>
                <tile:Content
                    uri="${catalogURL}/tiles/SampleTile/SampleTile.swf"
                    contentType="application/x-shockwave-flash"
                    loadAs="default" />
            </tile:TileClass>
            -->
                        <tile:TileClass fitContent="true" height="100%" label="ResearchTile" loadPolicy="auto" name="ResearchTile" width="100%">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/ResearchTile/ResearchTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="ViewsTile" loadPolicy="auto" name="ViewsTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/ViewsTile/ViewsTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="SnapshotTile" loadPolicy="auto" name="SnapshotTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                <tile:Depends>
                          <tile:Interface interfaceName="cafe.historian.services.IHistorianService" library="HistorianInterfaceLibrary"/>
                </tile:Depends>
                <tile:Properties>
                          <tile:Property name="historianService" type="cafe.historian.services.IHistorianService"/>
                </tile:Properties>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/SnapshotTile/SnapshotTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="ReportsTile" loadPolicy="auto" name="ReportsTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/ReportsTile/ReportsTile.swf"/>
                        </tile:TileClass>
                        <tile:TileClass fitContent="true" height="300" label="cafe.historian.tiles.admin.AdminTile" loadPolicy="auto" name="AdminTile" width="600">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                                  <tile:Content contentType="application/x-shockwave-flash" loadAs="default" uri="${catalogURL}/tiles/AdminTile/AdminTile.swf"/>
                        </tile:TileClass>
              </tile:TileClassList>   
        <!-- Specifies a list of interface libraries (tile:InterfaceLibrary elements)
        contained within this catalog -->
        <tile:InterfaceLibraryList>
            <!--  Remove the commenting from this tile:InterfaceLibrary element to
            include a reference to an interface library in this catalog. Within a
            tile:InterfaceLibrary element, a tile:InterfaceList child element
            specifies a list of interfaces (tile:Interface elements) to include
            in the catalog. For each tile:Interface element, specify the interface
            class using the following attribute:
                interfaceName: A fully-qualified package and class reference to class
                that defines a service interface.
            <tile:InterfaceLibrary name="SampleInterfaceLibrary">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                 <tile:InterfaceList>                 
                    <tile:Interface interfaceName="com.adobe.adep.samples.services.sampleservice.ISampleService"/>                
                 </tile:InterfaceList>
             </tile:InterfaceLibrary>
             -->        
                   <tile:InterfaceLibrary name="HistorianInterfaceLibrary">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                      <tile:InterfaceList>
                    <tile:Interface interfaceName="cafe.historian.services.IHistorianService"/>
                </tile:InterfaceList>
            </tile:InterfaceLibrary>
        </tile:InterfaceLibraryList>   
        <!-- Specifies a list of service libraries (tile:ServiceLibrary elements)
        contained within this catalog. -->
         <tile:ServiceLibraryList>
              <!--  Remove the commenting from this tile:ServiceLibrary element to
              include a reference to a service library in this catalog. Within a
              tile:ServiceLibrary element, a tile:ServiceClassList child element
              specifies a list of service classes (tile:SeviceClass elements) to
              include in the catalog. For each tile:ServiceClass element, specify a
              service using the following attributes of the tile:Content child
              element:
                  uri: A reference, either to absolute or relative, to the content's
                  location on a server.
                  contentType: The MIME type for the tile's content. For service
                  libraries specify "application/xml".
              <tile:ServiceLibrary name="SampleService">
                <ct:Metadata>
                    <ct:Description/>
                 </ct:Metadata>
                 <tile:ServiceClassList>                
                    <tile:ServiceClass name="SampleService">
                        <tile:Content
                        uri="${catalogURL}/services/SampleService/SampleService-com-adobe-adep-samples-services-s ampleservice-impl.gxml"
                        contentType="application/xml"/>
                    </tile:ServiceClass>               
                 </tile:ServiceClassList>            
             </tile:ServiceLibrary>        
             -->
                        <tile:ServiceLibrary name="HistorianService">
                <ct:Metadata>
                    <ct:Description/>
                </ct:Metadata>
                      <tile:ServiceClassList>
                    <tile:ServiceClass className="cafe.historian.services.impl.HistorianService" name="theHistorianService" scope="singleton">
                    <tile:Implements>
                              <tile:Interface interfaceName="cafe.historian.services.IHistorianService" library="HistorianInterfaceLibrary"/>
                    </tile:Implements>
                    <tile:Content contentType="application/xml" uri="${catalogURL}/services/HistorianService/theHistorianService.gxml"/>
                    </tile:ServiceClass>
                          <tile:ServiceClass name="HistorianService">
                        <tile:Content contentType="application/xml" uri="${catalogURL}/services/HistorianService/HistorianService-cafe-historian-services-imp l.gxml"/>
                    </tile:ServiceClass>
                </tile:ServiceClassList>
            </tile:ServiceLibrary>
        </tile:ServiceLibraryList>
        <!-- Specifies a list of style sheets (view:StylesheetClass elements) contained
        within this catalog -->
        <view:StylesheetClassList>
            <!--  Remove the commenting from this view:StylesheetClass element to
            include a style sheet reference in this catalog. Include a separate
            view:StylesheetClass element for each style sheet you include in the
            catalog. Within each view:StylesheetClass element, specify the style sheet
            content using the following attributes of the view:Content child element:
                uri: A reference, either to absolute or relative, to the content's
                location on a server.
                contentType: The MIME type for the style sheet content. For Flex
                tiles, specify "application/x-shockwave-flash", and for HTML tiles
                specify "text/css".
            <view:StylesheetClass name="CafeMosaicTheme">
                <ct:Metadata>
                    <ct:Description>An alternative way to navigate using a ComboBox.</ct:Description>
                </ct:Metadata>
                <view:Content contentType="application/x-shockwave-flash" uri="${catalogURL}/stylesheets/CafeMosaicTheme/CafeMosaicTheme.swf"/>
            </view:StylesheetClass>
           -->
        </view:StylesheetClassList>   
        <!-- Specifies a list of panels (view:PanelClass elements) contained within
        this catalog -->
        <view:PanelClassList>
            <!--  Remove the commenting from this view:PanelClass element to include
            a reference to a panel in this catalog. Include a separate view:PanelClass
            element for each panel you include in the catalog. Within a view:PanelClass
            element, a view:Content child element specifies information for a panel
            using a view:Panel child element. For each view:Panel child element,
            specify the panel information using the following attributes:
                name: A unique name for the panel used to reference it from within the
                catalog.
                label: Descriptive text that displays as the panel title in the user
                interface of the composite application.
                tileChrome: Sets the default user interface for the panel. Values may
                be "none", "title" or "full". If the value is "full", then there is
                chrome on the panel which displays the title (label) and allows the
                panel to be moved, potentially deleted (if permitted), and resized.
                If the value is "title", the chrome is the same as for "full" without
                the ability to resize. If the value is "none", then there is no
                chrome on the panel, which means no title (label), and no user
                interface for for manipulating the panel.
                allowContentDelete: Specifies whether users can delete this panel at
                run time when the "chrome" attribute is set to "full" or "title".
                Values may be "true" or "false".
            Each view:Panel element may contain one or more tile:TileReference child
            elements that specify tiles to display within the panel at run time. You
            can override default tile attribute values here to customize the tile's
            appearance when referenced within this panel:
                catalog: Reference to the catalog that contains the tile.
                name: The name of the tile specified in the catalog.
                label: (override) The label of the tile.
                chrome: (override) Sets the user interface for the tile. Values may
                be "none", "title" or "full". If the value is "full", then there is
                chrome on the tile, which displays the title (label) of panels
                contained within the tile, and the tile allows for the panel to be
                moved, potentially deleted (if permitted), and resized. If the value
                is "title", the chrome is the same as for "full" without the ability
                to resize. If the value is "none", then there is no chrome on the
                tile, which means no panel title (label), and no user interface for
                for manipulating the panel.
                fitContent: (override) Specifies whether tile content should be
                automatically resize to fit the container. Values may be "true" or
                "false".
            <view:PanelClass name="SamplePanel">
                <ct:Metadata>
                    <ct:Description />
                </ct:Metadata>
                <view:Content>           
                    <view:Panel name="SamplePanel" label="Sample Panel"
                        tileChrome="true" allowContentDelete="true" width="100%" height="100%">
                        <view:Layout name="HorizontalLayout" />
                        <tile:TileReference
                            catalog="${catalog}" name="SampleTile" label="Sample Tile" width="100%" height="50%"
                            chrome="full" fitContent="true"/>
                    </view:Panel>
                </view:Content>
            </view:PanelClass>
            -->
        </view:PanelClassList> 
        <!-- Specifies a list of views contained within this catalog -->
        <view:ViewClassList>
            <!--  Remove the commenting from this view:ViewClass element to include a
            reference to a view in this catalog.
            Include a separate view:ViewClass element for each view you include in the
            catalog. Within a view:ViewClass element, a view:Content child element
            specifies information for a panel using a view:View child element. For
            each view:View child element, specify the panel information using the
            following attributes:
                name: A unique name for the view used to reference it from within
                the catalog.
                label: Descriptive text that displays as the panel title in the
                user interface of the composite application.
            Each view:View element may contain one or more view:PanelReference child
            elements that specify panels to display within the view at run time. You
            can override default panel attribute values here to customize the panel's
            appearance when referenced within this view:
                catalog: Reference to the catalog that contains the panel.
                name: The name of the panel specified in the catalog.
            <view:ViewClass label="Sample View" name="SampleView">
                <ct:Metadata>
                    <ct:Description>Sample View</ct:Description>
                </ct:Metadata>
                <view:Content>
                    <view:View name="SampleView" width="100%" height="100%"
                        label="Sample View">
                        <catalog:CatalogReference name="Default"
                            uri="Default" />
                        <view:PanelReference catalog="Default" name="SamplePanel" />
                    </view:View>
                </view:Content>
            </view:ViewClass>
            -->
        </view:ViewClassList>
    </catalog:Catalog>
    SnapshotTile.mxml (snippet)
    private var watcher:ChangeWatcher;
    [Bindable]
    [Consume(catalog="Historian", library="HistorianInterfaceLibrary")]
    public var historianService:IHistorianService;
    protected function _preinitializeHandler(event:FlexEvent):void
              this.addEventListener( AnnotationParseEvent.COMPLETE, _annotationParseEventCompleteHandler );
              watcher = ChangeWatcher.watch(this, "historianService", onGotService, false, true);
              protected function onGotService(e:PropertyChangeEvent):void
              if(historianService)
                        var test:ArrayCollection = historianService.getSnapshots("jonphill") as ArrayCollection;
                        trace("Using service, item 1: " + test.getItemAt(0));
                        trace("Using service, item 2: " + test.getItemAt(1));
    I've also attached two screenshots showing the project structure in FB and CRX.
    Any help here would be great as I'm pulling my hair out at this point!
    Thanks

    There's not an actual space in the error, it just looks that way when I pasted the text into the post.
    For some additional information, I've tried going through the tutorial here (http://www.youtube.com/ADEPDevelopers#p/c/DF68F4464D4EF4E0/4/klNspQvfVMc) and here (http://help.adobe.com/en_US/enterpriseplatform/10.0/AEPDeveloperGuide/WS989a722fbb254cbe-6 f13dcd01304cbb1ac4-8000.html), however, neither one goes through the full steps of adding the Service to the axml and cxml files which is where I'm probably having trouble.
    I've also looked at the StockMosaicService sample included with ADEP and tried mimicking it but with no luck. I had expected the ADEP tooling in Flash Builder to handle all this for me but it doesn't appear to be working properly now.

  • Is it possible to remove the 'soap12' namespace from the WSDL for basicHttpBinding endpoints (i.e soap 1.1 clients)?

    Hello,
    We want to import the WSDL from a running WCF service endpoint (which is using basic HTTP binding) in order to implement the same web service interface in a Lotus Notes application. Unfortunately the proxy generator for Lotus Notes doesn't like the particular dialect of WSDL that our WCF service is exposing, in particular it throws a wobbly when it sees
    xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/.
    Even though soap1.2 isn't being used, the basic http binding is leaving this reference in the wsdl and Lotus Notes seems to think this is a SOAP 1.2 WSDL file even though I know it's a SOAP 1.1 compatible file.
    In order to get around this I'm using disco.exe to pull the wsdl files down locally, manually edit the files to remove this unused name space and then edit all the schema import locations to convert lines such as http://localhost:7780/MEX?xsd=xsd0 to lines such as file://\wsdl\MEX.xsd etc...
    Is there a simple setting somewhere that will remove that 'soap12' fragment from the wsdl? It's a bit of a pain because we are in a development phase and so the WSDL isn't completely stable at the moment and is changing frequently which requires this manual editing stage.
    Thanks
    Paul.

    The following method works correctly for me:
    public class Soap11WsdlExporter : WsdlExporter
        public override MetadataSet GetGeneratedMetadata()
            var metadataSet = base.GetGeneratedMetadata();
            foreach (var metadataSection in metadataSet.MetadataSections)
                var description = metadataSection.Metadata as System.Web.Services.Description.ServiceDescription;
                if (description != null)
                    var namespaces = description.Namespaces.ToArray();
                    var newNamespaces = new XmlSerializerNamespaces();
                    foreach (var ns in namespaces)
                        if (ns.Name.ToLower() != "soap12")
                            newNamespaces.Add(ns.Name, ns.Namespace);
                    description.Namespaces = newNamespaces;
            return metadataSet;
    public class MyServiceHostFactory : ServiceHostFactory
        protected override ServiceHost CreateServiceHost(Type serviceType, Uri[] baseAddresses)
            ServiceHost serviceHost = new ServiceHost(serviceType, baseAddresses);
            var useSoap11 = true;
            //We only removing SOAP12 namespace only if all the bindings use SOAP11.
            foreach(var endPoint in serviceHost.Description.Endpoints)
                useSoap11 &= endPoint.Binding.MessageVersion.Envelope == EnvelopeVersion.Soap11;
            if (useSoap11)
                var behavior = serviceHost.Description.Behaviors.Find<ServiceMetadataBehavior>();
                if (behavior != null)
                    behavior.MetadataExporter = new Soap11WsdlExporter();
            return serviceHost;
    Hope this helps
    Another Paradigm Shift
    http://shevaspace.blogspot.com

  • Flex sdk incremental build will lose swc information

    I have a mxmlc ant task job like this
            <mxmlc 
            file="${trunk_dir}/main/src/main.mxml"
            output="${local_tmp}/app/bin/main.swf"
                      >    
                <load-config filename="${basedir}/flex-config-sea.xml"/>
                <source-path path-element="${FLEX_HOME}/frameworks"/>
            </mxmlc>
    in flex-config-sea.xml I put this in for incremental compile and swc build
          <include-libraries>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/Mate_08_9.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/xprogress.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/component.swc</library>
          </include-libraries>
          <incremental>true</incremental>
    the first time build is ok, but the second time after I changed one single file, the output is
    [mxmlc] Loading configuration file /opt/cruisecontrol-bin-2.8.4/projects/cc/flex-config-sea.xml
        [mxmlc] Recompile: /opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/src/C.as
        [mxmlc] Reason: The source file or one of the included files has been updated.
        [mxmlc] Files changed: 1 Files affected: 0
        [mxmlc] Required RSLs:
        [mxmlc]     textLayout_2.0.0.232.swz with 1 failover.
        [mxmlc]     framework_4.6.0.23201.swz with 1 failover.
        [mxmlc]     rpc_4.6.0.23201.swz with 1 failover.
        [mxmlc]     mx_4.6.0.23201.swz with 1 failover.
        [mxmlc]     spark_4.6.0.23201.swz with 1 failover.
        [mxmlc]     sparkskins_4.6.0.23201.swz with 1 failover.
        [mxmlc] /tmp/sea_local/app/bin/main.swf (426617 bytes)
    but the output swf is complaining lack of some swc when running, which didn't show up in the first time
    ReferenceError: Error #1065: Variable _shared_maps_GlobalMapWatcherSetupUtil is not defined.
              at global/flash.utils::getDefinitionByName()
              at shared.maps::GlobalMap()
              at main/_main_GlobalMap1_i()
              at main()
              at _main_mx_managers_SystemManager/create()
              at mx.managers.systemClasses::ChildManager/initializeTopLevelWindow()
              at mx.managers::SystemManager/initializeTopLevelWindow()
              at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::kickOff()
              at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::preloader_completeHandler()
              at flash.events::EventDispatcher/dispatchEventFunction()
              at flash.events::EventDispatcher/dispatchEvent()
              at mx.preloaders::Preloader/timerHandler()
              at flash.utils::Timer/_timerDispatch()
              at flash.utils::Timer/tick()
    this message normally shows up when there's no Mate_08_9.swc found at runtime. but this shouldn't happen.
    is there anyway to work around this? thanks a lot
    here is the full flex-config-sea.xml:
    <flex-config>
       <!-- benchmark: output performance benchmark-->
       <!-- benchmark usage:
       <benchmark>boolean</benchmark>
       -->
       <compiler>
          <!-- compiler.accessible: generate an accessible SWF-->
          <accessible>true</accessible>
          <!-- compiler.actionscript-file-encoding: specifies actionscript file encoding. If there is no BOM in the AS3 source files, the compiler will use this file encoding.-->
          <!-- compiler.actionscript-file-encoding usage:
          <actionscript-file-encoding>string</actionscript-file-encoding>
          -->
          <!-- compiler.allow-source-path-overlap: checks if a source-path entry is a subdirectory of another source-path entry. It helps make the package names of MXML components unambiguous.-->
          <allow-source-path-overlap>false</allow-source-path-overlap>
          <!-- compiler.as3: use the ActionScript 3 class based object model for greater performance and better error reporting. In the class based object model most built-in functions are implemented as fixed methods of classes.-->
          <as3>true</as3>
          <!-- compiler.compress usage:
          <compress>boolean</compress>
          -->
          <!-- compiler.context-root: path to replace {context.root} tokens for service channel endpoints-->
          <!-- compiler.context-root usage:
          <context-root>context-path</context-root>
          -->
          <!-- compiler.debug: generates a movie that is suitable for debugging-->
          <debug>false</debug>
          <!-- compiler.defaults-css-files usage:
          <defaults-css-files>
             <filename>string</filename>
             <filename>string</filename>
          </defaults-css-files>
          -->
          <!-- compiler.defaults-css-url: defines the location of the default style sheet. Setting this option overrides the implicit use of the defaults.css style sheet in the framework.swc file.-->
          <!-- compiler.defaults-css-url usage:
          <defaults-css-url>string</defaults-css-url>
          -->
          <!-- compiler.define: define a global AS3 conditional compilation definition, e.g. -define=CONFIG::debugging,true or -define+=CONFIG::debugging,true (to append to existing definitions in flex-config.xml) -->
          <!-- compiler.define usage:
          <define>
             <name>string</name>
             <value>string</value>
             <value>string</value>
          </define>
          -->
          <!-- compiler.enable-runtime-design-layers usage:
          <enable-runtime-design-layers>boolean</enable-runtime-design-layers>
          -->
          <!-- compiler.es: use the ECMAScript edition 3 prototype based object model to allow dynamic overriding of prototype properties. In the prototype based object model built-in functions are implemented as dynamic properties of prototype objects.-->
          <es>false</es>
          <extensions>
             <!-- compiler.extensions.extension usage:
             <extension>
                <extension>string</extension>
                <parameters>string</parameters>
             </extension>
             -->
          </extensions>
          <!-- compiler.external-library-path: list of SWC files or directories to compile against but to omit from linking-->
          <external-library-path>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/player/11.1/playerglobal.swc</path-element>
          </external-library-path>
          <fonts>
             <!-- compiler.fonts.advanced-anti-aliasing: enables advanced anti-aliasing for embedded fonts, which provides greater clarity for small fonts.-->
             <advanced-anti-aliasing>true</advanced-anti-aliasing>
             <!-- compiler.fonts.flash-type: enables FlashType for embedded fonts, which provides greater clarity for small fonts.-->
             <!-- compiler.fonts.flash-type usage:
             <flash-type>boolean</flash-type>
             -->
             <languages>
                <!-- compiler.fonts.languages.language-range: a range to restrict the number of font glyphs embedded into the SWF-->
                <!-- compiler.fonts.languages.language-range usage:
                <language-range>
                   <lang>string</lang>
                   <range>string</range>
                   <range>string</range>
                </language-range>
                -->
             </languages>
             <!-- compiler.fonts.local-font-paths usage:
             <local-font-paths>
                <path-element>string</path-element>
                <path-element>string</path-element>
             </local-font-paths>
             -->
             <!-- compiler.fonts.local-fonts-snapshot: File containing system font data produced by flex2.tools.FontSnapshot.-->
             <!-- compiler.fonts.managers: Compiler font manager classes, in policy resolution order-->
             <managers>
                <manager-class>flash.fonts.JREFontManager</manager-class>
                <manager-class>flash.fonts.BatikFontManager</manager-class>
                <manager-class>flash.fonts.AFEFontManager</manager-class>
                <manager-class>flash.fonts.CFFFontManager</manager-class>
             </managers>
             <!-- compiler.fonts.max-cached-fonts: sets the maximum number of fonts to keep in the server cache.  The default value is 20.-->
             <max-cached-fonts>20</max-cached-fonts>
             <!-- compiler.fonts.max-glyphs-per-face: sets the maximum number of character glyph-outlines to keep in the server cache for each font face. The default value is 1000.-->
             <max-glyphs-per-face>1000</max-glyphs-per-face>
          </fonts>
          <!-- compiler.headless-server: a flag to set when Flex is running on a server without a display-->
          <!-- compiler.headless-server usage:
          <headless-server>boolean</headless-server>
          -->
          <!-- compiler.include-libraries: a list of libraries (SWCs) to completely include in the SWF-->
          <!-- compiler.include-libraries usage:
          <include-libraries>
             <library>string</library>
             <library>string</library>
          </include-libraries>
          -->
          <include-libraries>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/Mate_08_9.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/xprogress.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/component.swc</library>
          </include-libraries>
          <!-- compiler.incremental: enables incremental compilation-->
          <!-- compiler.incremental usage:
          <incremental>boolean</incremental>
          -->
          <incremental>true</incremental>
          <!-- compiler.isolate-styles: enables the compiled application or module to set styles that only affect itself and its children-->
          <!-- compiler.isolate-styles usage:
          <isolate-styles>boolean</isolate-styles>
          -->
          <!-- compiler.keep-all-type-selectors: disables the pruning of unused CSS type selectors-->
          <!-- compiler.keep-all-type-selectors usage:
          <keep-all-type-selectors>boolean</keep-all-type-selectors>
          -->
          <!-- compiler.keep-as3-metadata: keep the specified metadata in the SWF-->
          <!-- compiler.keep-as3-metadata usage:
          <keep-as3-metadata>
             <name>string</name>
             <name>string</name>
          </keep-as3-metadata>
          -->
          <!-- compiler.keep-generated-actionscript: save temporary source files generated during MXML compilation-->
          <keep-generated-actionscript>false</keep-generated-actionscript>
          <!-- compiler.library-path: list of SWC files or directories that contain SWC files-->
          <library-path>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/flash-integration.swc</path-element>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/authoringsupport.swc</path-element>
             <path-element>/opt/flexsdk/4.6.0/frameworks/locale/{locale}</path-element>
          </library-path>
          <!-- compiler.locale: specifies the locale for internationalization-->
          <locale>
             <locale-element>en_US</locale-element>
          </locale>
          <!-- compiler.minimum-supported-version usage:
          <minimum-supported-version>string</minimum-supported-version>
          -->
          <!-- compiler.mobile: specifies the target runtime is a mobile device-->
          <mobile>false</mobile>
          <mxml>
             <!-- compiler.mxml.compatibility-version: specifies a compatibility version. e.g. -compatibility-version=2.0.1-->
             <!-- compiler.mxml.compatibility-version usage:
             <compatibility-version>version</compatibility-version>
             -->
             <!-- compiler.mxml.minimum-supported-version usage:
             <minimum-supported-version>string</minimum-supported-version>
             -->
             <!-- compiler.mxml.qualified-type-selectors usage:
             <qualified-type-selectors>boolean</qualified-type-selectors>
             -->
          </mxml>
          <namespaces>
             <!-- compiler.namespaces.namespace: Specify a URI to associate with a manifest of components for use as MXML elements-->
             <namespace>
                <uri>http://ns.adobe.com/mxml/2009</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mxml-2009-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>library://ns.adobe.com/flex/spark</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/spark-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>library://ns.adobe.com/flex/mx</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mx-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>http://www.adobe.com/2006/mxml</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mxml-manifest.xml</manifest>
             </namespace>
          </namespaces>
          <!-- compiler.omit-trace-statements: toggle whether trace statements are omitted-->
          <omit-trace-statements>true</omit-trace-statements>
          <!-- compiler.optimize: Enable post-link SWF optimization-->
          <optimize>true</optimize>
          <!-- compiler.preloader: Specifies the default value for the Application's preloader attribute. If not specified, the default preloader value is mx.preloaders.SparkDownloadProgressBar when -compatibility-version >= 4.0 and mx.preloaders.DownloadProgressBar when -compatibility-version < 4.0.-->
          <!-- compiler.preloader usage:
          <preloader>string</preloader>
          -->
          <!-- compiler.report-invalid-styles-as-warnings: enables reporting of invalid styles as warnings-->
          <!-- compiler.report-invalid-styles-as-warnings usage:
          <report-invalid-styles-as-warnings>boolean</report-invalid-styles-as-warnings>
          -->
          <!-- compiler.report-missing-required-skin-parts-as-warnings: Use this option to generate a warning instead of an error when a missing required skin part is detected.-->
          <!-- compiler.report-missing-required-skin-parts-as-warnings usage:
          <report-missing-required-skin-parts-as-warnings>boolean</report-missing-required-skin-parts-as-warnings>
          -->
          <!-- compiler.services: path to Flex Data Services configuration file-->
          <!-- compiler.services usage:
          <services>filename</services>
          -->
          <!-- compiler.show-actionscript-warnings: runs the AS3 compiler in a mode that detects legal but potentially incorrect code-->
          <show-actionscript-warnings>true</show-actionscript-warnings>
          <!-- compiler.show-binding-warnings: toggle whether warnings generated from data binding code are displayed-->
          <show-binding-warnings>true</show-binding-warnings>
          <!-- compiler.show-invalid-css-property-warnings: toggle whether invalid css property warnings are reported-->
          <!-- compiler.show-invalid-css-property-warnings usage:
          <show-invalid-css-property-warnings>boolean</show-invalid-css-property-warnings>
          -->
          <!-- compiler.show-shadowed-device-font-warnings: toggles whether warnings are displayed when an embedded font name shadows a device font name-->
          <show-shadowed-device-font-warnings>false</show-shadowed-device-font-warnings>
          <!-- compiler.show-unused-type-selector-warnings: toggle whether warnings generated from unused CSS type selectors are displayed-->
          <show-unused-type-selector-warnings>true</show-unused-type-selector-warnings>
          <!-- compiler.source-path: list of path elements that form the roots of ActionScript class hierarchies-->
          <source-path>
          </source-path>
          <!-- compiler.strict: runs the AS3 compiler in strict error checking mode.-->
          <strict>true</strict>
          <!-- compiler.theme: list of CSS or SWC files to apply as a theme-->
          <!-- compiler.use-resource-bundle-metadata: determines whether resources bundles are included in the application.-->
          <use-resource-bundle-metadata>true</use-resource-bundle-metadata>
          <!-- compiler.verbose-stacktraces: save callstack information to the SWF for debugging-->
          <verbose-stacktraces>false</verbose-stacktraces>
          <!-- compiler.warn-array-tostring-changes: Array.toString() format has changed.-->
          <warn-array-tostring-changes>false</warn-array-tostring-changes>
          <!-- compiler.warn-assignment-within-conditional: Assignment within conditional.-->
          <warn-assignment-within-conditional>true</warn-assignment-within-conditional>
          <!-- compiler.warn-bad-array-cast: Possibly invalid Array cast operation.-->
          <warn-bad-array-cast>true</warn-bad-array-cast>
          <!-- compiler.warn-bad-bool-assignment: Non-Boolean value used where a Boolean value was expected.-->
          <warn-bad-bool-assignment>true</warn-bad-bool-assignment>
          <!-- compiler.warn-bad-date-cast: Invalid Date cast operation.-->
          <warn-bad-date-cast>true</warn-bad-date-cast>
          <!-- compiler.warn-bad-es3-type-method: Unknown method.-->
          <warn-bad-es3-type-method>true</warn-bad-es3-type-method>
          <!-- compiler.warn-bad-es3-type-prop: Unknown property.-->
          <warn-bad-es3-type-prop>true</warn-bad-es3-type-prop>
          <!-- compiler.warn-bad-nan-comparison: Illogical comparison with NaN. Any comparison operation involving NaN will evaluate to false because NaN != NaN.-->
          <warn-bad-nan-comparison>true</warn-bad-nan-comparison>
          <!-- compiler.warn-bad-null-assignment: Impossible assignment to null.-->
          <warn-bad-null-assignment>true</warn-bad-null-assignment>
          <!-- compiler.warn-bad-null-comparison: Illogical comparison with null.-->
          <warn-bad-null-comparison>true</warn-bad-null-comparison>
          <!-- compiler.warn-bad-undefined-comparison: Illogical comparison with undefined.  Only untyped variables (or variables of type *) can be undefined.-->
          <warn-bad-undefined-comparison>true</warn-bad-undefined-comparison>
          <!-- compiler.warn-boolean-constructor-with-no-args: Boolean() with no arguments returns false in ActionScript 3.0.  Boolean() returned undefined in ActionScript 2.0.-->
          <warn-boolean-constructor-with-no-args>false</warn-boolean-constructor-with-no-args>
          <!-- compiler.warn-changes-in-resolve: __resolve is no longer supported.-->
          <warn-changes-in-resolve>false</warn-changes-in-resolve>
          <!-- compiler.warn-class-is-sealed: Class is sealed.  It cannot have members added to it dynamically.-->
          <warn-class-is-sealed>true</warn-class-is-sealed>
          <!-- compiler.warn-const-not-initialized: Constant not initialized.-->
          <warn-const-not-initialized>true</warn-const-not-initialized>
          <!-- compiler.warn-constructor-returns-value: Function used in new expression returns a value.  Result will be what the function returns, rather than a new instance of that function.-->
          <warn-constructor-returns-value>false</warn-constructor-returns-value>
          <!-- compiler.warn-deprecated-event-handler-error: EventHandler was not added as a listener.-->
          <warn-deprecated-event-handler-error>false</warn-deprecated-event-handler-error>
          <!-- compiler.warn-deprecated-function-error: Unsupported ActionScript 2.0 function.-->
          <warn-deprecated-function-error>true</warn-deprecated-function-error>
          <!-- compiler.warn-deprecated-property-error: Unsupported ActionScript 2.0 property.-->
          <warn-deprecated-property-error>true</warn-deprecated-property-error>
          <!-- compiler.warn-duplicate-argument-names: More than one argument by the same name.-->
          <warn-duplicate-argument-names>true</warn-duplicate-argument-names>
          <!-- compiler.warn-duplicate-variable-def: Duplicate variable definition -->
          <warn-duplicate-variable-def>true</warn-duplicate-variable-def>
          <!-- compiler.warn-for-var-in-changes: ActionScript 3.0 iterates over an object's properties within a "for x in target" statement in random order.-->
          <warn-for-var-in-changes>false</warn-for-var-in-changes>
          <!-- compiler.warn-import-hides-class: Importing a package by the same name as the current class will hide that class identifier in this scope.-->
          <warn-import-hides-class>true</warn-import-hides-class>
          <!-- compiler.warn-instance-of-changes: Use of the instanceof operator.-->
          <warn-instance-of-changes>true</warn-instance-of-changes>
          <!-- compiler.warn-internal-error: Internal error in compiler.-->
          <warn-internal-error>true</warn-internal-error>
          <!-- compiler.warn-level-not-supported: _level is no longer supported. For more information, see the flash.display package.-->
          <warn-level-not-supported>true</warn-level-not-supported>
          <!-- compiler.warn-missing-namespace-decl: Missing namespace declaration (e.g. variable is not defined to be public, private, etc.).-->
          <warn-missing-namespace-decl>true</warn-missing-namespace-decl>
          <!-- compiler.warn-negative-uint-literal: Negative value will become a large positive value when assigned to a uint data type.-->
          <warn-negative-uint-literal>true</warn-negative-uint-literal>
          <!-- compiler.warn-no-constructor: Missing constructor.-->
          <warn-no-constructor>false</warn-no-constructor>
          <!-- compiler.warn-no-explicit-super-call-in-constructor: The super() statement was not called within the constructor.-->
          <warn-no-explicit-super-call-in-constructor>false</warn-no-explicit-super-call-in-constructor>
          <!-- compiler.warn-no-type-decl: Missing type declaration.-->
          <warn-no-type-decl>true</warn-no-type-decl>
          <!-- compiler.warn-number-from-string-changes: In ActionScript 3.0, white space is ignored and '' returns 0. Number() returns NaN in ActionScript 2.0 when the parameter is '' or contains white space.-->
          <warn-number-from-string-changes>false</warn-number-from-string-changes>
          <!-- compiler.warn-scoping-change-in-this: Change in scoping for the this keyword.  Class methods extracted from an instance of a class will always resolve this back to that instance.  In ActionScript 2.0 this is looked up dynamically based on where the method is invoked from.-->
          <warn-scoping-change-in-this>false</warn-scoping-change-in-this>
          <!-- compiler.warn-slow-text-field-addition: Inefficient use of += on a TextField.-->
          <warn-slow-text-field-addition>true</warn-slow-text-field-addition>
          <!-- compiler.warn-unlikely-function-value: Possible missing parentheses.-->
          <warn-unlikely-function-value>true</warn-unlikely-function-value>
          <!-- compiler.warn-xml-class-has-changed: Possible usage of the ActionScript 2.0 XML class.-->
          <warn-xml-class-has-changed>false</warn-xml-class-has-changed>
       </compiler>
       <!-- debug-password: the password to include in debuggable SWFs-->
       <!-- debug-password usage:
       <debug-password>string</debug-password>
       -->
       <!-- default-background-color: default background color (may be overridden by the application code)-->
       <default-background-color>0xFFFFFF</default-background-color>
       <!-- default-frame-rate: default frame rate to be used in the SWF.-->
       <default-frame-rate>24</default-frame-rate>
       <!-- default-script-limits: default script execution limits (may be overridden by root attributes)-->
       <default-script-limits>
          <max-recursion-depth>1000</max-recursion-depth>
          <max-execution-time>60</max-execution-time>
       </default-script-limits>
       <!-- default-size: default application size (may be overridden by root attributes in the application)-->
       <default-size>
          <width>500</width>
          <height>375</height>
       </default-size>
       <!-- externs: a list of symbols to omit from linking when building a SWF-->
       <!-- externs usage:
       <externs>
          <symbol>string</symbol>
          <symbol>string</symbol>
       </externs>
       -->
       <frames>
          <!-- frames.frame: A SWF frame label with a sequence of classnames that will be linked onto the frame.-->
          <!-- frames.frame usage:
          <frame>
             <label>string</label>
             <classname>string</classname>
          </frame>
          -->
       </frames>
       <framework>halo</framework>
       <!-- include-inheritance-dependencies-only: only include inheritance dependencies of classes specified with include-classes -->
       <!-- include-inheritance-dependencies-only usage:
       <include-inheritance-dependencies-only>boolean</include-inheritance-dependencies-only>
       -->
       <!-- include-resource-bundles: a list of resource bundles to include in the output SWC-->
       <!-- include-resource-bundles usage:
       <include-resource-bundles>
          <bundle>string</bundle>
          <bundle>string</bundle>
       </include-resource-bundles>
       -->
       <!-- includes: a list of symbols to always link in when building a SWF-->
       <!-- includes usage:
       <includes>
          <symbol>string</symbol>
          <symbol>string</symbol>
       </includes>
       -->
       <!-- link-report: Output a XML-formatted report of all definitions linked into the application.-->
       <!-- link-report usage:
       <link-report>filename</link-report>
       -->
       <!-- load-config: load a file containing configuration options-->
       <!-- load-externs: an XML file containing <def>, <pre>, and <ext> symbols to omit from linking when building a SWF-->
       <!-- load-externs usage:
       <load-externs>filename</load-externs>
       -->
       <metadata>
          <!-- metadata.contributor: A contributor's name to store in the SWF metadata-->
          <!-- metadata.contributor usage:
          <contributor>name</contributor>
          -->
          <!-- metadata.creator: A creator's name to store in the SWF metadata-->
          <creator>darkhutgme</creator>
          <!-- metadata.date: The creation date to store in the SWF metadata-->
          <!-- metadata.date usage:
          <date>text</date>
          -->
          <!-- metadata.description: The default description to store in the SWF metadata-->
          <description></description>
          <!-- metadata.language: The language to store in the SWF metadata (i.e. EN, FR)-->
          <language>EN</language>
          <!-- metadata.localized-description: A localized RDF/XMP description to store in the SWF metadata-->
          <!-- metadata.localized-description usage:
          <localized-description>
             <text>string</text>
             <lang>string</lang>
             <lang>string</lang>
          </localized-description>
          -->
          <!-- metadata.localized-title: A localized RDF/XMP title to store in the SWF metadata-->
          <!-- metadata.localized-title usage:
          <localized-title>
             <title>string</title>
             <lang>string</lang>
             <lang>string</lang>
          </localized-title>
          -->
          <!-- metadata.publisher: A publisher's name to store in the SWF metadata-->
          <publisher>darkhutgame</publisher>
          <!-- metadata.title: The default title to store in the SWF metadata-->
          <title>GAME</title>
       </metadata>
       <!-- raw-metadata: XML text to store in the SWF metadata (overrides metadata.* configuration)-->
       <!-- raw-metadata usage:
       <raw-metadata>text</raw-metadata>
       -->
       <!-- remove-unused-rsls: remove RSLs that are not being used by the application-->
       <remove-unused-rsls>true</remove-unused-rsls>
       <!-- resource-bundle-list: prints a list of resource bundles to a file for input to the compc compiler to create a resource bundle SWC file. -->
       <!-- resource-bundle-list usage:
       <resource-bundle-list>filename</resource-bundle-list>
       -->
       <!-- runtime-shared-libraries: a list of runtime shared library URLs to be loaded before the application starts-->
       <!-- runtime-shared-libraries usage:
       <runtime-shared-libraries>
          <url>string</url>
          <url>string</url>
       </runtime-shared-libraries>
       -->
       <!-- runtime-shared-library-path: specifies a SWC to link against, an RSL URL to load, with an optional policy file URL and optional failover URLs -->
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/textLayout.swc</path-element>
          <rsl-url>textLayout_2.0.0.232.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/tlf/2.0.0.232/textLayout_2.0.0.232.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/osmf.swc</path-element>
          <rsl-url>osmf_1.0.0.16316.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/osmf_1.0.0.16316.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/framework.swc</path-element>
          <rsl-url>framework_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/framework_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/charts.swc</path-element>
          <rsl-url>charts_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/charts_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/rpc.swc</path-element>
          <rsl-url>rpc_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/rpc_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/mx/mx.swc</path-element>
          <rsl-url>mx_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/mx_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/advancedgrids.swc</path-element>
          <rsl-url>advancedgrids_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/advancedgrids_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark.swc</path-element>
          <rsl-url>spark_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark_dmv.swc</path-element>
          <rsl-url>spark_dmv_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_dmv_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/sparkskins.swc</path-element>
          <rsl-url>sparkskins_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/sparkskins_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-settings>
          <!-- runtime-shared-library-settings.application-domain: override the application domain an RSL is loaded into. The supported values are 'current', 'default', 'parent', or 'top-level'.-->
          <application-domain>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/textLayout.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/osmf.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/framework.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/charts.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/rpc.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/mx/mx.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/advancedgrids.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark_dmv.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/sparkskins.swc</path-element>
             <application-domain-target>default</application-domain-target>
          </application-domain>
          <!-- runtime-shared-library-settings.force-rsls: force an RSL to be loaded, overriding the removal caused by using the remove-unused-rsls option-->
          <!-- runtime-shared-library-settings.force-rsls usage:
          <force-rsls>
             <path-element>string</path-element>
             <path-element>string</path-element>
          </force-rsls>
          -->
       </runtime-shared-library-settings>
       <!-- size-report: Output an XML-formatted report detailing the size of all code and data linked into the application.-->
       <!-- size-report usage:
       <size-report>filename</size-report>
       -->
       <!-- static-link-runtime-shared-libraries: statically link the libraries specified by the -runtime-shared-libraries-path option.-->
       <static-link-runtime-shared-libraries>false</static-link-runtime-shared-libraries>
       <!-- swf-version: specifies the version of the compiled SWF file.-->
       <swf-version>14</swf-version>
       <!-- target-player: specifies the version of the player the application is targeting. Features requiring a later version will not be compiled into the application. The minimum value supported is "9.0.0".-->
       <target-player>11.1.0</target-player>
       <!-- tools-locale: specifies the locale used by the compiler when reporting errors and warnings.-->
       <!-- tools-locale usage:
       <tools-locale>string</tools-locale>
       -->
       <!-- use-direct-blit: Use hardware acceleration to blit graphics to the screen, where such acceleration is available.-->
       <!-- use-direct-blit usage:
       <use-direct-blit>boolean</use-direct-blit>
       -->
       <!-- use-gpu: Use GPU compositing features when drawing graphics, where such acceleration is available.-->
       <!-- use-gpu usage:
       <use-gpu>boolean</use-gpu>
       -->
       <!-- use-network: toggle whether the SWF is flagged for access to network resources-->
       <use-network>true</use-network>
       <!-- verify-digests: verifies the libraries loaded at runtime are the correct ones.-->
       <verify-digests>true</verify-digests>
       <!-- warnings: toggle the display of warnings-->
       <!-- warnings usage:
       <warnings>boolean</warnings>
       -->
    </flex-config>

    Somewhere in your pom.xml where you are configuring your build dependancies there will be a line <scope>caching</scope> this line is configuring the build to use a flex runtime shared library. This line is generating the error because caching is not a valid dependancy scope in maven 3 however mojos uses it anyway. There was a defect opened against flexmojos; I've linked it below. Froeder's response to the issue was that it was not fixable, that the warning is expected and that we'll have to live with it for now.
    https://issues.sonatype.org/browse/FLEXMOJOS-363?page=com.atlassian.jira.plugin.system.iss uetabpanels%3Achangehistory-tabpanel

  • I get a Pre-execute error message when importing from Excel using the wizard.

    Hello, I get the following pre execute error message(see below) when I try to import a table from Excel when using the wizard. I wrote my own code in the edit window. i noticed after writing it that the data types did not appear changed in the mappings window.
    Can anyone explain what these errors mean and how they can be solved. Thank you.
    Operation stopped...
    - Initializing Data Flow Task (Success)
    - Initializing Connections (Success)
    - Setting SQL Command (Success)
    - Setting Source Connection (Success)
    - Setting Destination Connection (Success)
    - Validating (Success)
    Messages
    * Warning 0x80049304: Data Flow Task 1: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available.  To resolve, run this package as an administrator,
    or on the system's console.
    (SQL Server Import and Export Wizard)
    - Prepare for Execute (Success)
    - Pre-execute (Error)
    Messages
    * Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Unspecified error".
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "The metadata could not be determined because every code path results in
    an error; see previous errors for some of these.".
    An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Invalid object name 'dbo.PriceTable$'.".
    (SQL Server Import and Export Wizard)
    * Error 0xc0202040: Data Flow Task 1: Failed to open a fastload rowset for "[dbo].[PriceTable$]". Check that the object exists in the database.
    (SQL Server Import and Export Wizard)
    * Error 0xc004701a: Data Flow Task 1: Destination - PriceTable$ failed the pre-execute phase and returned error code 0xC0202040.
    (SQL Server Import and Export Wizard)
    * Information 0x4004300b: Data Flow Task 1: "Destination - PriceTable$" wrote 0 rows.
    (SQL Server Import and Export Wizard)
    - Executing (Success)
    - Copying to [dbo].[PriceTable$] (Stopped)
    - Post-execute (Stopped)
    frustrationmultiplied

    Hello,
    Are you willing to try other ways to do the same?
    http://www.excel-sql-server.com/excel-import-to-sql-server-using-linked-servers.htm
    http://support.microsoft.com/kb/321686 (Distributed queries)
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Is there a way to embed copyright information with forms?

    I would like to put a copyright on custom forms I am creating, or not really a copyright but just an acknowldgement of my company as the creator of the form and of the practice which is using the form. Is there a way to embed this in a PDF. Not necessarily in a visible way either. I am using Adobe Acrobat Pro 9. My boss is demanding this so please help!

    First you can add the information as a footer in the authoring program.
    Next you can add custom meta data fields to include the copyright notice, contact information, and usage restrictions through the "File => Properties => Custom" UI or with JavaScript. Doc Properties info
    You can also set the meta daa copyright through the "File => Properties => Description => Additional Metadata..."  or with JavaScript. Doc Properties metadata
    You can modify these scripts to make them functions that can be accessed by adding an option to an Acrobat menu item or as a tool bar button.
    app addMenuItem method
    app add subMenu
    app addToolButton
    app removeToolButton

  • How can I embed XML data in a PDF?

    I want to embed XML data in a PDF so the file can be scanned for the data behind the document. Is there a standard way to do this?
    For example, if the PDF is a bank statement, the embedded XML would be the individual's account number and bank balances. It would not include any of the standard text in the statement such as the bank name, etc.
    I've read up on the XMP spec but that seems to be more metadata about the document (title, subject, etc.). And there is tagged content but that is an alternate view of the entire document.
    ??? - thanks - dave

    Although the XMP block is stored in XML, you can't just embed any XML file. The block has to follow the standard, which means that each data packet needs to be defined in a schema - as the name suggests, XMP is eXtendable so you can define new schema for local use, but you can't mess about with the standard ones and randomly add new tags. The schema itself isn't embedded in the file, it's referenced by a unique ID and URI. of course having a data packet in a custom schema doesn't mean any software will see it - Acrobat's Advanced Search can be told to scan the XMP block but  search engines only tend to bother with the basic tags such as 'title' and 'description'.
    To see what's currently in a PDF, open Document Properties > Description > Additional Metadata > Advanced.
    You can save the current XMP block as a text file (.xmp extension), and replace/append other XMP files. If you click the "i" icon on the top right of the Advanced dialog you can access system profiles - these can be created in other applications such as Bridge, but there's no profile manager in Acrobat itself.
    For technical information on working with XMP and creating new schema, see http://www.adobe.com/devnet/xmp.html
    Note that the XMP SDK for CS6 does not work in the Acrobat Family.

  • People Refinement Panel not displaying "Department" filter category.

    I am trying to create people directory in SharePoint 2010. I am using "People Search Core Result" web-part and "People Refinement Panel" web-part.
    Following is the screen of my "People Search Core Result" webpart properties:
    Following is the "Filter category Definition" in "People Refinement Panel"
    <?xml version="1.0" encoding="utf-8"?>
    <FilterCategories>
    <Category Title="Department" Description="Use this filter to restrict results to a specific department" Type="Microsoft.Office.Server.Search.WebControls.ManagedPropertyFilterGenerator" MetadataThreshold="5" NumberOfFiltersToDisplay="4" MaxNumberOfFilters="20" SortBy="Frequency" SortByForMoreFilters="Name" SortDirection="Descending" SortDirectionForMoreFilters="Ascending" ShowMoreLink="True" MappedProperty="DepartmentR" MoreLinkText="show more" LessLinkText="show fewer" />
    <Category Title="View" Description="View matches by" Type="Microsoft.Office.Server.Search.WebControls.RankingModelFilterGenerator" MetadataThreshold="3" NumberOfFiltersToDisplay="3" ShowMoreLink="False" MappedProperty=""/>
    <Category Title="spshjobtitle" Description="Use this filter to restrict results to a specific job title" Type="Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator" MetadataThreshold="3" NumberOfFiltersToDisplay="3" MaxNumberOfFilters="50" ShowMoreLink="True" MappedProperty="ows_MetadataFacetInfo" MoreLinkText="show more" LessLinkText="show fewer"/>
    <Category Title="Organization" Description="Use this filter to restrict results to a specific organization" Type="Microsoft.Office.Server.Search.WebControls.ManagedPropertyFilterGenerator" MetadataThreshold="5" NumberOfFiltersToDisplay="4" MaxNumberOfFilters="50" SortBy="Frequency" SortDirection="Descending" SortByForMoreFilters="Name" SortDirectionForMoreFilters="Ascending" ShowMoreLink="True" MappedProperty="OrgNames" MoreLinkText="show more" LessLinkText="show fewer"/>
    <Category Title="Managed Metadata Columns" Description="Managed metadata of the documents" Type="Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator" MetadataThreshold="3" NumberOfFiltersToDisplay="3" MaxNumberOfFilters="50" ShowMoreLink="True" MappedProperty="ows_MetadataFacetInfo" MoreLinkText="show more" LessLinkText="show fewer"/>
    </FilterCategories>
    I have unchecked "Use Default Configuration" in "People Refinement Panel" web-part.
    I can only see "Job Title" in refinement panel.
    In above xml code, the metadata property "DepartmentR" is mapped to "People:Department(Text)".  I even full crawled after creating this property but this property never appears in Refinement Panel. I even performed full profile synchronization
    in User Profile Application but still no luck.
    Please help.

    Make sure the managed property has the following set
    1. Allow Property to be used in scopes: Ticked
    2. Reduce storage requirements for text properties by using a hash for comparison: Ticked
    3. Add managed property to custom results set retrieved on each query. Note: Only the first 2 kilobytes of data is available for display by default: Ticked
    Check this post, it displays exactly what you want might help you
    Raghavendra Shanbhag | Blog: www.SharePointColumn.com
    Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Disclaimer: This posting is provided "AS IS" with no warranties.

Maybe you are looking for

  • Submit by Email AS a PDF (urgent - time crunch)

    I'm creating a form to be distributed externally to clients via email.  I'd like them to be able to fill in the form, then click Submit by Email and have a completed PDF sent back to me (which we save in clients files for our records in an attempt at

  • Does the newest mac mini ($799 one) support intel vt-d when use the virtual machine like fusion?

    I've got some info about this mac mini. the cpu is i5-2520M? which support vt-d. at least intel's page say it can. I want make sure about this before i buy it, plesas help. thank you~~!

  • PO history status texts

    Hi All, For subsequent debit and credit, the PO history is shown with indicator NB-L.  Also, in some cases I can PO history with indicator SD-L (Subs. deb. log. IV).  How is this status getting updated in PO history. Which transaction will update thi

  • Exact things happen in the implementation time.

    Dear Cons We know the configuration. consultants prepares their CV as if they know end to end implimentation. In real time 60% don't know the exact scenario occured in implimetnation. so my question is from particularly while doing initial entry of s

  • Step Forward/Backward One Field

    Sadly, Avid Media Composer has been my daily editing tool (my place of employment is an Avid house). I started on FCP and freelance using my FCP machine... believe me, I would very much rather be cutting on FCP. Going from FCP to Avid is... well... a