Bug 1184236
| Summary: | Errors and warnings when importing jts quickstart into JBDS | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | sgilda | ||||
| Component: | Quickstarts | Assignee: | jboss-set | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikoleta Hlavickova <nziakova> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.4.0 | CC: | bsutter, cdewolf, fbricon, jkudrnac, manderse | ||||
| Target Milestone: | ER3 | Flags: | fbricon:
needinfo+
|
||||
| Target Release: | EAP 6.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-08-19 12:43:28 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
The jboss-ejb.xml schema issues are similar to the ones reported for the ejb-security-interceptors (Bug 1178748) and are documented in the common JBDS instructions hewre: https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.md Fixed all of the import errors other than the known jboss-ejb3 schema issues. This quickstart is fairly complex and requires a lot of manual configuration, so it does not include JBDS instructions. Fix is in this commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/b76a451d8e993e34d2563811d9d18778f0aa6959 There are no JBDS instructions in jts quickstart, should they be added? If yes, then there is also this one: Failed while installing JPA 2.0. org.osgi.service.prefs.BackingStoreException: Resource '/jboss-jts/application-component-1/.settings' does not exist. Fred, I am able to reproduce these. There are 3 bugs that display similar "Failed while installing JPA 2,0" errors: Bug 1178831 - kitchensink-ear Bug 1184236 - jts (this bug) Bug 1182606 - kitchensink-ml-ear Stacktrace: java.lang.RuntimeException: org.osgi.service.prefs.BackingStoreException: Resource '/jboss-jts/application-component-1/.settings' does not exist. at org.eclipse.jst.common.project.facet.core.libprov.internal.LibraryProviderFrameworkImpl.setCurrentProvider(LibraryProviderFrameworkImpl.java:224) at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.execute(LibraryInstallDelegate.java:597) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute_(JpaFacetActionDelegate.java:77) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:52) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:35) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:154) at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:109) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:250) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:163) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:133) at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob$1.doCreateMavenProjects(ImportMavenProjectsJob.java:73) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62) at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob.runInWorkspace(ImportMavenProjectsJob.java:82) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.osgi.service.prefs.BackingStoreException: Resource '/jboss-jts/application-component-1/.settings' does not exist. at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferencesGroup.save(ProjectFacetPreferencesGroup.java:174) at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferences.flush(ProjectFacetPreferences.java:412) at org.eclipse.jst.common.project.facet.core.libprov.internal.LibraryProviderFrameworkImpl.setCurrentProvider(LibraryProviderFrameworkImpl.java:220) ... 32 more Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-jts/application-component-1/.settings' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215) at org.eclipse.core.internal.resources.File.create(File.java:115) at org.eclipse.core.internal.resources.File.create(File.java:188) at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:358) at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:321) at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:307) at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferencesGroup.save(ProjectFacetPreferencesGroup.java:165) ... 34 more I've pushed a fix to m2e-wtp 1.2.0 (fr Eclipse Mars) see https://bugs.eclipse.org/bugs/show_bug.cgi?id=459810. @Fred Bricon: I will add a note to shared JBDS instruction page with a pointer to you fix. Thanks!
I can't reproduce this problem any more, even when I do a 'git clean' and start with a fresh workspace.
However, now I'm seeing this error on import:
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-exception, "http://java.sun.com/xml/ns/javaee":assembly-descriptor-entry}' is expected.
jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 28
XML Problem
I compared the jboss-ejb3.xml file to those in the JBoss EAP source and there are many like this that contain the iiop:iiop, however I don't see it in the schema definition. I'm not sure how to fix this one.
The schema has been uploaded but when I update the schemaLocation, it creates even more errors. @carlo: Do you know who could help with these XML and Schema validation errors? Updated the newly uploaded jboss-ejb-iiop_1_0.xsd schemaLocation, Remaining issues are documented in the shared JBDS guide. Fix is in this commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/03ab61ee4bf6df386d7f2dd097dcfede9f8eeb86 Created attachment 992261 [details]
Referenced File Error Details for jboss-ejb3-spec-2_0.xsd errors on import
Referenced File Error Details for jboss-ejb3-spec-2_0.xsd errors on import into JBDS.
To be clear, these are the issues I still see:
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF XML Problem
This one is addressed by the following bugs:
* https://bugzilla.redhat.com/show_bug.cgi?id=901186
* https://bugzilla.redhat.com/show_bug.cgi?id=1192591
Referenced file contains errors (jar:file:/home/sgilda/tools/jbdevstudio/studio/plugins/org.jboss.tools.as.catalog_3.0.1.Final-v20141209-0156-B106.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF XML Problem
I see 2 reported issues for the above:
* https://issues.jboss.org/browse/JBIDE-18435
* https://issues.jboss.org/browse/JBIDE-18576
They appear to be marked resolved. I'm not clear why I still see these errors.
Fred, do you know why I still see the second error?
This is an upstream (Eclipse WTP) issue. See https://issues.jboss.org/browse/JBIDE-18316 Thanks Fred! I added the warning to the list: https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.md#use-red-hat-jboss-developer-studio-or-eclipse-to-run-the-quickstarts Added the error to https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.md. Verified with EAP 6.4.0.ER3. |
Description of problem: ERRORS Project configurator "org.eclipse.m2e.wtp.jpa.internal.configurator.wtp" is not available. To enable full functionality, install the project configurator and run Maven->Update Project Configuration. pom.xml /jboss-jts-application-component-2 line 90 Maven Project Build Lifecycle Mapping Problem Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-ejb-plugin:2.3:ejb (execution: default, phase: package) pom.xml /jboss-jts-application-component-2 line 90 Maven Project Build Lifecycle Mapping Problem cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-exception, "http://java.sun.com/xml/ns/javaee":assembly-descriptor-entry}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 28 XML Problem WARNINGS schema_reference.4: Failed to read schema document 'jboss-ejb-iiop_1_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 28 XML Problem No connection specified for project. No database-specific validation will be performed. jboss-jts-application-component-1 JPA Problem Missing beans.xml file in the project jboss-jts-application-component-2. This file is required for bean archives [JSR-299 ยง12.1] jboss-jts-application-component-2 line 0 CDI Problem Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-jts-application-component-1 Build path JRE System Library Problem Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-jts-application-component-2 Build path JRE System Library Problem Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: