Hi: I want to get rid of the stacktrace soap is including in the fault detail whenever i throw an exception (I don't want clients to get all that junk). So i got a couple of questions someone might be able to help me: 1. What method should I redefine to send something else other than the stacktrace (first of all, can/should I?)? Is it - public void printStackTrace(PrintWriter s) or - public void printStackTrace(PrintStream s) or - public void printStackTrace() ? 2. After doing 1, can I change the <stackrtace> tag being used? 3. If i can't do 1 and/or 2, can i disable printing the stacktrace at all? Thanks in advanced and best regards, Ivo Conde e Silva Technical Department Taguspark - Edif. Inovação IV, nº 721 Porto Salvo 2780-920 Oeiras - Portugal E-mail: [EMAIL PROTECTED] Tel.: (+351) 214 220 660 Fax: (+351) 214 220 669 Tlm: (+351) 91 8742703 -----Original Message----- From: Travis Song [mailto:[EMAIL PROTECTED]] Sent: segunda-feira, 28 de Maio de 2001 12:05 To: [EMAIL PROTECTED] Subject: Re: SOAP without RPC Hi all. The message below is a sent message with one attachment in the sample.mime example. This example uses call to invoke remote method. Of course it is "SOAP with RPC", strictly speaking. Is there any way that we can add elements in the SOAP Evelope so that we can generate a message such as an ebXML. POST /soap/servlet/rpcrouter HTTP/1.0 Host: localhost:8070 Content-Type: multipart/related; boundary="----=_Part_0_529641.991045815370"; type="text/xml"; start="449364.991045815480.apache-soap.travis.travis" Content-Length: 884 SOAPAction: "" ------=_Part_0_529641.991045815370 Content-Type: text/xml; charset=utf-8 Content-Transfer-Encoding: 8bit Content-ID: <449364.991045815480.apache-soap.travis.travis> Content-Length: 468 <?xml version='1.0' encoding='UTF-8'?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <ns1:sendFile xmlns:ns1="urn:mime" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <addedfile href ="cid:5352659.991045815370.apache-soap.travis.travis"/> </ns1:sendFile> </SOAP-ENV:Body> </SOAP-ENV:Envelope> ------=_Part_0_529641.991045815370 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-ID: <5352659.991045815370.apache-soap.travis.travis> Content-Length: 4 bar! ------=_Part_0_529641.991045815370-- Travis Song Engineer eSum Technologies Inc., XML-Based Solutions R&D Sungbo Yeoksam Bldg, 833-2 Yeoksam-dong Kangnam-gu, Seoul Korea 135-080 Office 82 2 3451 2389 Mobile 82 19 9155 3557 MSN [EMAIL PROTECTED] ICQ 82395925 "You're only here for a short visit. Don't hurry. Don't worry. And be sure to smell the flowers along the way." ----- Original Message ----- From: Sanjiva Weerawarana <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, May 27, 2001 12:49 PM Subject: Re: SOAP without RPC > Yes, SOAP is actually a messaging system with RPC built on top > of that. > > Do you mean maintaining an HTTP session or a session in terms > of a SOAP header kinda thing? The prior is done by keeping a > cookie going (which Apache SOAP support for RPC Java things) > or by doing URL rewriting. In v2.2, each provider does its > own thing for sessions. > > If you want to use a SOAP header for session support that > provides the best end-to-end session opportunity. However, that > has to get accepted (and supported in WSDL, for example) > for it to make sense over time in open systems. > > Sanjiva. > > ----- Original Message ----- > From: "Halestino Pimentel" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, May 26, 2001 11:00 AM > Subject: SOAP without RPC > > > > Is it possible to use SOAP without RPC? > > If so, how can I manage the sessions? > > > > Thank's > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] >
BEGIN:VCARD VERSION:2.1 N:Silva;Ivo FN:Ivo Silva EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20001206T131126Z END:VCARD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]