function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Ron-LONRon-LON 

Problem with ECLIPSE: org.xml.sax.SAXParseException -- HELP??

Hi,

 

I'm quite frustrated by my current problem with Eclipse.  Hopefully someone's seen this?

 

I've been getting this error with Eclipse when trying to save back to Salesforce on the production instance.  I had two Force.com projects, one that pointed to my production instance and one that pointed to my developers account.

 

I was only getting the error for prod and not the dev.  So I deleted the Force.com project and created new.  That didn't work.  So I got rid of everything eclipse on my pc.  Then I went  to http://community.salesforce.com/t5/forums/postpage/board-id/apex and followed the directions for downloading, installing and configuring Eclipse from scratch.

 

No luck with that either.

 

The steps I'm taking to repeat the error:

 

I open up one of my unit test classes and somewhere in the middle on an empty line I add "//comment" into the code.  Then I save.

 

In the Problems area, I get "Save error: Unable to perform save on all files.  An unexpected error has occurred. Check the logfile for details."

 

Does anyone know how I remedy these errors from the log below, or even some guidance as to what they are??

 

Thanks!!!

 

 

!SESSION 2010-01-29 17:40:16.132 ----------------------------------------------- eclipse.buildId=M20090211-1700 java.version=1.6.0_18 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0 2010-01-29 17:44:57.978 !MESSAGE Error parsing metadata repository !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 9, column 99: Missing required attribute in "repository": url !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 9, column 99: Illegal value for attribute "url" of element "repository": null !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 10, column 99: Missing required attribute in "repository": url !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 10, column 99: Illegal value for attribute "url" of element "repository": null !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 11, column 97: Missing required attribute in "repository": url !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 11, column 97: Illegal value for attribute "url" of element "repository": null !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 12, column 97: Missing required attribute in "repository": url !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2010-01-29 17:44:57.978 !MESSAGE Error at line 12, column 97: Illegal value for attribute "url" of element "repository": null !SESSION 2010-01-29 17:49:18.286 ----------------------------------------------- eclipse.buildId=M20090211-1700 java.version=1.6.0_18 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY com.salesforce.ide.core 2 0 2010-01-29 17:50:44.730 !MESSAGE WARN [2010-01-29 17:50:44,730] (IntroEditorInput.java:loadDocument:130) - org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. !ENTRY com.salesforce.ide.core 2 0 2010-01-29 17:56:15.365 !MESSAGE WARN [2010-01-29 17:56:15,365] (ProjectService.java:handleDeployResult:1928) - Save failed! !ENTRY com.salesforce.ide.core 2 0 2010-01-29 17:56:15.381 !MESSAGE WARN [2010-01-29 17:56:15,381] (ProjectService.java:handleRetrieveResult:2073) - Nothing to save to project - retrieve result is empty !ENTRY com.salesforce.ide.core 4 0 2010-01-29 17:56:15.396 !MESSAGE ERROR [2010-01-29 17:56:15,381] (BuilderController.java:handleException:134) - Unable to perform save on all files. !STACK 0 java.lang.NullPointerException at com.salesforce.ide.core.services.ProjectService.setRunTestFailureMarker(ProjectService.java:2335) at com.salesforce.ide.core.services.ProjectService.handleRunTestMessages(ProjectService.java:2310) at com.salesforce.ide.core.services.ProjectService.handleRunTestResult(ProjectService.java:2230) at com.salesforce.ide.core.services.ProjectService.handleDeployResult(ProjectService.java:1940) at com.salesforce.ide.core.project.BuilderController.handleSaves(BuilderController.java:118) at com.salesforce.ide.core.project.BuilderController.build(BuilderController.java:95) at com.salesforce.ide.core.project.BuilderController.build(BuilderController.java:75) at com.salesforce.ide.core.project.OnlineBuilder.incrementalBuild(OnlineBuilder.java:79) at com.salesforce.ide.core.project.OnlineBuilder.build(OnlineBuilder.java:49) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

 

 

 

bob_buzzardbob_buzzard
So are you still trying to save to a production org?  According to the Apex docs, you can't develop against a production org, you can only deploy changes, so this may be intended behaviour (albeit without a decent message!).
Ron-LONRon-LON

I did think about that because I'm still able to "deploy". 

 

I was able to save, and I was also able to delete.  Now I've got some old triggers I don't need but I've had to deploy a version of the trigger with the body commented out because I can't delete because of the same error.