Skip to content
Browse files

Documentation improved, no functionality change.

  • Loading branch information...
1 parent dd9f118 commit 2b32a448c8c2b8ce1de619b1611b00ca939d03c8 @aknrdureegaesr committed May 10, 2012
Showing with 12 additions and 2 deletions.
  1. +7 −1 README.markdown
  2. +5 −1 twoAttachmentStreamingTest/src/demo/mtom/streamsending/client/Driver.java
View
8 README.markdown
@@ -1,4 +1,4 @@
-This demonstrates a regression in MTOM streaming in Apache CXF.
+This demonstrates a regression in MTOM streaming in Apache CXF, recently fixed.
## What you run
@@ -47,6 +47,12 @@ _Outcome seen: Same as plain JDK 6._
This is a regression, CXF 2.6.0 no longer does MTOM streaming properly.
+### CXF version 2.6.1
+
+* Fixed according to [https://issues.apache.org/jira/browse/CXF-4298]
+* TODO: Retest.
+
+(Apache fixes considerably faster than I can find the time to retest! Wow!)
### For the record
View
6 twoAttachmentStreamingTest/src/demo/mtom/streamsending/client/Driver.java
@@ -155,8 +155,12 @@ public static void initializeClient() {
// Activate streaming on the client side,
// so it is not the client that stores the attachments before sending.
- // In the author's experience, this always works:
+ // In the author's experience, this always works, irregardless of WS stack used:
@SuppressWarnings("restriction")
+ // If you see an error in Eclipse here:
+ // Navigate Window / Preferences / Java / Compiler/ Errors/Warnings /
+ // Deprecated and restricted API / Forbidden reference (access rules):
+ // and change from "Error" to "Warning".
String doChunking = com.sun.xml.internal.ws.developer.JAXWSProperties.HTTP_CLIENT_STREAMING_CHUNK_SIZE;
((BindingProvider) port).getRequestContext().put(doChunking, 4096);
}

0 comments on commit 2b32a44

Please sign in to comment.
Something went wrong with that request. Please try again.