[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Dmitry Geraskov commented on JBIDE-8765: ---------------------------------------- Max, do you know steps to reproduce? I guess I need to use somehow m2Eclipse, but not just install it and try to build Console Configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Dmitry Geraskov commented on JBIDE-8765: ---------------------------------------- I asked Vialy and he said the issue was reproduced always when you try to build Console Configuration related to jpa project. Now I can't reproduce it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Dmitry Geraskov commented on JBIDE-8765: ---------------------------------------- Yes, when the call is removed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8765: -------------------------------------- The issue can also be reproduced without m2eclipse. Some plugin that requires org.apache.xerces can be the cause of the problem (o.j.t.smooks.ui, o.j.t.common.model.ui, for instance). The issue can be reproduced in the following way: - disable the JPA validator - comment or remove the line 277 in the HibernateConsolePlugin.class(JptJpaCorePlugin.getJpaProjectManager().getJpaProjects()) - create a Seam Web Project - add the JPA facet 2.0 to the project - restart Eclipse - open the created Console Configuration Eclipse will throw an exception and will disable a content handler (smooks, m2eclipse ...). Problem will not happen later because the content handler will be disabled. It happens because of the way the ConsoleConfiguration classloader is defined(see ConsoleConfiguration.createClassLoader). The classloader overrides loadClass and findClass methods what forces it to use the context of the org.hibernate.eclipse plugin. However, the classloader doesn't override the getResource method and resources are being searched using the context of the plugin that called the action. If the plugin includes xerces, this classloader finds the META-INF/services/javax.xml.parsers.SaxParserFactory resource that defines org.apache.xerces.jaxp.SAXParserFactoryImpl Since classes are loaded using the classloader of the org.hibernate.eclipse plugin, this class can't be found. Eclipse throws the exception and disables the content handler. Solution: - add the getResource method to the ConsoleConfiguration classloader The line 277 in the HibernateConsolePlugin class can be commented/removed. This would also fix some other potential issues related to ConsoleConfiguration. We can't include the org.eclipse.jpt.jpa.core dependency to the org.hibernate.eclipse.console plugin and exclude the org.eclipse.jst.j2ee.web plugin. The org.eclipse.jpt.jpa.core plugin indirectly requires the org.eclipse.jst.j2ee.web plugin and can't be started without it (see JptJpaCorePlugin.java line 203-204). Attached is a patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Dmitry Geraskov commented on JBIDE-8765: ---------------------------------------- And I can't reproduce the issue with the steps. Is it reproduced always or only sometimes? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8765: -------------------------------------- The issue can be reproduced after restarting Eclipse the first time. The test project is placed on http://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/testjbide8765/.... You can try to reproduce the issue in the following way: - ensure the smooks.ui and/or m2e plugin are resolved - create a database connection named DefaultDS - create a JBoss AS runtime named jboss-5.1.0.GA Runtime - import the test project from the above mentioned url - comment or remove the line 277 in the HibernateConsolePlugin class(JptJpaCorePlugin.getJpaProjectManager().getJpaProjects()) - restart Eclipse - try to open the test hibernate configuration -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-8765: -------------------------------------- Dima, I have noticed that you removed the line 277 in the HibernateConsolePlugin.class class, but you didn't override getResource in the ConsoleConfiguration class. I can still reproduce the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Dmitry Geraskov commented on JBIDE-8765: ---------------------------------------- Snjezana, I committed the full patch(first part was committed as a fix ofanother issue). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8765?page=com.atlassian.jira.plugin... ] Jiri Peterka closed JBIDE-8765. ------------------------------- Didn't replicate the error in JBT 3.3.0.m1, L64 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira