Hi Patric - I filed one for you and fixed the bug
http://jira.codehaus.org/browse/XFIRE-399
- Dan
Dan Diephouse wrote:
This looks like a quirk with our base64 handling. If MTOM is enabled,
we don't even try to read in the byte[] from the document, we look for
the attachment instead. This is clearly a bug. Please file a JIRA and
we'll get this fixed. Thanks,
- Dan
Patric Fornasier wrote:
Hi,
I enabled MTOM on both client and server and it works fine.
However, when I disable MTOM on the server (and leave MTOM enabled on
the client), service.createProblem() returns null.
public void testDynamicClient() throws Exception {
Service serviceModel = new
ObjectServiceFactory().create(BigProblemService.class);
BigProblemService service = (BigProblemService) new
XFireProxyFactory().create(serviceModel,
"http://fedora:8080/toy-problem/services/BigProblemService";);
Client client = ((XFireProxy)
Proxy.getInvocationHandler(service)).getClient();
client.setProperty("mtom-enabled", "true");
byte[] bytes = service.createProblem();
writeToFile(bytes, new File("c:/dynamic.png"));
}
Is this normal behaviour? Shouldn't the client be able to automatically
detect wheter a message is sent using MTOM and then if appropriate swith
to 'MTOM mode' if necessary?
Cheers,
patric
--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain
legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete
both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or
unauthorised
amendment. This notice should not be removed.
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
