You need to sign in to do that
Don't have an account?
DrewK.ax1106
Eclipse Force.com IDE Save Errors
Any ideas on how to fix this? Thanks.
Save error: Unable to perform save on all files: com.salesforce.ide.api.metadata.types.Metadata$JaxbAccessorF_fullName cannot be cast to com.sun.xml.internal.bind.v2.runtime.reflect.Accessor **** line 1 Force.com save problem
Just to update everyone, its July 2012 and we are having issues with Java JRE 7u5 and JDK 7u5.
So I DOWNGraded with the follwing steps:
This worked fine.
Obviously we are slightly concerned that we now have an "old" version of JRE on our PCs (because security-concious apps like GoToMeeting require the latest versions to work) >> Salesforce, Please Solve this so we can use the latest (most secure/fast) version of JRE/JDK Thanks. :-)
All Answers
I get the same error on trying to create a new project in Eclipse. Can anyone shed a light on this?
Okay I got to the bottom of it. Solution:
- Use JRE v6 update 27 - 64bit (downgraded from JRE 7)
- Use JDK v6 update 27 - 64 bit (downgraded from JDK 7)
- Re-installed Eclipse SDK 3.6.2
In short, downgrading solved the problem.
Excellent! That did it thanks!
Is the proposed installation fix pertaining to Save Errors still up-to-date?
Thanks
Jeff in Seattle
Just to update everyone, its July 2012 and we are having issues with Java JRE 7u5 and JDK 7u5.
So I DOWNGraded with the follwing steps:
This worked fine.
Obviously we are slightly concerned that we now have an "old" version of JRE on our PCs (because security-concious apps like GoToMeeting require the latest versions to work) >> Salesforce, Please Solve this so we can use the latest (most secure/fast) version of JRE/JDK Thanks. :-)
Hi,
Yes this will Solves the problem.
You can understand that Java Version 1.7 breakes some where and problem solved by installing Java 1.6 versions.
http://boards.developerforce.com/t5/Apex-Code-Development/Very-strange-IDE-error-occuring-today/td-p/339769
I appreciate you for sharing and it will defiantly useful to lot of people
That may well solve the "issue", but downgrading Eclipse to a version that was from 2010 and a version of Java from August 2011 (especially considering the numerous severe Java bug/exploits the last few months), that just doesn't feel like a "Solution"
CurtisK +1
How long must we wait to be able to use current versions?? Downgrading is a terrible and ridiculous fix.
Just to follow up, if you look in this thread, you may be able to find a workaround without downgrading, my post there shows how I happened to get it working with my setup, but there are some variations as you'll see
http://wiki.developerforce.com/page/Force.com_IDE_Installation_for_Eclipse_3.6
I've uninstalled and am downloading the newer version indicated on this page:
http://wiki.developerforce.com/page/Force.com_IDE_Installation