[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBDS-3119:
-----------------------------------------
Ok. I wish I could create a simpler way to reproduce this with SwitchYard, but here it is:
1. Start with a clean Luna SR2 install
2. Add update sites:
* Luna - http://download.eclipse.org/releases/luna
* JBTIS Luna - http://download.jboss.org/jbosstools/updates/development/luna/integration...
* SY 2.0.1.Beta1 - http://download.jboss.org/jbosstools/updates/development/luna/integration...
3. Install SwitchYard tools
4. Ensure that Help->Preferences, XML->XML Files->Validation - "Honour all XML schema locations" is turned on.
5. Import bean-service-quickstart. It should validate the project during build, if not - File->Validate at root of project.
I'm seeing all sorts of errors, as in the list below.
{code}
Description Resource Path Location Type
cvc-complex-type.2.4.a: Invalid content was found starting with element 'implementation.bean'. One of '{"http://docs.oasis-open.org/ns/opencsa/sca/200912":documentation, "http://docs.oasis-open.org/ns/opencsa/sca/200912":implementation}' is expected. switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 28 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'implementation.bean'. One of '{"http://docs.oasis-open.org/ns/opencsa/sca/200912":documentation, "http://docs.oasis-open.org/ns/opencsa/sca/200912":implementation}' is expected. switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 34 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'interface.java'. One of '{"http://docs.oasis-open.org/ns/opencsa/sca/200912":documentation, "http://docs.oasis-open.org/ns/opencsa/sca/200912":interface, "http://docs.oasis-open.org/ns/opencsa/sca/200912":binding, "http://docs.oasis-open.org/ns/opencsa/sca/200912":callback, "http://docs.oasis-open.org/ns/opencsa/sca/200912":requires, "http://docs.oasis-open.org/ns/opencsa/sca/200912":policySetAttachment, "http://docs.oasis-open.org/ns/opencsa/sca/200912":extensions}' is expected. switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 30 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'interface.java'. One of '{"http://docs.oasis-open.org/ns/opencsa/sca/200912":documentation, "http://docs.oasis-open.org/ns/opencsa/sca/200912":interface, "http://docs.oasis-open.org/ns/opencsa/sca/200912":binding, "http://docs.oasis-open.org/ns/opencsa/sca/200912":callback, "http://docs.oasis-open.org/ns/opencsa/sca/200912":requires, "http://docs.oasis-open.org/ns/opencsa/sca/200912":policySetAttachment, "http://docs.oasis-open.org/ns/opencsa/sca/200912":extensions}' is expected. switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 36 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'interface.java'. One of '{"http://docs.oasis-open.org/ns/opencsa/sca/200912":documentation, "http://docs.oasis-open.org/ns/opencsa/sca/200912":interface, "http://docs.oasis-open.org/ns/opencsa/sca/200912":binding, "http://docs.oasis-open.org/ns/opencsa/sca/200912":callback, "http://docs.oasis-open.org/ns/opencsa/sca/200912":requires, "http://docs.oasis-open.org/ns/opencsa/sca/200912":policySetAttachment, "http://docs.oasis-open.org/ns/opencsa/sca/200912":extensions}' is expected. switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 39 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'transform.java'. One of '{"urn:switchyard-config:switchyard:1.0":transform}' is expected. switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 44 XML Problem
cvc-complex-type.2.4.a: Invalid content was found starting with element 'validate.java'. One of '{"urn:switchyard-config:switchyard:1.0":validate}' is expected. switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 48 XML Problem
Referenced file contains errors (jar:file:/C:/Runtimes4/empty-lunasr2/plugins/org.switchyard.tools.xsd_2.0.1.v20150727-2018-H8-Beta1.jar!/schema/bean_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 1 XML Problem
Referenced file contains errors (jar:file:/C:/Runtimes4/empty-lunasr2/plugins/org.switchyard.tools.xsd_2.0.1.v20150727-2018-H8-Beta1.jar!/schema/sca-binding-jca-1.1-cd04-rev2.xsd). For more information, right click on the message in the Problems View and select "Show Details..." switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 1 XML Problem
Referenced file contains errors (jar:file:/C:/Runtimes4/empty-lunasr2/plugins/org.switchyard.tools.xsd_2.0.1.v20150727-2018-H8-Beta1.jar!/schema/sca-binding-jms-1.1-csd05.xsd). For more information, right click on the message in the Problems View and select "Show Details..." switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 1 XML Problem
Referenced file contains errors (jar:file:/C:/Runtimes4/empty-lunasr2/plugins/org.switchyard.tools.xsd_2.0.1.v20150727-2018-H8-Beta1.jar!/schema/transform_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 1 XML Problem
Referenced file contains errors (jar:file:/C:/Runtimes4/empty-lunasr2/plugins/org.switchyard.tools.xsd_2.0.1.v20150727-2018-H8-Beta1.jar!/schema/validate_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." switchyard.xml /switchyard-bean-service/src/main/resources/META-INF line 1 XML Problem
No grammar constraints (DTD or XML Schema) referenced in the document. order.xml /switchyard-bean-service/src/test/resources/xml line 1 XML Problem
No grammar constraints (DTD or XML Schema) referenced in the document. orderAck.xml /switchyard-bean-service/src/test/resources/xml line 1 XML Problem
No grammar constraints (DTD or XML Schema) referenced in the document. soap-request.xml /switchyard-bean-service/src/test/resources/xml line 1 XML Problem
No grammar constraints (DTD or XML Schema) referenced in the document. soap-response.xml /switchyard-bean-service/src/test/resources/xml line 1 XML Problem
{code}
> XML Schema validation fails when importing external schema
> ----------------------------------------------------------
>
> Key: JBDS-3119
> URL: https://issues.jboss.org/browse/JBDS-3119
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-dependencies, server
> Affects Versions: 8.0.0.Beta3
> Reporter: Mustafa Musaji
> Assignee: Rob Stryker
> Attachments: bean-service-quickstart.zip
>
>
> Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741
> This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20400) Add support for EJB Project configuration
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-20400:
-----------------------------------
Summary: Add support for EJB Project configuration
Key: JBIDE-20400
URL: https://issues.jboss.org/browse/JBIDE-20400
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Fred Bricon
There's currently no ejb plugin in gradle that'd help us automatically configure the EJB Facet in eclipse.
This requires some investigation on what is doable, what can be inferred reliably from the project configuration and its dependencies (eg. has no war/ear plugin but depends on the ejb-api jar)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20399) Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-20399:
------------------------------------
Summary: Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2
Key: JBIDE-20399
URL: https://issues.jboss.org/browse/JBIDE-20399
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, openshift
Affects Versions: 4.3.0.Beta2
Reporter: Len DiMaggio
Attachments: Screenshot-4.png, Screenshot-5.png
See attached screen shots - any combination of user inputs returns this error if the user attempts to create a new v3 application:
The server type, credentials, or auth scheme might be incorrect. Could not get resource ~ in namespace : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /oapi was not found on this server.</p>
<p>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.</p>
<hr>
<address>Apache/2.2.15 (Red Hat) Server at openshift.redhat.com Port 443</address>
</body></html>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20399) Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20399?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-20399:
---------------------------------
Attachment: Screenshot-5.png
Screenshot-4.png
Also - the error is displayed in an awkward manner - see screenshots.
> Cannot create new OpenShift v3 application when launching wizard from Central in 4.3.0.beta2
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-20399
> URL: https://issues.jboss.org/browse/JBIDE-20399
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Len DiMaggio
> Attachments: Screenshot-4.png, Screenshot-5.png
>
>
> See attached screen shots - any combination of user inputs returns this error if the user attempts to create a new v3 application:
> The server type, credentials, or auth scheme might be incorrect. Could not get resource ~ in namespace : <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>404 Not Found</title>
> </head><body>
> <h1>Not Found</h1>
> <p>The requested URL /oapi was not found on this server.</p>
> <p>Additionally, a 403 Forbidden
> error was encountered while trying to use an ErrorDocument to handle the request.</p>
> <hr>
> <address>Apache/2.2.15 (Red Hat) Server at openshift.redhat.com Port 443</address>
> </body></html>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3492:
--------------------------------
CDW qa_ack: + (was: ?)
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 9.0.0.CR1
>
> Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3492:
--------------------------------
CDW devel_ack: + (was: ?)
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 9.0.0.CR1
>
> Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3492:
-----------------------------
CDW release: + (was: ?)
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 9.0.0.CR1
>
> Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3492:
--------------------------------
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 9.0.0.CR1
>
> Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3492:
--------------------------------
Priority: Optional (was: Major)
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 9.0.0.CR1
>
> Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months