[ https://issues.jboss.org/browse/JBWS-2570?page=com.atlassian.jira.plugin.... ] Steve Cohen commented on JBWS-2570: ----------------------------------- Can we please get some activity on this? This bug is almost two years old and it is biting me now, using a different platform jbossas-5.1.0GA and jbossws-native-3.4.0GA. Even a comment? Is this ever going to be fixed? I believe I understand why it happens. It happens because the supplied WSDL is transformed in deployment, for some reason. Instead of my original WSDL and schema JBOSS converts it to an "equivalent" format that is quite parseable, but which breaks the schema locator which has no way of finding the original schema which has been renamed. Here is my WSDL after JBOSS deploys it: <?xml version="1.0" encoding="UTF-8" ?> - <definitions name="SampleService" targetNamespace="http://org.javactivity/SampleService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://org.javactivity/SampleService/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://org.javactivity/SampleService" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <import location="http://localhost:8080/sample?wsdl&resource=SampleServicePort_PortType8512585196678794077.wsdl" namespace="http://org.javactivity/SampleService/" /> - <service name="SampleService"> - <port binding="ns1:SampleServicePortBinding" name="SampleSOAP"> <soap:address location="http://localhost:8080/sample" /> </port> </service> </definitions> Obviously, I did not name my import SampleServicePort_PortType8512585196678794077.wsdl. I am attaching the wsdl and schema that I actually built. If there is a workaround for this problem can someone at least please post it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBWS-2570?page=com.atlassian.jira.plugin.... ] Steve Cohen edited comment on JBWS-2570 at 10/7/11 7:00 PM: ------------------------------------------------------------ Can we please get some activity on this? This bug is almost two years old and it is biting me now, using a different platform jbossas-5.1.0GA and jbossws-native-3.4.0GA. Even a comment? Is this ever going to be fixed? I believe I understand why it happens. It happens because the supplied WSDL is transformed in deployment, for some reason. Instead of my original WSDL and schema JBOSS converts it to an "equivalent" format that is quite parseable, but which breaks the schema locator which has no way of finding the original schema which has been renamed. Here is my WSDL after JBOSS deploys it: <?xml version="1.0" encoding="UTF-8" ?> - <definitions name="SampleService" targetNamespace="http://org.javactivity/SampleService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://org.javactivity/SampleService/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://org.javactivity/SampleService" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <import location="http://localhost:8080/sample?wsdl&resource=SampleServicePort_PortType8512585196678794077.wsdl" namespace="http://org.javactivity/SampleService/" /> - <service name="SampleService"> - <port binding="ns1:SampleServicePortBinding" name="SampleSOAP"> <soap:address location="http://localhost:8080/sample" /> </port> </service> </definitions> Obviously, I did not name my import SampleServicePort_PortType8512585196678794077.wsdl. I am attaching the wsdl and schema that I actually built. If there is a workaround for this problem can someone at least please post it? I'll also note that the same problem happens with an all-in-one wsdl. Or is there an easier way to validate on the server? was (Author: stevecoh4): Can we please get some activity on this? This bug is almost two years old and it is biting me now, using a different platform jbossas-5.1.0GA and jbossws-native-3.4.0GA. Even a comment? Is this ever going to be fixed? I believe I understand why it happens. It happens because the supplied WSDL is transformed in deployment, for some reason. Instead of my original WSDL and schema JBOSS converts it to an "equivalent" format that is quite parseable, but which breaks the schema locator which has no way of finding the original schema which has been renamed. Here is my WSDL after JBOSS deploys it: <?xml version="1.0" encoding="UTF-8" ?> - <definitions name="SampleService" targetNamespace="http://org.javactivity/SampleService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="http://org.javactivity/SampleService/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://org.javactivity/SampleService" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <import location="http://localhost:8080/sample?wsdl&resource=SampleServicePort_PortType8512585196678794077.wsdl" namespace="http://org.javactivity/SampleService/" /> - <service name="SampleService"> - <port binding="ns1:SampleServicePortBinding" name="SampleSOAP"> <soap:address location="http://localhost:8080/sample" /> </port> </service> </definitions> Obviously, I did not name my import SampleServicePort_PortType8512585196678794077.wsdl. I am attaching the wsdl and schema that I actually built. If there is a workaround for this problem can someone at least please post it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBWS-2570?page=com.atlassian.jira.plugin.... ] Steve Cohen commented on JBWS-2570: ----------------------------------- Sorry, that's a bit above my newbie status at this point. Could you at least confirm that I am on the right track - that SchemaValidation fails because the schema cannot be located once the JBoss deployer has transformed it? I'm pretty sure this is true because I am making progress on a bandaid. This workaround uses Maven to copy the schema to another web project deployed in the same ear as web content (/{context-root}/schema.xsd). This can then be seen by the @SchemaValidation tag. It seems to work pretty well, but it's obviously a bandaid, However, it's a bandaid that tends to confirm my hypothesis - if JBossws could only see the schema, it could use it to validate. Perhaps you might be able to enlighten me on why JBoss transforms the wsdl and schema in the first place? This seems to be a pretty fundamental thing and I'm sure there must be a good reason for it. Could it be somehow made optional without completely hosing jbossws? I have a feeling that this is a minefield. My goal was simply to use JBoss and I may not have enough time to look this deeply into it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBWS-2570?page=com.atlassian.jira.plugin.... ] Steve Cohen commented on JBWS-2570: ----------------------------------- Another solution is here: http://javaeenotes.blogspot.com/2011/02/when-schemavalidation-in-jax-ws-w... It looks complicated but it isn't. Just do what the guy says, copy the code and it works. Basically, he's defining a handler for validation and using that annotation instead of the @SchemaValidation. The handler requires a URL for the schema be passed in. Which is fine since you probably coded the Schema as a separate file to begin with. At least until the bug is fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira