[
https://issues.jboss.org/browse/WFLY-5250?page=com.atlassian.jira.plugin....
]
Rob Stryker updated WFLY-5250:
------------------------------
Description:
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar
xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you
replace this with:
{code}
urn:iiop
http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one
example:
{code}
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}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a
descriptor that passes validation.
was:
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar
xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop
http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop
http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you
replace this with:
{code}
urn:iiop
http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one
example:
{code}
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}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a
descriptor that passes validation.
wildfly-jts-application-component-2 quickstart fails to validate in
eclipse
---------------------------------------------------------------------------
Key: WFLY-5250
URL:
https://issues.jboss.org/browse/WFLY-5250
Project: WildFly
Issue Type: Bug
Reporter: Rob Stryker
Assignee: Jason Greene
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar
xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you
replace this with:
{code}
urn:iiop
http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one
example:
{code}
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}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a
descriptor that passes validation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)