[JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20531:
-------------------------------------
I've added the linked ports blurb to the dialog :
!http://content.screencast.com/users/fbricon/folders/Jing/media/ad8e53fd-c0ec-4216-9cda-405a5e13a48c/00000256.png|width=525!
We can revisit (add icon, layout) in Beta2 if needed.
> Expose additional service ports from deploy docker image wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-20531
> URL: https://issues.jboss.org/browse/JBIDE-20531
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: docker
> Fix For: 4.3.1.Beta1
>
> Attachments: PortWindow.png, Service and routing page.png, service port edit dialog.png
>
>
> Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image
> * Also only remove those which were added
> * Only reset those which are defaults
> * Edit via double click
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21297?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21297:
--------------------------------------
Assignee: Victor Rubezhny
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
> --------------------------------------------------------------------
>
> Key: JBIDE-21297
> URL: https://issues.jboss.org/browse/JBIDE-21297
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Priority: Critical
> Labels: testfailure
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m...
> # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5}
> <case>
> <age>8</age>
> <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className>
> <duration>1.777</duration>
> <errorDetails>Content Assistant returned no proposals</errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79)
> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61)
> </errorStackTrace>
> <failedSince>61</failedSince>
> <name>testJstJsdtTernCAOnEcma5</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21297?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21297:
-----------------------------------
Priority: Major (was: Critical)
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
> --------------------------------------------------------------------
>
> Key: JBIDE-21297
> URL: https://issues.jboss.org/browse/JBIDE-21297
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Labels: testfailure
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m...
> # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5}
> <case>
> <age>8</age>
> <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className>
> <duration>1.777</duration>
> <errorDetails>Content Assistant returned no proposals</errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79)
> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61)
> </errorStackTrace>
> <failedSince>61</failedSince>
> <name>testJstJsdtTernCAOnEcma5</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21296) failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21296?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21296:
----------------------------------------
Works for me locally.
[~nickboldt] any idea why it fails on jenkins?
> failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
> --------------------------------------------------------------------------
>
> Key: JBIDE-21296
> URL: https://issues.jboss.org/browse/JBIDE-21296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
>
> {code}
> 18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
> com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
> on project org.jboss.tools.seam.core.test: IO Error
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
> 18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:17:13 ... 19 more
> 18:17:13 Caused by: java.io.EOFException
> 18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
> 18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
> 18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
> 18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
> 18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
> 18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
> 18:17:13 ... 21 more
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21298:
-------------------------------
Component/s: runtime-detection
(was: usage)
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
> ----------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Priority: Critical
> Labels: testfailure
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for usage component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21298:
----------------------------------
Summary: 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component
Key: JBIDE-21298
URL: https://issues.jboss.org/browse/JBIDE-21298
Project: Tools (JBoss Tools)
Issue Type: Task
Components: usage
Affects Versions: 4.3.1.Beta1
Reporter: Nick Boldt
Priority: Critical
*1 Test Failure(s) in JBIDE 4.3.1.Beta1 for usage component:*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
# [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
[Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for usage component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
-----
* {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
{code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
<case>
<age>5</age>
<className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
<duration>0.0050</duration>
<errorDetails>/qa/services/hudson/jboss-runtimes
expected:<0> but was:<1></errorDetails>
<errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
expected:<0> but was:<1>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.TestCase.assertEquals(TestCase.java:401)
at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
</errorStackTrace>
<failedSince>58</failedSince>
<name>testLoadSaveRuntimePaths</name>
<skipped>false</skipped>
<status>FAILED</status>
</case>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20764) Create Server Adapter for OpenShift 3 applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20764:
------------------------------------------
[~fbricon] can you please review https://github.com/jbosstools/jbosstools-openshift/pull/842?
> Create Server Adapter for OpenShift 3 applications
> --------------------------------------------------
>
> Key: JBIDE-20764
> URL: https://issues.jboss.org/browse/JBIDE-20764
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: new_and_noteworthy, openshift_v3
> Fix For: 4.3.1.Beta1
>
> Attachments: server adapter wizard.bmml, server adapter wizard.png
>
>
> get the actions available on OpenShift 3 resources in openshift explorer so you don't necessarily have to jump between the various views to work with openshift apps. This matches an existing feature in OpenShift 2. Upon project creation, a "Create server adapter" checkbox should be displayed.
> Server status= matching deployment pod status
> Possible menus:
> - Start/Stop
> - Show Web Console
> - Port Forwarding
> - Stream logs
> [~maxandersen] can you think of anything else?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21297:
----------------------------------
Summary: 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component
Key: JBIDE-21297
URL: https://issues.jboss.org/browse/JBIDE-21297
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common/jst/core
Affects Versions: 4.3.1.Beta1
Reporter: Nick Boldt
Priority: Critical
*1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m...
# [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds)
[Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
-----
* {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds)
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5}
<case>
<age>8</age>
<className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className>
<duration>1.777</duration>
<errorDetails>Content Assistant returned no proposals</errorDetails>
<errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79)
at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61)
</errorStackTrace>
<failedSince>61</failedSince>
<name>testJstJsdtTernCAOnEcma5</name>
<skipped>false</skipped>
<status>FAILED</status>
</case>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-3550:
-----------------------------------
I haven't tested with a jbds build yet, and so I'm going to leave this open despite it being past code freeze. I'll see what (or if) I can do anything for it tomorrow, just in case i can catch a respin. If I can't, then I'll punt to b2 sadly.
> Developer - autodetect the CDK in IDE
> -------------------------------------
>
> Key: JBDS-3550
> URL: https://issues.jboss.org/browse/JBDS-3550
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use
> Acceptance Criteria:
> * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect
> * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20536) Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20536?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-20536:
--------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements
> ---------------------------------------------------------------------------
>
> Key: JBIDE-20536
> URL: https://issues.jboss.org/browse/JBIDE-20536
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server, upstream
> Reporter: Rob Stryker
> Labels: xml_validation_quickstarts_eap7, xml_validation_quickstarts_wildfly, xml_validation_schema_error
> Fix For: 4.3.1.Beta2
>
>
> Several errors fail with the following error message:
> Referenced file contains errors (file:/home/rob/code/fuseide/fuseide/targetplatform/target/org.fusesource.ide.targetplatform.target.repo/../../../../../jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> The schema seems to fail to resolve any elements that have 'jboss' in them, for example:
> {code}
> <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/>
> {code}
> When looking at the entire xsd space, I see no attempt to reference or import any remote schema or any jboss schema url or namespace.
> The offending schema file is here:
> {code}<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
> targetNamespace="http://www.jboss.com/xml/ns/javaee"
> xmlns="http://www.jboss.com/xml/ns/javaee"
> xmlns:javaee="http://java.sun.com/xml/ns/javaee"
> elementFormDefault="qualified"
> attributeFormDefault="unqualified"
> version="2.0">
> <!-- xs:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="ejb-jar_3_1.xsd"/ -->
> <!-- xs:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"/ -->
> <xs:import namespace="http://java.sun.com/xml/ns/javaee"/>
> <xs:element name="ejb" type="javaee:jboss-ejb-beanType"/>
> <xs:element name="ejb-jar" type="javaee:jboss-ejb-jarType"/>
> <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/>
> <xs:element name="destination-jndi-name" type="xs:string" />
> <xs:element name="distinct-name" type="xs:string">
> <xs:annotation>
> <xs:documentation>
> The distinct-name for this EJB module.
> </xs:documentation>
> </xs:annotation>
> </xs:element>
> </xs:schema>
> {code}
> Perhaps I'm not understanding xml enough, but I kinda agree with the validator here, in that there's no clear way to resolve any of the jboss-* elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months