[jbosstools-issues] [JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog

[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-19910: ------------------------------------------ So these are schemas/dtds referenced in wildfly and javaee7 samples http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit... http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-policy-sche... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-context-schema-... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-policy-schema-o... http://glassfish.org/dtds/glassfish-resources_1_5.dtd http://glassfish.org/dtds/glassfish-web-app_3_0-1.dtd http://java.sun.com/dtd/properties.dtd http://java.sun.com/xml/ns/j2ee/connector_1_6.xsd - redirects http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd - redirects http://java.sun.com/xml/ns/javaee/application_7.xsd - redirects http://jboss.org/schema/arquillian/arquillian_1_0.xsd http://maven.apache.org/xsd/assembly-1.1.2.xsd http://www.infinispan.org/schemas/infinispan-config-6.0.xsd http://jboss.org/ironjacamar/schema/ironjacamar_1_0.xsd http://jboss.org/j2ee/dtd/service-ref_4_0.dtd http://jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd http://jboss.org/j2ee/schema/jboss-web_6_0.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/connector_1_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_serv... http://www.puppycrawl.com/dtds/configuration_1_2.dtd http://www.w3.org/2001/XMLSchema.dtd http://www.w3.org/2001/datatypes.dtd http://www.w3.org/2006/03/addressing/ws-addr.xsd http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd http://www.w3.org/ns/ws-policy - not xsd/dtd http://www.ws-i.org/Testing/Tools/2004/12/AP10_BP11_SSBP10_TAD.xml http://www.ws-i.org/Testing/Tools/2005/01/SSBP10_BP11_TAD_1-0.xml I've also taken a look at how cache works in Eclipse to see why i thought that wsdl validator doesn't use it. I can say that both XML and WSDL validators are using cache. Cache however doesn't cache resource that in http header define cache-control = no-cache. These resources are never cached and always downloaded again and again. It's true that when no-cache is defined, resource shouldn't be cached, but some "temporary" cache valid at least for one validation run could be used. This is a room for a performance boost - I removed no-cache check and made a comparison with wildfly import: clean cache, maven offline, no-cache is checked (so default eclipse) 3 runs: 661s,684s,653s = average 666 clean cache, maven offline, no-cache is NOT checked 3 runs: 556s, 540s,549s = average 548s [~maxandersen] WDYT ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)