-
Bug
-
Resolution: Done
-
Major
-
jbossws-native-3.0.4
-
None
-
14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core 14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
-
Medium
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under the test suite to simulate this error.
- is incorporated by
-
-
- Closed
-
