[ https://jira.jboss.org/jira/browse/JBIDE-3286?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-3286: --------------------------------------- Component/s: Webservices Fix Version/s: 3.0.0.cr1 Assignee: Feng Qian Grid, something you did or is it from the general set of xml in JBossAS ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3286?page=com.atlassian.jira.plu... ] Juergen Zimmermann commented on JBIDE-3286: ------------------------------------------- First of all: the new entries regarding DTD are working fine! For instance, the problems regarding jboss.xml, jboss-app.xml, jboss-web.xml and so on are gone. Thanks to Rob! However, the 2 new entries regarding XML schema are NOT working. I'll attach 2 screenshots: 1) "persistence.xml" shows that the "Key Type" within Preferences > XML > XML Catalog is "Namespace Name" 2) "jbossws" shows that both jboss-wsse-server.xml and standard-jaxws-endpoint-config.xml are claiming that "No grammar constraints (DTD or XML schema) detected for the document." Both catalog entries have the "Key Type": "Schema Location" instead of "Namespace Name" as it is provided for persistence.xsd Here is the contents of jboss-wsse-server.xml: <?xml version="1.0"?> <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd"> <config> <requires> <username/> </requires> </config> </jboss-ws-security> Here is the contents of standard-jaxws-endpoint-config.xml: <?xml version="1.0"?> <jaxws-config xmlns="urn:jboss:jaxws-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd"> <endpoint-config> <config-name>Standard WSSecurity Endpoint</config-name> <post-handler-chains> <javaee:handler-chain> <javaee:protocol-bindings> ##SOAP11_HTTP </javaee:protocol-bindings> <javaee:handler> <javaee:handler-name> WSSecurity Handler </javaee:handler-name> <javaee:handler-class> org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer </javaee:handler-class> </javaee:handler> </javaee:handler-chain> </post-handler-chains> </endpoint-config> </jaxws-config> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3286?page=com.atlassian.jira.plu... ] Juergen Zimmermann updated JBIDE-3286: -------------------------------------- Attachment: jbossws.jpg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-3286?page=com.atlassian.jira.plugin.s... ] Lukas Jungmann closed JBIDE-3286. --------------------------------- Closing old out-of date issues. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira