[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka edited comment on JBIDE-20346 at 6/21/19 7:09 AM:
------------------------------------------------------------------
[~jeffmaury] Update on this issue - the same issue still remains on EAP 7.0. Error msg here:
{code:java}
*Errors after project example import*
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
Referenced file contains errors (jar:file:/home/hudson/.m2/repository/p2/osgi/bundle/org.jboss.tools.as.catalog/3.7.0.v20190613-0743/org.jboss.tools.as.catalog-3.7.0.v20190613-0743.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..."
{code}
was (Author: zcervink):
[~jeffmaury] Update on this issue - the same issue still remains on EAP 7.0:
??Errors after project example import
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
Referenced file contains errors (jar:file:/home/hudson/.m2/repository/p2/osgi/bundle/org.jboss.tools.as.catalog/3.7.0.v20190613-0743/org.jboss.tools.as.catalog-3.7.0.v20190613-0743.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..."??
> Jts quickstart (EAP 6.4) contains XML validation errors
> -------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.x
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> 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 line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.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 line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka edited comment on JBIDE-20346 at 6/21/19 7:08 AM:
------------------------------------------------------------------
[~jeffmaury] Update on this issue - the same issue still remains on EAP 7.0:
??Errors after project example import
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
Referenced file contains errors (jar:file:/home/hudson/.m2/repository/p2/osgi/bundle/org.jboss.tools.as.catalog/3.7.0.v20190613-0743/org.jboss.tools.as.catalog-3.7.0.v20190613-0743.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..."??
was (Author: zcervink):
[~jeffmaury] Update on this issue - the same issue still remains on EAP 7.0:
{code:java}
Errors after project example import
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
Referenced file contains errors (jar:file:/home/hudson/.m2/repository/p2/osgi/bundle/org.jboss.tools.as.catalog/3.7.0.v20190613-0743/org.jboss.tools.as.catalog-3.7.0.v20190613-0743.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..."
{code}
> Jts quickstart (EAP 6.4) contains XML validation errors
> -------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.x
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> 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 line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.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 line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka commented on JBIDE-20346:
-----------------------------------------
[~jeffmaury] Update on this issue - the same issue still remains on EAP 7.0:
{code:java}
Errors after project example import
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected.
Referenced file contains errors (jar:file:/home/hudson/.m2/repository/p2/osgi/bundle/org.jboss.tools.as.catalog/3.7.0.v20190613-0743/org.jboss.tools.as.catalog-3.7.0.v20190613-0743.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..."
{code}
> Jts quickstart (EAP 6.4) contains XML validation errors
> -------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.x
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> 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 line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.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 line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka reassigned JBIDE-20346:
---------------------------------------
Assignee: Jeff MAURY
> Jts quickstart (EAP 6.4) contains XML validation errors
> -------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.12.x
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> 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 line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.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 line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim commented on JBDS-4777:
----------------------------------------
I consider this issue resolved given that it's about documenting how to use the server adapter with debugging-switch, debugging-port and deployment directory provided in the docker image. The exact steps are provided 2 comment further up: https://issues.jboss.org/browse/JBDS-4777?focusedCommentId=13747480&page=...
Furthermore an enhancement for the particular use case was provided.
[~mgreenbe] I encourage you to file existing shortcomings and suggested improvements for the tooling in their own jira issues. We'll try to address those asap.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift
> Fix For: 12.12.0.GA
>
> Attachments: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-10.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png, screenshot-7.png, screenshot-8.png, screenshot-9.png
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim updated JBDS-4777:
-----------------------------------
Fix Version/s: 12.12.0.GA
(was: 12.x)
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift
> Fix For: 12.12.0.GA
>
> Attachments: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-10.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png, screenshot-7.png, screenshot-8.png, screenshot-9.png
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim edited comment on JBDS-4777 at 6/21/19 6:18 AM:
-----------------------------------------------------------------
[~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from [https://github.com/jbosstools/jbosstools-openshift.git|http://example.com....
was (Author: adietish):
[~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from [upstream](https://github.com/jbosstools/jbosstools-openshift.git) /master.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-10.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png, screenshot-7.png, screenshot-8.png, screenshot-9.png
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim edited comment on JBDS-4777 at 6/21/19 6:18 AM:
-----------------------------------------------------------------
[~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from [upstream|https://github.com/jbosstools/jbosstools-openshift.git]/master.
was (Author: adietish):
[~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from [https://github.com/jbosstools/jbosstools-openshift.git|http://example.com....
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-10.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png, screenshot-7.png, screenshot-8.png, screenshot-9.png
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim edited comment on JBDS-4777 at 6/21/19 6:17 AM:
-----------------------------------------------------------------
[~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from [upstream](https://github.com/jbosstools/jbosstools-openshift.git) /master.
was (Author: adietish):
[~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from upstream (https://github.com/jbosstools/jbosstools-openshift/) /master.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-10.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png, screenshot-7.png, screenshot-8.png, screenshot-9.png
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.... ]
André Dietisheim commented on JBDS-4777:
----------------------------------------
[~mgreenbe] PR https://github.com/jbosstools/jbosstools-openshift/pull/1847 was merged into master, topic branch removed. The improvement that it's addressing is now available in nightly binary builds. If you want to keep using our plugins source, simply switch to master and pull from upstream (https://github.com/jbosstools/jbosstools-openshift/pull/1847) /master.
> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
> Key: JBDS-4777
> URL: https://issues.jboss.org/browse/JBDS-4777
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 12.11.0.GA
> Environment: CodeReady Studio 12.11
> Reporter: Rick Wagner
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift
> Fix For: 12.x
>
> Attachments: Dockerfile, Problem_Description.pdf, screenshot-1.png, screenshot-10.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png, screenshot-7.png, screenshot-8.png, screenshot-9.png
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months