I have been working with jDeveloper and JDE (J.D.Edwards) for a little while. Mostly to build integration pieces for portals and custom applications. One of the strangest things happened to me after I did a package update (upgrade to local JDE application) the other day.
After the package update, I grabbed my project code from the OMW (object management workbench) and tried to go back to development. All of a sudden it had replaced my ValueObject classes with generated classes ( really...I have no idea why) and copied some other strange code articles to my computer.
This was really strange but good thing I managed to backup my code using an alternative source code control system just in case something bizarre like this happened....which of course it did. I copied my code back over the top of the JDE code and all was well, with the exception of some oracle.e1.bssvfoundation classes not working correctly (complaining that the method could not be found, etc). In order to build my code I needed to remove some new code (that showed up during the package build) in the c:\e812\dv812\java\source\oracle\e1\bssvfoundation folder. I think its safe to say you can delete that entire folder because it should not exist in your source code folder.
To try and make a confusing story short and understandable I guess what I am trying to say if you find that you have the folder c:\e812\dv812\java\source\oracle\e1\bssvfoundation you can delete it because you probably shouldn't have it....these are system functions that you don't need the source for, and chances are if you do have the source its not the right version :s. I am not sure why they are included in our package but they are.
If your still with me then I hope this helped...if you are confused then drop me a line and I will attempt to explain by adding more acronyms and file paths.
Calvin