facebook

Error: Processing Dirty Regions

  1. MyEclipse IDE
  2.  > 
  3. Java EE Development (EJB, JSP, Struts, XDoclet, etc.)
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #282051 Reply

    ceeturose
    Member

    Hi

    I am facing a strange problem in Eclipse. I created a JSP file using Struts taglibs. But, whenever I modify or save jsp file a pop-up window will appear saying:
    An internal error occured during: “Processing Dirty Regions”.
    javax/servlet/jsp/tagext/TagLibraryInfo.

    Why is this happening? It appears each and every time. Can someone please help on this.

    Thanks

    #282060 Reply

    Loyal Water
    Member

    Are you getting this error with Eclipse or MyEclipse ?

    Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

    #282707 Reply

    kangelov
    Member

    I experience exactly the same problem. It’s a clean install and it’s breaking down, I don’t usually use MyEclipse on a Mac.

    This is the information you request:

    *** Date:
    Monday, March 10, 2008 12:06:09 o’clock PM EDT

    ** System properties:
    OS=MacOSX
    OS version=10.5.2
    Java version=1.5.0_13

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    Eclipse Graphical Editing Framework

    Version: 3.3.1.v20070814
    Build id: 20080221-1602

    Eclipse Platform

    Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
    Build id: M20080221-1800

    Eclipse Java Development Tools

    Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
    Build id: M20080221-1800

    Eclipse Plug-in Development Environment

    Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
    Build id: M20080221-1800

    Eclipse Graphical Editing Framework

    Version: 3.3.2.v20080129
    Build id: 20080221-1602

    Eclipse RCP

    Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
    Build id: M20080221-1800

    Eclipse startup command=-os
    macosx
    -ws
    carbon
    -arch
    ppc
    -showsplash
    -launcher
    /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse
    -name
    Eclipse
    –launcher.library
    /Applications/eclipse/Eclipse.app/Contents/MacOS/../../../plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.3.R33x_v20080118/eclipse_1023.so
    -startup
    /Applications/eclipse/Eclipse.app/Contents/MacOS/../../../plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
    -keyring
    /Users/kangelov/.eclipse_keyring
    -consoleLog
    -showlocation
    -product
    com.genuitec.myeclipse.product.ide
    -vm
    /System/Library/Frameworks/JavaVM.framework

    #282708 Reply

    kangelov
    Member

    I experience exactly the same problem. It’s a clean install and it’s breaking down, I don’t usually use MyEclipse on a Mac.

    This is the information you request:

    *** Date:
    Monday, March 10, 2008 12:06:09 o’clock PM EDT

    ** System properties:
    OS=MacOSX
    OS version=10.5.2
    Java version=1.5.0_13

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    Eclipse Graphical Editing Framework

    Version: 3.3.1.v20070814
    Build id: 20080221-1602

    Eclipse Platform

    Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
    Build id: M20080221-1800

    Eclipse Java Development Tools

    Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
    Build id: M20080221-1800

    Eclipse Plug-in Development Environment

    Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
    Build id: M20080221-1800

    Eclipse Graphical Editing Framework

    Version: 3.3.2.v20080129
    Build id: 20080221-1602

    Eclipse RCP

    Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
    Build id: M20080221-1800

    Eclipse startup command=-os
    macosx
    -ws
    carbon
    -arch
    ppc
    -showsplash
    -launcher
    /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse
    -name
    Eclipse
    –launcher.library
    /Applications/eclipse/Eclipse.app/Contents/MacOS/../../../plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.3.R33x_v20080118/eclipse_1023.so
    -startup
    /Applications/eclipse/Eclipse.app/Contents/MacOS/../../../plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
    -keyring
    /Users/kangelov/.eclipse_keyring
    -consoleLog
    -showlocation
    -product
    com.genuitec.myeclipse.product.ide
    -vm
    /System/Library/Frameworks/JavaVM.framework

    #282716 Reply

    Loyal Water
    Member

    Guys,
    This seems like an issue related to Eclipse 3.3.2. The dev team is already working on this. You can keep a track of this at the following link:-
    https://www.genuitec.com/forums/topic/multiple-errors-have-occurred/#post-282687

    #282717 Reply

    kangelov
    Member

    I apologize for the double post above. I solved the problem:

    I installed MyEclipse on top of a non-Classic version of Eclipse. In particular I used Eclipse pre-loaded with plugins for J2EE development and then installed MyEclipse on top of that. That’s a no-no: You have to use a Classic Eclipse to install MyEclipse.

    Here is the solution: Close everything, install a fresh Eclipse and make sure it is the “Classic” one. You don’t have to delete your old eclipse, just put it in a different directory.

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Error: Processing Dirty Regions

You must be logged in to post in the forum log in