You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.
but rather is completely useless: Due to being declared as
"namespace='##other'", it does not accept any nested tags from "ws" namespace,
such as ws:addressing and ws:mtom.
s that are activated in this endpoint.
]]></xs:documentation>
</xs:annotation>
xs:complexType
<xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any
namespace='##other'/></xs:sequence>
</xs:complexType>
</xs:element>
Changing this by directly modifying the xsd to read
works around the issue, but in order to really solve the issue from its roots, I
think some XBean annotations must be changed (sorry, I am not at all familiar
with XBean).
Could you please release an updated version of the Spring extension to fix this?
Many thanks & best regards,
Andreas
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered:
Due to the following declaration in spring-jax-ws-core.xsd, the ws:features
element currently cannot be made to work as announced in
http://weblogs.java.net/blog/kohsuke/archive/2007/01/spring_support.html
<ws:service impl="foo.MyService">
ws:features
<ws:addressing />
</ws:features>
</ws:service>
but rather is completely useless: Due to being declared as
"namespace='##other'", it does not accept any nested tags from "ws" namespace,
such as ws:addressing and ws:mtom.
<xs:element name='features' minOccurs='0' maxOccurs='1'>
xs:annotation
xs:documentation<![CDATA[
{@link WebServiceFeature}
s that are activated in this endpoint.
]]></xs:documentation>
</xs:annotation>
xs:complexType
<xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any
namespace='##other'/></xs:sequence>
</xs:complexType>
</xs:element>
Changing this by directly modifying the xsd to read
<xs:sequence minOccurs='0' maxOccurs='unbounded'>xs:any/</xs:sequence>
works around the issue, but in order to really solve the issue from its roots, I
think some XBean annotations must be changed (sorry, I am not at all familiar
with XBean).
Could you please release an updated version of the Spring extension to fix this?
Many thanks & best regards,
Andreas
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered: