[jbosstools-issues] [JBoss JIRA] (JBIDE-23311) Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-23311:
-------------------------------------

[~mmalina] If you notice, all of the listed "missing" schema are standard jee schema. They are included in WTP. We do not include them because it will confuse stuff and we already depend on WTP. 

As for how to verify, I really don't know. I've always just tried autocomplete for specific schema if I want to test them and make sure it works. 

My unit tests use WTP API to create a new xml file based on the schema and verify that the root element is correct. I don't test autocomplete for various parts of the schema. 

Close this jira if you're satisified with this response. 

> Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1
> -----------------------------------------------------------------
>
>                 Key: JBIDE-23311
>                 URL: https://issues.jboss.org/browse/JBIDE-23311
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: server
>    Affects Versions: 4.4.2.AM2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> Rather than reopening JBIDE-23161 to ask you about some discrepancies that I found, I am opening this JIRA.
> I compared the contents of org.jboss.tools.as.catalog_3.2.2.v20160923-0424.jar and what's in the wildfly 10.1.0 zip. And there are some diffs. I understand that there will always be more in the plugin - we keep some previous versions. But there are many xsd files missing in the plugin:
> {code}
> $ comm -23 xsd-list-wf.txt xsd-list-plugin.txt 
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> nattura:jar rasp$ find . -name javaee_7.xsd
> nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt 
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> nattura:jar rasp$ 
> nattura:jar rasp$ 
> nattura:jar rasp$ 
> nattura:jar rasp$ 
> nattura:jar rasp$ 
> nattura:jar rasp$ 
> nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt 
> application-client_6.xsd
> application-client_7.xsd
> application_1_4.xsd
> application_5.xsd
> application_6.xsd
> application_7.xsd
> ejb-jar_2_1.xsd
> ejb-jar_3_0.xsd
> ejb-jar_3_1.xsd
> ejb-jar_3_2.xsd
> j2ee_1_4.xsd
> j2ee_jaxrpc_mapping_1_1.xsd
> j2ee_web_services_1_1.xsd
> j2ee_web_services_client_1_1.xsd
> javaee_5.xsd
> javaee_6.xsd
> javaee_7.xsd
> javaee_web_services_1_2.xsd
> javaee_web_services_1_3.xsd
> javaee_web_services_1_4.xsd
> javaee_web_services_client_1_2.xsd
> javaee_web_services_client_1_3.xsd
> javaee_web_services_client_1_4.xsd
> jbxb_1_0.xsd
> jsp_2_0.xsd
> jsp_2_1.xsd
> jsp_2_2.xsd
> jsp_2_3.xsd
> orm_1_0.xsd
> persistence_1_0.xsd
> persistence_2_0.xsd
> web-app_2_4.xsd
> web-app_2_5.xsd
> web-app_3_0.xsd
> web-app_3_1.xsd
> web-common_3_0.xsd
> web-common_3_1.xsd
> web-facelettaglibrary_2_2.xsd
> web-facesconfig_1_2.xsd
> web-facesconfig_2_2.xsd
> web-fragment_3_0.xsd
> web-fragment_3_1.xsd
> web-jsptaglibrary_2_0.xsd
> web-jsptaglibrary_2_1.xsd
> web-partialresponse_2_2.xsd
> {code}
> But I randomly checked one and it was visible in Preferences -> XML -> XML Catalog. My guess is that these are not ours so they will be present in some Eclipse plugin and we don't need to add them. Can you confirm this?
> And in that case, what would you recommend as the best option to verify that our catalog is correct and also that the jboss.org.schema git repo is correct?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)