Thank you, Roshan. I actually finally stumbled upon this yesterday. It
looks like my attachments are getting added just fine now. Do you know
how to print out the whole body of the returned message including mime
headers and attachments? On the client side I am using
MessageContext mcResponse = mepClient
.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
mcResponse.getEnvelope().serialize(System.out);
to send the message. I can look at the soap envelope with the above code
but I want to be able to see the mime headers and attachments as well to
check that the message was constructed properly. What command will just
dump the entire received message?
Thanks,
Tammy
Punnoose, Roshan wrote:
Tammy,
1) I am not sure how to get a whole of this, because I think the whole
message is compiled when it is actually being sent. But I'm not
completely sure.
2) Yeah I had problems with attachments when I first started. Basically,
instead of actually adding a direct Attachment to the MessageContext
like it looks like we are supposed to do from the API. I do it this way:
1) Create a DataHandler from an InputStream
2) Create an OMText element from the DataHandler and add it to
the OMElement you are sending:
OMTextImpl textData = (OMTextImpl)
fac.createOMText(dataHandler,
true);
content.addChild(textData);
Now if you aren't working with OMElements directly, then you are
probably using the stub generation and data binding, in which case, I do
not know how it handles Attachments. I'm guessing there if you define an
element as xsd:base64binary, it will treat it as an
Attachment/XOP:Include in an MTOM document.
Hope that helps.
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Tammy Dugan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 1:27 PM
To: [email protected]
Subject: Re: [axis2]HTTP Status code
Thanks. A couple more questions:
* what can I call from the OperationClient to see the entire returned
message including the message mime headers to make sure I have set them
properly?
* I need access to the outgoing message context so I can add
attachments. How can I do that? All the attachment examples I have seen
involve a direct call to a replyTo address. We are processing
synchronous requests so we don't have a reply address. Any ideas?
Thanks for your help.
Tammy
Punnoose, Roshan wrote:
MessageContext.getCurrentMessageContext() is returning most likely the
Message_In MessageContext. That holds the HttpServletResponse going
back, all I had to do was change the status code on this class.
Code:
HttpServletResponse resp = (HttpServletResponse)
getCurrentMessageContext()
.getProperty(HTTPConstants.MC_HTTP_SERVLETRESPONSE);
if (resp != null) {
resp.setStatus(status);
}
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Tammy Dugan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 1:04 PM
To: [email protected]
Subject: Re: [axis2]HTTP Status code
How did you get access to the MessageContext that got returned?
Tammy
Punnoose, Roshan wrote:
Sorry, I got this to work. I actually got the ServletResponse from
the
MessageContext and then changed the status code. Pretty simple :)
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Punnoose, Roshan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 12:58 PM
To: [email protected]
Subject: [axis2]HTTP Status code
Is there anyway to change the status code of the return? I have a web
service that returns custom SOAP faults, but it always returns it
with
the status code of 200, I want to change that to 500? Any way?
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Punnoose, Roshan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 11:30 AM
To: [email protected]
Subject: RE: [axis2]REST requests failing
Looks like the RESTUtil is sending the inputStream as null in the
processURLRequest, which will break the TransportUtils class either
way.
What can we do?
Roshan Punnoose
Phone: 301-497-6039
-----Original Message-----
From: Punnoose, Roshan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 11:24 AM
To: [email protected]
Subject: [axis2]REST requests failing
I have a REST GET request, and I keep getting this error:
java.lang.NullPointerException.
java.lang.NullPointerException
at java.io.Reader.<init>(Reader.java:61)
at
java.io.InputStreamReader.<init>(InputStreamReader.java:80)
at
org.apache.axis2.builder.XFormURLEncodedBuilder.extractParametersFromReq
uest(XFormURLEncodedBuilder.java:123)
at
org.apache.axis2.builder.XFormURLEncodedBuilder.processDocument(XFormURL
EncodedBuilder.java:77)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:120)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil
.java:98)
at
org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processUR
LRequest(AxisServlet.java:767)
at
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:236)
Any ideas?
Roshan Punnoose
Phone: 301-497-6039
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Tammy Dugan
Computer Programmer
Regenstrief Institute, Inc.
1050 Wishard Blvd., RG5
Indianapolis, IN 46202
(317) 630 - 7346
Confidentiality Notice: The contents of this message and any files transmitted
with it may contain confidential and/or privileged information and are intended
solely for the use of the named addressee(s). Additionally, the information
contained herein may have been disclosed to you from medical records with
confidentiality protected by federal and state laws. Federal regulations and
State laws prohibit you from making further disclosure of such information
without the specific written consent of the person to whom the information
pertains or as otherwise permitted by such regulations. A general authorization
for the release of medical or other information is not sufficient for this
purpose.
If you have received this message in error, please notify the sender by return
e-mail and delete the original message. Any retention, disclosure, copying,
distribution or use of this information by anyone other than the intended
recipient is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
