[ https://jira.jboss.org/jira/browse/JBWS-2942?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2942: ---------------------------------- JBoss Forum Reference: http://community.jboss.org/message/528192#528192 Description: See http://community.jboss.org/message/528192#528192 . Basically that empty Metadata element, despite adding no real value info as it has not child/attributes (btw it's optional in the schema), appear to cause interoperability problems with Microsoft. This *might* be caused by the NativeEndpointReference's metadata attribute field that's always initialized with an empty Elements object (differently from the W3CEndpointReference). was: See http://community.jboss.org/message/528192#528192 . Basically that empty Metadata element, despite adding no real value info (it's optional btw in the schema), appear to cause interoperability problems with Microsoft. This *might* be caused by the NativeEndpointReference's metadata attribute field that's always initialized with an empty Elements object (differently from the W3CEndpointReference). -- 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/JBWS-2942?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-2942: --------------------------------- Fix Version/s: jbossws-native-3.3.0.Beta5 (was: jbossws-native-3.3) Assignee: Richard Opalka This is .NET bug because the EPR we're generating is perfectly valid. Anyway I'll fix our code base to don't serialize empty elements. -- 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