Sebastien,
thanks a lot for your help. I appreciate it.
Regards,
-R
Tardif, Sebastien wrote:
I never saw */*, if it's not a legal mime format maybe other tools will
be less forgiving that axis that by default when it doesn't regognize it
use DataHandler. DataHandler is a Java things. As an example some
platform may decide to give you a SoapPart instead and now you are stuck
to parse it.
-----Original Message-----
From: Rafael Gomez [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 11:10 AM
To: [EMAIL PROTECTED]
Subject: Re: Axis, SwA and Basic Profile 1.1
Tardif, Sebastien wrote:
What is the type of your attachment? If you don't know the content type
should be "application/octet-stream" this will give you an OctetStream
class which represent the data with a byte[].
Let me know if that doesn't answer your question.
Yes. What I understand is that depending of the mime:content 'type'
attribute value, different classes will be chosen by Axis for mapping:
application/octet-stream --> OctetStream ; multipart/mixed -->
MimeMultipart ; */* --> DataHandler ; ...
So just do <mime:content part="content"
type="application/octet-stream"/>
You probably want to be aware of
http://nagoya.apache.org/jira/browse/AXIS-1609 if you transfer big
attachment.
I understood that it is better to use DataHandler because of streaming
and thus not having all in memory. I saw the patch to wsdl2java.
But a DataHandler is exactly what I got when I changed to "*/*". So was
the patch needed? Should */* be avoided for any reason?
Rgds,
-R
-----Original Message-----
From: Rafael Gomez [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 18, 2004 9:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Axis, SwA and Basic Profile 1.1
Tardif, Sebastien wrote:
Axis does support SwA because I use it myself. Axis didn't really try
to read Basic Profile 1.1 and be compatible for it seems it is. With
recent patches and maybe even without them Axis should be better than
JWSDP 1.5 in this area.
I have run the SwA example provided by Axis. I got the following method
in SwaPort.java:
public java.lang.String swaSend(java.lang.String applicationName,
javax.mail.internet.MimeMultipart content)
Then I changed
<mime:content part="content" type="multipart/mixed"/>
to
<mime:content part="content" type="*/*"/>
and I got:
public java.lang.String swaSend(java.lang.String applicationName,
javax.activation.DataHandler content)
Why?
How do you use Axis' SwA support? Via 'multipart/Related' in binding
section plus 'multipart/mixed' type in non-soap:body mime:part like the
Axis' SwA example?
Rgds,
-R
smime.p7s
Description: S/MIME Cryptographic Signature
