8.1.2.1201 OD is this a known bug and is there any fix.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • neman
    Hot Shot
    • Oct 2019
    • 10

    8.1.2.1201 OD is this a known bug and is there any fix.

    When I export a speech application in this new version of OD, it apparently is modifying a file called ddlog4j2.xml by commenting out the <appender-ref ref="console-log"/>, which I understand is by design. However, if you mod the application and export it again, it adds a comment to the comment, causing errors on the server. If you export again it adds a comment to the comment to the comment and your file starts looking like this.

    here is the file after the 2nd export, i've underlined the lines for your reference.
    <Loggers>
    <Logger name="Dialog.Designer.TraceWriter" level="debug" additivity="false">
    <appender-ref ref="trace"/>
    <!--<!-- <appender-ref ref="console-log"/>-->-->
    </Logger>
    <Logger name="Dialog.Designer.ReportWriter" level="debug" additivity="false">
    <appender-ref ref="report"/>
    <!--<!-- <appender-ref ref="console-log"/>-->-->
    </Logger>
    <Root level="debug" additivity="false">
    <!--<!-- <AppenderRef ref="console-log"/>-->-->
    </Root>
    </Loggers>
  • wilsonyu
    Hot Shot
    .
    • Sep 2011
    • 24

    #2
    So when you say " if you mod the application...", do you mean you commented out the line manually? If you do that, that might cause the conflict. We did not expect you to do the modification manually while the project is in development. Is there problem you reverse the modification before the export?

    Comment

    • neman
      Hot Shot
      • Oct 2019
      • 10

      #3
      No I did not mod the file. If I change anything in the speech application, add a data node, move a line, anything. Save it. Then export using the wizard, it keeps adding more and more comments to those lines shown.

      Comment

      • wilsonyu
        Hot Shot
        .
        • Sep 2011
        • 24

        #4
        I did some testing. What I found is if the ddlog4j2.xml is in its original form (without the "<! >") and the export is successful, the "<! >" would NOT get built up. You can do as many "Export" without any problem. Only when there is an error in the "Export", the ddlog42j.xml in the data directory gets changed and the "<! >" gets built up in the file and results in the error in the war file. This was not intended. I will look into resolving it. In the meantime, you can manually modify the ddlog4j2.xml in the data to return it to its original form for now. You won't have problem if the Export is successful.

        Comment

        • neman
          Hot Shot
          • Oct 2019
          • 10

          #5
          Thank you much appreciated

          Comment

          Loading