[jboss-jira] [JBoss JIRA] (WFLY-3891) Update appropriate web folders with newly changed schema

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005942#comment-13005942 ] 

Max Rydahl Andersen commented on WFLY-3891:
-------------------------------------------

yeah this needs updating to at least make the quickstart samples actually validate.

BUT one thing that worries me is what happens if WF8, 9 or future make additions/changes to the schema - how will users be able to know the right schemalocation ? Shouldn't these be versioned/use schema namespace additions instead of redefining the spec ? (similar to what seem to be done in standalone.xml xsd's ?)

> Update appropriate web folders with newly changed schema
> --------------------------------------------------------
>
>                 Key: WFLY-3891
>                 URL: https://issues.jboss.org/browse/WFLY-3891
>             Project: WildFly
>          Issue Type: Task
>            Reporter: Rob Stryker
>            Assignee: Jason Greene
>
> Recent changes to several ejb3 xsd files require the following web folders to be updated with the most up-to-date schema files:
> http://www.jboss.org/j2ee/schema/
> http://www.jboss.org/schema/jbossas/
> While this specific request comes due to WFLY-3189, it is related to WFLY-3434 about finding somewhere to host all schema. But  something tells me putting them all on wildfly.org is not sufficient. Tools like eclipse will see the namespace and schemaLocation in our examples online (Such as https://docs.jboss.org/author/display/AS71/jboss-ejb3.xml+Reference)  and copy-paste them verbatim. Those example files include things like the following:
> {code}
> 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://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
> {code}
> The important thing to note here is that it specifically points to http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd  and so that specific schema file needs to be updated at THAT url, not at the wildfly URL.  Tools like eclipse or other validators will try to fetch those specific urls.  
> If we intend to move all schemas to wildfly.org, then we probably need to update all examples to point to the new files as well. 
> At this point, the schemas I care most about are those mentioned in the following two PRs:
> https://github.com/wildfly/wildfly/pull/6739
> https://github.com/jboss/metadata/pull/72
> But obviously all appropriate or changed xsd's should be updated on the web urls if possible. 



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)