<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Eclipse for ABAP: ByteCode.java:778: unexpected case in reading pad file in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/eclipse-for-abap-bytecode-java-778-unexpected-case-in-reading-pad-file/m-p/788559#M39810</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
  &lt;P&gt;in the error log view, I got several of these info events when I open an ABAP program's source code in Eclipse 2018-12:&lt;/P&gt;
  &lt;P&gt;"Plug-in: com.sap.rnd.rndrt&lt;/P&gt;
  &lt;P&gt;Message: ByteCode.java:778: unexpected case in reading pad file&lt;/P&gt;
  &lt;P&gt;An exception stack trace is not available."&lt;/P&gt;
  &lt;P&gt;This is quite annoying because I don't know why this message occurs and it doesn't mean anything to me. It happens several times when opening an ABAP program's source code and it looks like some bug. It is hard to see other (relevant) error messages if this message spams the error log.&lt;/P&gt;
  &lt;P&gt;Is this expected behavior or actually a bug? If it is a bug, how can I report it (via Launchpad -&amp;gt; which component?)?&lt;/P&gt;
  &lt;P&gt;Thanks for your replies!&lt;/P&gt;</description>
    <pubDate>Fri, 15 Feb 2019 20:05:46 GMT</pubDate>
    <dc:creator>clemens_prill</dc:creator>
    <dc:date>2019-02-15T20:05:46Z</dc:date>
    <item>
      <title>Eclipse for ABAP: ByteCode.java:778: unexpected case in reading pad file</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/eclipse-for-abap-bytecode-java-778-unexpected-case-in-reading-pad-file/m-p/788559#M39810</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
  &lt;P&gt;in the error log view, I got several of these info events when I open an ABAP program's source code in Eclipse 2018-12:&lt;/P&gt;
  &lt;P&gt;"Plug-in: com.sap.rnd.rndrt&lt;/P&gt;
  &lt;P&gt;Message: ByteCode.java:778: unexpected case in reading pad file&lt;/P&gt;
  &lt;P&gt;An exception stack trace is not available."&lt;/P&gt;
  &lt;P&gt;This is quite annoying because I don't know why this message occurs and it doesn't mean anything to me. It happens several times when opening an ABAP program's source code and it looks like some bug. It is hard to see other (relevant) error messages if this message spams the error log.&lt;/P&gt;
  &lt;P&gt;Is this expected behavior or actually a bug? If it is a bug, how can I report it (via Launchpad -&amp;gt; which component?)?&lt;/P&gt;
  &lt;P&gt;Thanks for your replies!&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 20:05:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/eclipse-for-abap-bytecode-java-778-unexpected-case-in-reading-pad-file/m-p/788559#M39810</guid>
      <dc:creator>clemens_prill</dc:creator>
      <dc:date>2019-02-15T20:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: Eclipse for ABAP: ByteCode.java:778: unexpected case in reading pad file</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/eclipse-for-abap-bytecode-java-778-unexpected-case-in-reading-pad-file/m-p/788560#M39811</link>
      <description>&lt;P&gt;This issue seems to occur because NW version 731 is used. Thus an older ADT backend is being used with latest Eclipse. I didn't find a solution but I found out that this error doesn't happen with systems which use a newer NW version.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 10:31:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/eclipse-for-abap-bytecode-java-778-unexpected-case-in-reading-pad-file/m-p/788560#M39811</guid>
      <dc:creator>clemens_prill</dc:creator>
      <dc:date>2019-03-18T10:31:01Z</dc:date>
    </item>
  </channel>
</rss>

