XML parser and XML processor

Hi,
I am trying to load the XML Parser and XSLT processor into the XDK that i have. Please can someone tell me how this is done. So far i keep hearing about classpath and .jar files. i have no idea what to do with these. Is there a manual which will tell me how to do this? Or can anyone explain to me?. Or can anyone tell me how to check if they are already there, the technican installed the software but does not know how to use it!, so i am very lost with this and am using it for my masters project.
Hope you can help.
Thanks

Hi,
I have checked the lib folder. xmlparsev2.jar is there. Is this the classpath? if not how do i get it to the classpath? and how do i do that?
Thanks for your help so far

Similar Messages

  • Parse and output XML document while preserving attribute order

    QUESTION: How can I take in an element with attributes from an XML and output the same element and attributes while preserving the order of those attributes?
    The following code will parse and XML document and generate (practically) unchanged output. However, all attributes are ordered a-z
    Example: The following element
    <work_item_type work_item_db_site="0000000000000000" work_item_db_id="0" work_item_type_code="3" user_tag_ident="Step" name="Work Step" gmt_last_updated="2008-12-31T18:00:00.000000000" last_upd_db_site="0000000000000000" last_upd_db_id="0" rstat_type_code="1">
    </work_item_type>is output as:
    <work_item_type gmt_last_updated="2008-12-31T18:00:00.000000000" last_upd_db_id="0" last_upd_db_site="0000000000000000" name="Work Step" rstat_type_code="1" user_tag_ident="Step" work_item_db_id="0" work_item_db_site="0000000000000000" work_item_type_code="3">
    </work_item_type>As you may notice, there is no difference in these besides order of the attributes!
    I am convened that the problem is not in the stylesheet.xslt but if you are not then it is posted bellow.
    Please, someone help me out with this! I have a feeling the solution is simple
    The following take the XML from source.xml and outputs it to DEST_filename with attributes in a-z order
    Code:
    private void OutputFile(String DEST_filename, String style_filename){
         //StreamSource stylesheet = new StreamSource(style_filename);
         try{
              File dest_file = new File(DEST_filename);
              if(!dest_file.exists())
                  dest_file.createNewFile();
              TransformerFactory tranFactory = TransformerFactory.newInstance();
              Transformer aTransformer = tranFactory.newTransformer();
              aTransformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
              Source src = new DOMSource("source.xml");
              Result dest = new StreamResult(dest_file);
              aTransformer.transform(src, dest);
              System.out.println("Finished");
         catch(Exception e){
              System.err.print(e);
              System.exit(-1);
        }

    You can't. The reason is, the XML Recommendation explicitly says the order of attributes is not significant. Therefore conforming XML serializers won't treat it as if it were significant.
    If you have an environment where you think that the order of attributes is significant, your first step should be to reconsider. Possibly it isn't really significant and you are over-reaching in some way. Or possibly someone writing requirements is ignorant of this fact and the requirement can be discarded.
    Or possibly your output is being given to somebody else who has a defective parser which expects the attributes to be in a particular order. You could quote the XML Recommendation to those people but often XML bozos are resistant to change. If you're stuck writing for that parser then you'll have to apply some non-XML processing to your output to fix it up on their behalf.

  • XML Parser and Content-type/encoding problem

    I've write a little and simple XML parser and a simple "trasformer" that recive an XML file and an XSL one and return HTML, here is the code:
    public static String toHTML(Document doc, String xslSource){
            ByteArrayOutputStream testo = new ByteArrayOutputStream();
            try{
                DOMSource source = new DOMSource(doc);
                TransformerFactory tFactory = TransformerFactory.newInstance();
                System.out.println("----> " + xslSource);
                Transformer transformer = tFactory.newTransformer(new StreamSource(xslSource));
                transformer.setOutputProperty(OutputKeys.INDENT, "yes");
                transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "2");
                transformer.setOutputProperty(OutputKeys.METHOD, "html");
             transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
             transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
                transformer.transform(source, new StreamResult(testo));
            }catch(Exception ioe){
                System.out.println("2 XMLTool.toHTML " + new java.util.Date());
                System.out.println(ioe);        
            return testo.toString();
        }the problem is that I would like to put the HTML code its return into a JEditorPane; now I'm trying with this code:
    JEditorPane jep1 = new JEditorPane();
    jep1.setContentType("text/html");
    jep1.setText(v);
    // 'v' is the string returned by the code posted up (the XML/XSL transformer)but I can't see anything in my JEditorPane.
    I think that the problem is this line of code that the transformer add automaticaly ad HTML code:
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">Infact if I try to delete this line from the code I can see what I want but is'n good delete a line of code without understend where is the problem.
    So, can anyone help me?

    good.
    when u set ur output properties to html , transformer
    searches for all entity references and converts accordingly.
    if u r using xalan these files will be used for conversion of
    Character entity references for markup-significant
    output_html.properties
    (this should be in templates package)
    and HTMLEntities.res(should be in serialize package)
    vasanth-ct

  • Parse and render XML... and get original replicated?

    Now that I've (temporarily) got iFS working (on another machine for now). I've got an XML question: I moved the airportdefinition.xml into the folder, and then subsequently moved the airport.xml into the folder, whereupon iFS parsed it and stored it. Yeah! However when examining (or copy out) the stored data, it is somewhat different than the original:
    original:
    <?xml version="1.0"?>
    <Airport>
    <Name>airport1.fly</Name>
    <AirportCode>SFO</AirportCode>
    <AirportName>San Francisco</AirportName>
    <FolderPath>.</FolderPath>
    </Airport>
    As recreated by the renderer:
    <?xml version = '1.0' standalone = 'yes'?>
    <AIRPORT>
    <Name>airport1.fly</Name>
    <Owner RefType="Name" ClassName="DIRECTORYUSER">system<!--ID # 96--></Owner>
    <ACL RefType="Name" ClassName="SYSTEMACCESSCONTROLLIST">Published<!--ID # 422--></ACL>
    <CreateDate format="MMM dd HH:mm">Nov 09 15:44</CreateDate>
    <Creator RefType="Name" ClassName="DIRECTORYUSER">system<!--ID # 96--></Creator>
    <LastModifyDate format="MMM dd HH:mm">Nov 09 15:44</LastModifyDate>
    <LastModifier RefType="Name" ClassName="DIRECTORYUSER">system<!--ID # 96--></LastModifier>
    <LockState>0</LockState>
    <AIRPORTCODE>SFO</AIRPORTCODE>
    <AIRPORTNAME>San Francisco</AIRPORTNAME>
    </AIRPORT>
    We'd like (to have cake and eat it) to be able to store parsed xml (to support queryability, indexing, reporting, etc.) but also want to be able to recreate the original xml UNCHANGED.
    If we don't parse it, we can have unchanged data, but then limit the queryability. Other than storing the xml document twice (both parsed and not) is there any way to do this?
    null

    I am glad that you solve this question and share the solution with us, I will mark your reply as the answer.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Oracle XML processor is not handling variable properly

    I use the XML Parser 2.0.2.7 to process an XML transformation but I don't get the expected result. Running this example with other XML Processor get the job done (IBM, Excelon, Microsoft). I read again the normative document on www.w3c.org on XSL and I believe that your processor fail to render my XSL transformation because it doesn't handle variable properly.
    So, here is my XML document and my XSL stylesheet:
    XML Document:
    <Results>
    <Usager>
    <IdUsager>34</IdUsager>
    <NomUsager>NomUsager</NomUsager>
    <PrenomUsager>Le prenom de l'usager</PrenomUsager>
    <NoAssuranceMaladie>ZZZZ12121212</NoAssuranceMaladie>
    <dossiersommaire_view>
    <UsagerSommaire>
    <IdEven>2</IdEven>
    <TypeElement>16</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>1998-04-05</DateDebut>
    <IdDoc>5</IdDoc>
    <IdCatgElement>6</IdCatgElement>
    <Description>Initial</Description>
    <IdTypeElement>16</IdTypeElement>
    <IdCatgElement1>6</IdCatgElement1>
    <Description1>Bilan mitastatique initial</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>16</TypeElement1>
    <DroitAcces>M</DroitAcces>
    </UsagerSommaire>
    <UsagerSommaire>
    <IdEven>30</IdEven>
    <TypeElement>15</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>2000-06-08</DateDebut>
    <IdDoc>31</IdDoc>
    <IdCatgElement>6</IdCatgElement>
    <Description>Initial</Description>
    <IdTypeElement>15</IdTypeElement>
    <IdCatgElement1>6</IdCatgElement1>
    <Description1>Sommaire initial</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>15</TypeElement1>
    <DroitAcces>M</DroitAcces>
    </UsagerSommaire>
    <UsagerSommaire>
    <IdEven>7</IdEven>
    <TypeElement>6</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>2000-04-15</DateDebut>
    <IdDoc>1</IdDoc>
    <IdCatgElement>2</IdCatgElement>
    <Description>Examens</Description>
    <IdTypeElement>6</IdTypeElement>
    <IdCatgElement1>2</IdCatgElement1>
    <Description1>Examens numirisis</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>6</TypeElement1>
    <DroitAcces>C</DroitAcces>
    </UsagerSommaire>
    <UsagerSommaire>
    <IdEven>9</IdEven>
    <TypeElement>2</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>2000-03-14</DateDebut>
    <IdDoc>1</IdDoc>
    <IdCatgElement>1</IdCatgElement>
    <Description>Suivi</Description>
    <IdTypeElement>2</IdTypeElement>
    <IdCatgElement1>1</IdCatgElement1>
    <Description1>Suivi oncologique</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>2</TypeElement1>
    <DroitAcces>C</DroitAcces>
    </UsagerSommaire>
    <UsagerSommaire>
    <IdEven>10</IdEven>
    <TypeElement>2</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>2000-03-27</DateDebut>
    <IdDoc>1</Id Doc>
    <IdCatgElement>1</IdCatgElement>
    <Description>Suivi</Description>
    <IdTypeElement>2</IdTypeElement>
    <IdCatgElement1>1</IdCatgElement1>
    <Description1>Suivi oncologique</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>2</TypeElement1>
    <DroitAcces>C</DroitAcces>
    </UsagerSommaire>
    <UsagerSommaire>
    <IdEven>16</IdEven>
    <TypeElement>16</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>2000-06-05</DateDebut>
    <IdDoc>46</IdDoc>
    <IdCatgElement>6</IdCatgElement>
    <Description>Initial</Description>
    <IdTypeElement>16</IdTypeElement>
    <IdCatgElement1>6</IdCatgElement1>
    <Description1>Bilan mitastatique initial</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>16</TypeElement1>
    <DroitAcces>M</DroitAcces>
    </UsagerSommaire>
    <UsagerSommaire>
    <IdEven>26</IdEven>
    <TypeElement>15</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>2000-06-07</DateDebut>
    <IdDoc>32</IdDoc>
    <IdCatgElement>6</IdCatgElement>
    <Description>Initial</Description>
    <IdTypeElement>15</IdTypeElement>
    <IdCatgElement1>6</IdCatgElement1>
    <Description1>Sommaire initial</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>15</TypeElement1>
    <DroitAcces>M</DroitAcces>
    </UsagerSommaire>
    <UsagerSommaire>
    <IdEven>37</IdEven>
    <TypeElement>15</TypeElement>
    <IdUsager>34</IdUsager>
    <IdUtilisateur>1</IdUtilisateur>
    <DateDebut>2000-06-08</DateDebut>
    <IdDoc>32</IdDoc>
    <IdCatgElement>6</IdCatgElement>
    <Description>Initial</Description>
    <IdTypeElement>15</IdTypeElement>
    <IdCatgElement1>6</IdCatgElement1>
    <Description1>Sommaire initial</Description1>
    <IdUtilisateur1>1</IdUtilisateur1>
    <CodeProfil>3</CodeProfil>
    <CodeProfil1>3</CodeProfil1>
    <TypeElement1>15</TypeElement1>
    <DroitAcces>M</DroitAcces>
    </UsagerSommaire>
    </dossiersommaire_view>
    <categorie_view>
    <CatgElement>
    <IdCatgElement>1</IdCatgElement>
    <Description>Suivi</Description>
    <type_view>
    <TypeElement>
    <IdTypeElement>2</IdTypeElement>
    <IdCatgElement>1</IdCatgElement>
    <Description>Suivi oncologique</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>2</TypeElement>
    <DroitAcces>C</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>5</IdTypeElement>
    <IdCatgElement>1</IdCatgElement>
    <Description>Suivi pharmaceutique</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>5</TypeElement>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>3</IdTypeElement>
    <IdCatgElement>1</IdCatgElement>
    <Description>Suivi avec chimiothirapie</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>3</TypeEleme nt>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>4</IdTypeElement>
    <IdCatgElement>1</IdCatgElement>
    <Description>Evaluation psychosociale</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>4</TypeElement>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    </type_view>
    </CatgElement>
    <CatgElement>
    <IdCatgElement>2</IdCatgElement>
    <Description>Examens</Description>
    <type_view>
    <TypeElement>
    <IdTypeElement>6</IdTypeElement>
    <IdCatgElement>2</IdCatgElement>
    <Description>Examens numirisis</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>6</TypeElement>
    <DroitAcces>C</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    </type_view>
    </CatgElement>
    <CatgElement>
    <IdCatgElement>3</IdCatgElement>
    <Description>Ricidive</Description>
    <type_view>
    <TypeElement>
    <IdTypeElement>7</IdTypeElement>
    <IdCatgElement>3</IdCatgElement>
    <Description>Ricidives</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>7</TypeElement>
    <DroitAcces>C</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    </type_view>
    </CatgElement>
    <CatgElement>
    <IdCatgElement>4</IdCatgElement>
    <Description>Mitastase</Description>
    <type_view>
    <TypeElement>
    <IdTypeElement>8</IdTypeElement>
    <IdCatgElement>4</IdCatgElement>
    <Description>Mitastases</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>8</TypeElement>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    </type_view>
    </CatgElement>
    <CatgElement>
    <IdCatgElement>5</IdCatgElement>
    <Description>Traitement</Description>
    <type_view>
    <TypeElement>
    <IdTypeElement>9</IdTypeElement>
    <IdCatgElement>5</IdCatgElement>
    <Description>Chimiothirapie (nursing onco)</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>9</TypeElement>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>10</IdTypeElement>
    <IdCatgElement>5</IdCatgElement>
    <Description>Hormonothirapie (nursing onco)</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>10</TypeElement>
    <DroitAcces>C</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>12</IdTypeElement>
    <IdCatgElement>5</IdCatgElement>
    <Description>Radiothirapie - plan de traitement</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>12</TypeElement>
    <DroitAcces>C</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>13</IdTypeElement>
    <IdCatgElement>5</IdCatgElement>
    <Description>Radiothirapie - note de fin de traitement (rapport numirisi)</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement&gt ;13</TypeElement>
    <DroitAcces>C</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>14</IdTypeElement>
    <IdCatgElement>5</IdCatgElement>
    <Description>Chirurgie (rapport numirisi)</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>14</TypeElement>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    </type_view>
    </CatgElement>
    <CatgElement>
    <IdCatgElement>6</IdCatgElement>
    <Description>Initial</Description>
    <type_view>
    <TypeElement>
    <IdTypeElement>15</IdTypeElement>
    <IdCatgElement>6</IdCatgElement>
    <Description>Sommaire initial</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>15</TypeElement>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    <TypeElement>
    <IdTypeElement>16</IdTypeElement>
    <IdCatgElement>6</IdCatgElement>
    <Description>Bilan mitastatique initial</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>16</TypeElement>
    <DroitAcces>M</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    </type_view>
    </CatgElement>
    <CatgElement>
    <IdCatgElement>7</IdCatgElement>
    <Description>Autre</Description>
    <type_view>
    <TypeElement>
    <IdTypeElement>17</IdTypeElement>
    <IdCatgElement>7</IdCatgElement>
    <Description>Note du midecin</Description>
    <CodeProfil>3</CodeProfil>
    <TypeElement>17</TypeElement>
    <DroitAcces>C</DroitAcces>
    <IdUtilisateur>1</IdUtilisateur>
    <CodeProfil1>3</CodeProfil1>
    </TypeElement>
    </type_view>
    </CatgElement>
    </categorie_view>
    </Usager>
    </Results>
    XSL Stylesheet:
    <?xml version="1.0" encoding='ISO-8859-1'?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:output indent="yes" method="text" encoding='ISO-8859-1'/>
    <xsl:template match="*|/"><xsl:apply-templates/></xsl:template>
    <xsl:template match="text()|@*"><xsl:value-of select="."/></xsl:template>
    <xsl:template match="/"><xsl:text><html>
    </xsl:text>
    <xsl:text><BODY BGCOLOR= "#CEDFC6">
    </xsl:text>
    <xsl:text><APPLET CODEBASE="/applets/" CODE="SIRtree.class" WIDTH=200 HEIGHT=380>
    </xsl:text>
    <xsl:text><PARAM NAME="TITLEFONT" VALUE="0">
    </xsl:text>
    <xsl:text><PARAM NAME="ICONS" VALUE="/applets/DRQICON.gif">
    </xsl:text>
    <xsl:text><PARAM NAME="BGCOLOR" VALUE="8">
    </xsl:text>
    <xsl:text><PARAM NAME="NODEFONT" VALUE="3">
    </xsl:text>
    <xsl:text><PARAM NAME="HBGCOLOR" VALUE="2">
    </xsl:text>
    <xsl:text><PARAM NAME="TXTCOLOR" VALUE="2">
    </xsl:text>
    <xsl:text><PARAM NAME="HTXTCOLOR" VALUE="10">
    </xsl:text>
    <xsl:text><PARAM NAME="FONT1" VALUE="Helvetica|B">
    </xsl:text>
    <xsl:text><PARAM NAME="FONT2" VALUE="Helvetica|N">
    </xsl:text>
    <xsl:text><PARAM NAME="FONT3" VALUE="Arial|N">
    </xsl:text>
    <xsl:text><!-- Medium Grey -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color1" VALUE="150|150|150">
    </xsl:text>
    <xsl:text><!-- Black -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color2" VALUE="0|0|0">
    </xsl:text>
    <xsl:te xt><!-- Blue -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color3" VALUE="0|0|255">
    </xsl:text>
    <xsl:text><!-- Red -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color4" VALUE="255|0|0">
    </xsl:text>
    <xsl:text><!-- Orange -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color5" VALUE="255|128|0">
    </xsl:text>
    <xsl:text><!-- Dark Grey -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color6" VALUE="100|100|100">
    </xsl:text>
    <xsl:text><!-- Light Grey -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color7" VALUE="200|200|200">
    </xsl:text>
    <xsl:text><!-- Light Green -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color8" VALUE="206|223|198">
    </xsl:text>
    <xsl:text><!-- Yellow -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color9" VALUE="255|255|0">
    </xsl:text>
    <xsl:text><!-- White -->
    </xsl:text>
    <xsl:text><PARAM NAME="Color10" VALUE="255|255|255">
    </xsl:text>
    <xsl:text><PARAM NAME="BORDER" VALUE="0">
    </xsl:text>
    <xsl:text><!-- Menu principal -->
    </xsl:text>
    <xsl:variable name="NodeCPT" select='3'/>
    <xsl:text><PARAM NAME="NODE0" VALUE="ROOT|</xsl:text><xsl:value-of select="Results/Usager/NomUsager"/><xsl:text>"|1| | | | |0|-1">
    </xsl:text>
    <xsl:text><PARAM NAME="NODE1" VALUE="ROOT|</xsl:text><xsl:value-of select="Results/Usager/PrenomUsager"/><xsl:text>"|1| | | | |0|-1">
    </xsl:text>
    <xsl:text><PARAM NAME="NODE2" VALUE="ROOT|</xsl:text><xsl:value-of select="Results/Usager/NoAssuranceMaladie"/><xsl:text>"|1| | | | |0|-1">
    </xsl:text>
    <xsl:for-each select="/Results/Usager/categorie_view/CatgElement">
    <xsl:variable name="Racine" select="Description"/>
    <xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="ROOT|</xsl:text><xsl:value-of select="$Racine"/><xsl:text>|1| |mainFrame| | |1|-1|4">
    </xsl:text>
    <xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
    <xsl:text>
    // Ajouter les Types d'iliment
    </xsl:text>
    <xsl:for-each select="type_view/TypeElement">
    <xsl:variable name="Feuille" select="Description"/>
    <xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Racine"/><xsl:text>|</xsl:text><xsl:value-of select="Description"/><xsl:text>|1| |mainFrame| | |1|-1|4">
    </xsl:text>
    <xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
    <xsl:variable name="DroitAcces" select="DroitAcces"/>
    <xsl:if test="$DroitAcces = 'M'">
    <xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Feuille"/><xsl:text>|Ajouter...|3|http://drioq.qc.cgi.ca/jspdrioq/Elem_Query.jsp?IdTypeElem=</xsl:text><xsl:value-of select="TypeElementId"/><xsl:text>|mainFrame| | |0">
    </xsl:text>
    <xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
    </xsl:if>
    <xsl:variable name="TypeElement" select="IdTypeElement"/>
    <xsl:for-each select="//Results/Usager/dossiersommaire_view/UsagerSommaire[TypeElement=$TypeElement]">
    <xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Feuille"/><xsl:text>|</xsl:text><xsl:value-of select="Description"/><xsl:text> du </xsl:text><xsl:value-of select="DateDebut"/><xsl:text>|2|http://drioq.qc.cgi.ca/jspdrioq/Elem_Query.jsp?IdEven=</xsl:text><xsl:value-of select="I dEven"/><xsl:text>|mainFrame| | |0">
    </xsl:text>
    <xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
    </xsl:for-each>
    <xsl:if test="($DroitAcces = 'C')">
    <xsl:if test="(count(//Results/Usager/dossiersommaire_view/UsagerSommaire[TypeElement=$TypeElement]) = 0)">
    <xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Feuille"/><xsl:text>|Aucun Dossier |5| | | | |0">
    </xsl:text>
    <xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
    </xsl:if>
    </xsl:if>
    </xsl:for-each>
    </xsl:for-each>
    <xsl:text>
    //-----------------------------------PAS TOUCHE----------------------------------------------------------
    </xsl:text>
    <xsl:text></BODY>
    </xsl:text>
    <xsl:text></html>
    </xsl:text>
    </xsl:template>
    </xsl:stylesheet>
    null

    First of all, thank for Steve and Micheal for your help.
    Well, it's that I don't read section 11.5 before I posted my last messages(I don't know how I did that??? may be to much nightly development) Also I think that xsl:variable just lead to misunderstanding. I would prefere the "xsl:constant" label.
    In neither way, I'm still looking for a solution to number my parameter because I don't each time how many parameter I'll have to pass to my applets. I'm now looking for pure JSP.
    Steve you also pointed out that the use of <xsl:text> is very strange! You're right! The main reason why I'm working that way is because we need to generate JavaScript based on the XML Data. So I start my stylesheet in text mode because I need to generate text (JavaScript) and not only tag like "PARAM". But to simply this example and focus on the problem I retired the JavaScript Part and any other not relevent tag! If there is a way to change the output mode after generating the JavaScript I would like to know about it.
    Ok, everyone thanks again!

  • Question About Xerces Parser and Java  JAXP

    Hi,
    I have confusion about both of these API Xerces Parser and Java JAXP ,
    Please tell me both are used for same purpose like parsing xml document and one is by Apache and one is by sun ?
    And both can parse in SAX, or DOM model ?
    Is there any difference in performane if i use xerces in my program rather then JAXP, or is ther any other glance at all.
    Please suggest some thing i have and xml document and i want to parse it.
    Thanks

    Hi
    Xerces is Apaches implementation of W3C Dom specifiacation.
    JAXP is a API for XML parsing its not implementation.
    Sun ships a default implementation for JAXP.
    you have factory methods for selecting a parser at run time or you can set in some config file about what is the implementaion class for the SAXParser is to be chosen (typically you give give the class file of xerces sax parser or dom parser etc..)
    go to IBM Developerworks site and serch for Xerces parser config. which have a good explination of how to do it.
    and browse through j2ee api .may find how to do it.

  • Example IFS parser and renderer

    Hi
    I was wondering if someone could provide me with some sample code of a very simple parser and renderer to get me going on my java for this.
    In 9ifs there already is an example of a parser called SimplestParser which extracts information from between the <title>...</title> tags from a html document. The example then lets you apply this to html documents for which the extension .html is changed to .cus (for custom). The XML is given to create a custom class and associate the extension with that parser.
    What is not there is a renderer that displays this information back to the user (of what is between the <title>...</title> tags). I assume a renderer would display this in the IFS web interface when you go to Edit -> Properties.
    Would enyone be able to provide me with sample code for such a renderer, or alternatively a complete parser/renderer complementary set, extracting and displaying simple custom attibute(s) for a particular file type?
    That would greatly help me out.
    Thanks very much.
    Hugo

    I have another problem with custom parser. It doesn't work with versioned documents:
    I have versioned file in iFS, if I parse and upload new version of that file I get Error: File already exists. I think that I should somehow set the family of doument which I want to parse & upload. But I don't know how.
    null

  • Memory Leakage while parsing and schema validation

    It seems there is some kind of memory leakage. I was using xdk 9.2.0.2.0. Later i found that from this forum which contain a Topic on this and they (oracle ) claim they have memory leakage. And they have fixes this bugs in 9.2.0.6.0 xdk. When i used truss command, for each call to parser and schame validation, it was opening file descriptor for lpxus and lsxus file. And this connections were not close. And keep on openning it with each call to parser. I was able to diagonise this using truss command on on solaris. After making many calls, i was error message could not open file Result.xsd (0202). I am using one instance of Parser and Schema. And i am doing clean up for parser after each parse.
    Later i downloaded, 9.2.0.6.0,
    Above problem for the parser was solvedm but still the problem continued for schema validation. And even i tried with latest beta release 10.
    And this has caused great troubles to us. Please can u look whether there is come sort of leakage. Please advice if u have any solution.
    Code---
    This below code is called multiple times
    char* APIParser::execute(const char* xmlInput) {
              char* parseResult = parseDocument(xmlInput);
              //if(strcmp(parseResult,(const char*)"")==0) {
    if(parseResult == NULL) {
                   parseResult = getResult();
    parser.xmlclean();
         return parseResult;
              } else {
                   return parseResult;
    Parser and schema are intialised in Construtor and terminated in Destructor.

    Hi, here is the complete test case
    #include<iostream>
    #ifndef ORAXML_CPP_ORACLE
    # include <oraxml.hpp>
    #endif
    using namespace std;
    #define FAIL { cout << "Failed!\n"; return ; }
    void mytest(int count)
         uword ecode;
         XMLParser parser;
         Document *doc;
         Element root, elem;
         if (ecode = parser.xmlinit())
              cout << "Failed to initialze XML parser, error " << ecode << "\n";
              return ;
         cout << "\nCreating new document...\n";
         if (!(doc = parser.createDocument((oratext *) 0, (oratext *) 0,(DocumentType *) 0)))
         FAIL
         if (!(elem = doc->createElement((oratext *) "ROOT")))
                   FAIL
         string test="Elem";
         for(int i=0;i<count;i++)
              //test="Elem"+string(ltoa(i));
              if (!(elem = doc->createElement((oratext *) "element")))
                   FAIL
              if (!doc->appendChild(elem))
                   FAIL
         //doc ->print();
         //parser.xmlclean();
         parser.xmlterm();
    int main(int argc,char* argv[])
         int count=atol(argv[1]);
         mytest(count);
         char c;
         cout<<"check memory usage n press any key"<<endl;
         cin>>c;
         return 0;
    -------------------------------------------cut here-----
    Now, i cant use the xdk 10g because i work on a hpux machine. I have tried the above program with a count of 1000000. the memory usage at the end was around 2 gigabytes.
    Could someone please please help me? :(
    Thank you.

  • SSIS 2008 package conversion to SSIS 2012 using SQL Data Tools generating warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWra

    I am seeing the following warning is a SSIS C# script and receive a SSIS abort when I attempt to run the package.
    The SSIS log indicates the package is failing at about this same step in the process.  
    I have also included the file SSQLDUMPER_ERRORLOG.log that SSIS generates when it aborts below.
    My SSIS package has been set to 64-bit and I only have 64-bit SQL Server 2012 installed on the box.
    I migrated the package using the latest version of Data Tools that came out around mid July 2014.
    I edited all connection manager strings to point to 64-bit SQL Server and I run using the following command
    I edited the run string to point to the new 64 bit DTExec and attempted to run.
    C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /Rep V /F PkgMigration.dtsx .........................
    A significant amount of work does occur as reflected by the log steps prior to DTEXEC aborting but the log does just quit in mid sentence so not sure if it might have actually got a bit further.
    Any help on understanding what is happening here would be most appreciated.
    Warning               1              There was a mismatch between the processor
    architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWrap, Version=11.0.0.0, Culture=Neutral, PublicKeyToken=89845dcd8080cc91", "x86". This mismatch may
    cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a
    processor architecture that matches the targeted processor architecture of your project.                C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets             
    1605       5                sc_5756696d96034309a51afe69fed2eb44
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 6100
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00A8B770
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6100
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00A8B770
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0007.mdmp
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (1CBC:1808) 08/14/14 10:36:47, ACTION,                DTExec.exe, Watson Invoke: No
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 10124
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0012B770
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 10124
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0012B770
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0008.mdmp
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2724:2488) 08/14/14 10:43:09, ACTION,                DTExec.exe, Watson Invoke: No
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8716
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 0072B770
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8716
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0072B770
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0009.mdmp
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2240:89C) 08/14/14 10:51:56, ACTION,                DTExec.exe, Watson Invoke: No
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8856
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 009AB770
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8856
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x009AB770
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0010.mdmp
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (7B8:1E68) 08/14/14 11:01:36, ACTION,                DTExec.exe, Watson Invoke: No
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 1292
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00BFB770
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 1292
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00BFB770
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0011.mdmp
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (229C:1CD8) 08/14/14 11:45:45, ACTION,                DTExec.exe, Watson Invoke: No
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 4220
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0019B770
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 4220
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0019B770
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0012.mdmp
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2520:2624) 08/14/14 12:05:47, ACTION,                DTExec.exe, Watson Invoke: No
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 8408
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00000000003ECC18
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8408
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000003ECC18
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0001.mdmp
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION,                DTExec.exe, Watson Invoke: No

    Hi GaryAMiller,
    It seesm this is a know ssue. Please take a look at the following simialr issue at Microsoft Connect site:
    MSB3270: Mismatch between the processor architecture:
    https://connect.microsoft.com/VisualStudio/feedback/details/804933/msb3270-mismatch-between-the-processor-architecture-fakes-framework
    If this issue still persists, I would suggest
    opening a case with Microsoft Customer Support Services (CSS)(http://support.microsoft.com), so that a dedicated Support Professional can assist you in a more efficient manner.
    If you have any feedback on our support, please click
    here.
    Elvis Long
    TechNet Community Support

  • One Image for dual and single processor G5 machines

    I'm working in a lab that has both single and dual processors G5 machines. There is only one image for both machines and I suspect that we have a few bugs with the single processor machines because of this. Has anyone else used one image for both single and dual processors? Have there been problems. I'm wondering if it is necessary to create two separate images.
    mdinger

    There is not difference in the images, but you might have problems with the single G5 machines and 10.4. Did you do the firmware upgrade?
    I have ~10 single G5 and 25 dual D5 machines netinstalled from one image without trouble.
    jotjot

  • Bridge CS6: How do you write a script to assign a shortcut to "Batch" and "Image Processor"?

    Many times a day I need to access "Batch" and "Image Processor" in Bridge.
    There is no shortcut, so I have to go the Tools-Photoshop-Batch and Tools-Photoshop-Image Processor menu - the items I need are locked into a second level menu.
    Which is impractical.
    I remember, when I started out with Photoshop many years ago, I downloaded "Deke Keyes" from Deke McClelland, which included keystrokes for "Batch" and "Image Processor".
    From the Bridge forum I learned that you cannot assign shortcuts in Bridge CS6.
    So the general opinon was that a script was used to assign the shortcuts.
    Could you please tell me how to do that?
    Thanks!
    PS: I tried to assign shortcuts via the Mac OS X Mountain Lion keyboard preferences (applications), but it did not work.

    Hi,
    in the exit:Event of the 1st date field add this FormCalc script:
    DateField2 = Num2Date(Date2Num($.formattedValue, "DD.MM.YYYY") + 21, "DD.MM.YYYY")
    You may have to change th date pattern  "DD.MM.YYYY" in the way you need it.

  • Shortcuts for Batch and Image Processor in Bridge CS6

    I use Batch and Image Processor all the time, and I'd like to use a shortcut.
    Can you tell me if there is a shortcut or how I can program one?
    I set up shortcuts for those two commands in Photoshop, but they don't work in Bridge.
    I remember from the time I started with Photoshop and had Deke McClelland's book with his set of shortcuts. There was a shortcut that worked with image processor, but it was just a set you did install and no explanation. When I moved to a different computer and a newer version of Photoshop, these keys got lost.
    Is there any way to automate Batch and Image Processor?

    There is no way to economically batch process in Bridge without having to go thorough sub-menus.
    I'm sorry you can't get it to work, but on my system it works flawless.
    Testing a bit more it seems you don't need to use a unique shortcut at all. I also tried to use the shortcut for Batch I created in PS itself to get the Batch window to front for running actions on open files. For me that is [control + Cmd + B] but feel free to find an other one.
    When I discovered you don't need the unique shortcut at all I used the same shortcut for Bridge CC. . Also created [Control + Cmd + i] for the Image processor.
    Both started without problems.
    To extend I also created both same shortcuts for Bridge CS6. This also was working correctly, off course, having only PS CC open using the shortcut in Bridge CS6 it auto started PS CS6.
    So can you specify a bit more about what OS you are using on what computer (I have OSX 10.8.4 on a MacPro 2012)
    Some screenshots to show the shortcuts in System prefs and how the show in the Bridge Submenus:

  • PowerMac G5 Image across single, dual, and quad Processor Macs

    Good Day,
    Our organization is preparing to roll out Tiger. To streamline
    this process we have decided to create images for each Mac family in
    use. I know I need to find the newest possible model to create the
    image but what is the rule for single, dual, and quad processor macs?
    Can we use an image created on a quad processor PowerMac on the
    dual/single processor PowerMacs?
    Thanks

    Macs of different models and vintages may take different restore disks. The disk image method of doing this kind of work may or may not work. Use the original disks when faced with different releases or different models. See this article:
    http://docs.info.apple.com/article.html?artnum=25784
    So a dual-single processor transfer will not necessarily work.
    In addition, there are license agreement considerations.
    I would not do it unless you know you are in the clear on both accounts.

  • 01.01.0000 date parse and format

    Could somebody explain is wrong here?
    SimpleDateFormat frm = new SimpleDateFormat("yyyyMMddHHmmss");  // formatter
    frm.setTimeZone(TimeZone.getTimeZone("UTC"));   // UTC time zone
    // --- No problem for the next code ---
    String inDate = "19700101000000";  // 01.01.1970 input date
    long stamp;
    try {
        stamp = frm.parse(inDate).getTime();   // input date in long
    } catch (ParseException ex) {
        System.out.println("Interruption");
        stamp = 0;
    String outDate = frm.format(stamp);  // output date
    System.out.println("inDate=>" + inDate + "_longDate=>" + stamp + "_outDate=>" + outDate);
    // --- No idea why next code is working wrongly ---
    inDate = "00000101000000";  // 01.01.0000 input date
    try {
        stamp = frm.parse(inDate).getTime();   // input date in long
    } catch (ParseException ex) {
        System.out.println("Interruption");
        stamp = 0;
    outDate = frm.format(stamp);  // output date
    System.out.println("inDate=>" + inDate + "_longDate=>" + stamp + "_outDate=>" + outDate);I try to parse and format the time stamp 01.01.0000 00:00:00. On the finish I have 01.01.0001 instead of the correct 01.01.0000
    inDate=>19700101000000_longDate=>0_outDate=>19700101000000
    inDate=>00000101000000_longDate=>-62167392000000_outDate=>00010101000000

    You are calling format with a long parameter. The only format that matches that signature that I can see would be Format.format(Object) assuming autoboxing is changing the long to a Long.
    Format.format(Object) eventually calls DateFormat.format(Object, StringBuffer, FieldPosition). I have never used this method so I am not sure what it does.
    Was your intention to actually call this method?
    See the following example:
    System.out.println("Test 1: " + frm.format(new Long(0l), new StringBuffer(), new FieldPosition(0)));  
    System.out.println("Test 2: " + frm.format(new Long(-62167392000000l), new StringBuffer(), new FieldPosition(0)));  
    Test 1: 19700101000000
    Test 2: 00010101000000Edited by: jbish on Apr 26, 2013 12:43 PM
    Edited by: jbish on Apr 26, 2013 1:09 PM

  • Low Execute to Parse % and high soft parse %

    Hello Folks
    I am working on oracle 10g release2 on HP-UX
    After going through awr reports observed it have low Execute to Parse % but high soft parse % (Instance Efficiency Percentages)
    so cannot say issue with less use of bind variables,then what is cause of Execute to Parse %
    searched sites like ask.tom,burselon counsulting etc as usual they had given generic/diplomatic(escaping) replies on this
    like due to problem in application code,ineffecient sharing ,due to problem in database parameters etc
    without any clear indication for cause and solution like if some database parameters not set properly then should say which database parameters can be checked,cause due to more parsing and less execution
    please share if you had faced such issue and any suggestions to solve this
    examples why this could happen ,like possibilities in application code
    Thanks

      Load Profile
                                              Per Second       Per Transaction
                   Redo size:             11,685.79              3,660.98
                   Logical reads:             71,445.74             22,382.86
                   Block changes:                 70.89                 22.21
                   Physical reads:                 58.63                 18.37
                   Physical writes:                  2.80                  0.88
                   User calls:                652.93                204.55
                   Parses:                 48.39                 15.16
                   Hard parses:                  0.33                  0.10
                   Sorts:                  6.90                  2.16
                   Logons:                  0.23                  0.07
                   Executes:                 52.71                 16.51
                   Transactions:                  3.19
                % Blocks changed per Read:    0.10    Recursive Call %:    30.48
                Rollback per transaction %:    2.57       Rows per Sort:    29.66
        Instance Efficiency Percentages (Target 100%)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                 Buffer Nowait %:  100.00       Redo NoWait %:  100.00
                 Buffer  Hit   %:   99.92    In-memory Sort %:  100.00
                 Library Hit   %:   98.47        Soft Parse %:   99.32
                 Execute to Parse %:    8.19         Latch Hit %:   99.63
                 Parse CPU to Parse Elapsd %:   89.90     % Non-Parse CPU:   99.62There rdbms performs approximately 48 soft parse per second ,Soft Parse % and Library Hit very close to 99 it means there main part of sql are shared.Also here user calls similar high per second but executions less,however you should be try minimizing soft parsing.I do not know exactly for which interval you get this report but Execute to Parse % indicate that when executing query oracle can not find early cursor handles(open or closed) but it can find sql text and plan information from shared pool according hash values,in this case oracle perform soft parse again.In your case you also investigate shared pool size/fragmentation.To avoid little Execute to Parse % you can increase SESSION_CACHED_CURSORS or implement CURSOR_SPACE_FOR_TIME.So refer documentation and find how to use these parameters.

Maybe you are looking for

  • How Do I Get My Game Data Back?

    So, I have two sons and a daughter. One son is the oldest, (doesn't use the ipad often) Then the daughter is the middle (uses the ipad ALOT and knows everything about it ) and I have a child son, young. He plays games on the ipad. One day my daughter

  • I cannot see all mobile phone numbers in Messages after upgrade to iOS 6

    I have two mobile number entries for most of my contacts, for example: +853 1234 5678 0060 853 1234 5678 The first entry is for dialing the mobile number when I am overseas, and need to use the international prefix "+". I also use this for sending SM

  • Reset my Lumia 620 through settings and now it's '...

    I planned to give my Lumia 620 to my dad as I had recently upgraded to a 920. Thus I did a reset to make it feel as brand new as possible. Now, it's stuck at the 'cog cycle' for at least a day. What will the care centre do with it?

  • Can't registered a new product

    I'm trying to registered the new iPhone that I ordered on Apple.com. It shows, "According to our records, this serial number is registered to another Apple ID. If you have more than one Apple ID, log in to My Support Profile with that Apple ID to see

  • Kann ich eine sicherungs dvd von lion erstellen

    Hallo! Ich habe Lion installiert, hat alles super geklappt. Meine Frage: Kann ich von Lion eine Sicherungs DVD erstellen, sodass ich im Notfall davon neu installieren kann???? Wie geht das sonst - erst wieder Snow Leo drauf und dann updaten? Danke fü