facebook

lots of spring ide errors

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #354073 Reply

    atomz4peace
    Participant

    Hi,

    Every time I build my project, I’m not getting tons of errors relating to spring ide. I pasted one below, but I have about 20-30 of them, all identical except the class name. The java files exist, the app runs, etc.. we just see this error in the eclipse error log. It doesn’t seem to stop from building the app, but it does not look right.

    Any ideas? It’s still there after starting with -clean and rebuilding the app.

    Thanks!

    java.io.FileNotFoundException: class path resource [com/example/app1/webapp/EditApplicationController.class] cannot be opened because it does not exist
        at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:158)
        at org.springframework.ide.eclipse.core.type.asm.SimpleClassReaderFactory.getClassReader(SimpleClassReaderFactory.java:67)
        at org.springframework.ide.eclipse.core.type.asm.CachingClassReaderFactory.getClassReader(CachingClassReaderFactory.java:61)
        at org.springframework.ide.eclipse.core.type.asm.SimpleClassReaderFactory.getClassReader(SimpleClassReaderFactory.java:63)
        at org.springframework.ide.eclipse.core.java.classreading.JdtConnectedMetadataReader.<init>(JdtConnectedMetadataReader.java:42)
        at org.springframework.ide.eclipse.core.java.classreading.JdtMetadataReaderFactory.getMetadataReader(JdtMetadataReaderFactory.java:53)
        at org.springframework.ide.eclipse.core.java.classreading.CachingJdtMetadataReaderFactory.getMetadataReader(CachingJdtMetadataReaderFactory.java:38)
        at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:73)
        at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:274)
        at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:87)
        at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:752)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:745)
        at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcessExternal(BeansConfig.java:679)
        at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.addExternalPostProcessor(BeansConfig.java:710)
        at org.springframework.ide.eclipse.beans.core.internal.model.BeansProject$DefaultBeansConfigEventListener.onPostProcessorDetected(BeansProject.java:1281)
        at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.readConfig(BeansConfig.java:543)
        at org.springframework.ide.eclipse.beans.core.internal.model.AbstractBeansConfig.getBeans(AbstractBeansConfig.java:280)
        at org.springframework.ide.eclipse.beans.core.internal.model.validation.BeansConfigReloadingProjectContributionEventListener.start(BeansConfigReloadingProjectContributionEventListener.java:110)
        at org.springframework.ide.eclipse.core.internal.project.SpringProjectContributionManager$1.execute(SpringProjectContributionManager.java:112)
        at org.springframework.ide.eclipse.core.internal.project.SpringProjectContributionManager$9.run(SpringProjectContributionManager.java:291)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.springframework.ide.eclipse.core.internal.project.SpringProjectContributionManager.execute(SpringProjectContributionManager.java:294)
        at org.springframework.ide.eclipse.core.internal.project.SpringProjectContributionManager.build(SpringProjectContributionManager.java:110)
        at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
        at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
        at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
        at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
        at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
        at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
        at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
        at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    #354075 Reply

    support-swapna
    Moderator

    atomz4peace,

    Sorry that you are seeing this issue.

    1. Can you please go to MyEclipse > Migrate Workspace and see if the view shows any projects to be migrated ? If there are projects that need to be migrated,I recommend you migrate them. If there are errors showing, try clicking the Migration FAQ link on the migration dialog. It should advise on any errors.

    2. Can you please let us know if any changes are made to the project recently that might have caused the errors?

    3. Please switch to a new workspace, import the project and migrate it if MyEclipse prompts for migration and check if the issue persists.

    4. Please share the MyEclipse Version and Build Id from Help > About section.

    Let us know how it works for you.

    #354079 Reply

    atomz4peace
    Participant

    Hi,

    Thanks for the ideas. Here’s what I found:

    1) Nothing to be migrated

    2) I can’t think of what. I created a new project testing JSF2. This app is a JSF1. But nothing changed on the project itself.

    3) I did that and yes, it prompted for migration. When I then restarted ME, I got the same errors.

    4) Version: 2015 CI 12
    Build id: 13.0.0-20150323

    It doesn’t always throw the errors when opening ME. I outputs them when I open the spring explorer. I also have other errors on startup;

    Caught exception in FS.readPipe()

    and

    Project facet grails.app has not been defined. It is used in plugin com.vmware.vfabric.ide.eclipse.tcserver.core.

    But I don’t use grails at all.

    Any other ideas?

    #354085 Reply

    support-swapna
    Moderator

    atomz4peace,

    Thank you for the details.

    1. Is it possible for you to send us the project files to help us replicate the issue at our end? You can strip the project of its source code and send us all the .* files (.classpath,.project,.settings etc). Please send us the project files before the migration.

    2. Please also send us the .log file from the workspace where you saw errors even after migrating the project. The .log file is located at <workspace dir>/.metadata/.log.

    3.

    Project facet grails.app has not been defined. It is used in plugin com.vmware.vfabric.ide.eclipse.tcserver.core.

    It is “expected behavior”, since the tc server integration supports Grails apps in case you have the Grails tooling installed as well. If the Grails tooling is not installed, this message is being generated. It is a harmless error message which can be ignored.

    4. Please also let us know if you are using a Standard/Professional/Spring license.

    #354089 Reply

    Brian Fernandes
    Moderator

    Getting down to com/example/app1/webapp/EditApplicationController.class specifically, can you tell us what the path of EditApplicationController.java is? I assume it’s in the same project? Also, what’s the path to the compiledEditApplicationController.class file? It should be in your project too.

    Also, can you paste the snippet, in your spring bean configuration file where this controller is referenced?

    I’m wondering if there is something odd in your classpath setup that is preventing the model or the validator from finding these classes and thus leading to this error.

    From Swapna’s list earlier, would especially like to see the .classpath and the .springBeans file (post migration), in addition to the other files. Hopefully those will give us a better idea of what is going on.

    Sorry for the inconvenience caused.

    #354155 Reply

    atomz4peace
    Participant

    Thank you both, I’ll send you some files.

    #354159 Reply

    Brian Fernandes
    Moderator

    Thanks – I received the files. I see that the EditApplicationController class is referenced from the bean configuration in the web/WEB-INF/accessaudit-servlet.xml file.

    We still need to know, where is this class? Is it in the AccessAudit project or is it in another project (or is it in a referenced JAR file?) Could you tell me what the project relative path of the EditApplicationController.java and EditApplicationController.class files are?

    Are there any validation errors or warnings visible in the accessaudit-servlet.xml file? If not, just as a test, if, on line #215, you replace
    class=”com.handsonsecurity.accessaudit.webapp.EditApplicationController”>
    with
    class=”com.handsonsecurity.accessaudit.webapp.EditApplicationControlle”> (deliberately make a mistake in the name) and save the file, do you see an error / warning now, in the editor about the referenced class not being found?

    #354161 Reply

    atomz4peace
    Participant

    Thanks Brian,

    The class files are all in this project. It does not reference any other projects and the build dir is off the project home/build/classes/….. The source files are in project home/src/….

    I have no validation errors. When I remove the r like you suggest, it throws about 30 or so of those same errors in the error, one for each bean. It also then flags that line as an error in ME saying class not found.

    ME does the same thing no matter which bean is modified.

    Anything else to try?

    #354174 Reply

    Brian Fernandes
    Moderator

    atomz,

    Thanks very much for the details – we’ve actually been able to reproduce this internally.

    We’re working on a fix for this issue at high priority, should be something we can put out in the next CI release.

    Watch this space for updates and thank you for your patience!

    #389596 Reply

    support-swapna
    Moderator

    atomz,

    The fix for the issue is out with our latest CI release, MyEclipse 2015 CI 13.Please go to Help > Check for Updates and update to CI 13.

    Let us know if you see any issues.

    –Swapna
    MyEclipse Support

Viewing 10 posts - 1 through 10 (of 10 total)
Reply To: lots of spring ide errors

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