RE: SOAP:Header question

@ws.apache.orgSubject: Re: SOAP:Header questionTry specifying the body parts before the header parts -- both in the messages and in the binding. That should get rid of the warnings.Anne On 10/26/05, Tysnes Are Thobias [EMAIL PROTECTED] wrote: Hello Anne! Thanks for your reply

RE: SOAP:Header question

Hello! I have som issues with SOAP:Header. The solution with multiple parts in a message raise a warning in .NET: Warning: This web reference does not conform to WS-I Basic Profile v1.1. R2210: If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a

RE: how can i see xml exange between client and server

TCPMonitor (supplied with axis) is the tool you want Cheers, Are T. Tysnes -Original Message- From: Thibaut Lassalle [mailto:[EMAIL PROTECTED] Sent: 24. juni 2005 14:53 To: axis-user@ws.apache.org Subject: how can i see xml exange between client and server hi, i use the wsdl2java

Data-binding in Axis 1.2

Hello! Axis 1.1's data-binding framework did miss some features which made room for other tools like Castor to be used instead. (validation ++) Has this changed in Axis 1.2 !? Is the data-binding in Axis 1.2 as good as Castor !? Maybe better !? :o) Cheers, Are T. Tysnes

WebSphere 5.1 does not run Web Applications running Axis SOAP Engine

Hello! We are running WebSphere Application Servers in production and are planing on deploying a Web Application (Web Services, Axis 1.2 and Castor). There are some issues deploying Web Applications containing Axis in WebSphere because IBM is using a home-made version of Axis inside WebSphere.

RE: WebSphere 5.1 does not run Web Applications running Axis SOAPEngine

finding the solution through google. -Original Message- From: Tysnes Are Thobias [mailto:[EMAIL PROTECTED] Sent: 04 May 2005 8:54 To: axis-user@ws.apache.org Cc: axis-dev@ws.apache.org Subject: WebSphere 5.1 does not run Web Applications running Axis SOAP Engine Hello! We are running

RE: Axis and Castor - newbie question

Hello! Some inputs on question 1) a) You can use the TCPMonitor to alter the incoming XML b) In my Axis + Castor project I do use JUnit TestCases with non-castor generated client code Cheers, Are T. Tysnes -Original Message- From: David Easley [mailto:[EMAIL PROTECTED] Sent: 1. mai

Re: List of Possible Exception Messages?

I think it needs some work to clean up all the messages and faultcodes which may be thrown in Axis http://marc.theaimsgroup.com/?l=axis-userm=111089602014070w=2 http://marc.theaimsgroup.com/?l=axis-devm=111208204315200w=2 Hopefully this is included in Axis 1.2 Final Cheers, Are T. Tysnes

Shouldn't I receive a better SoapFault ?

Hello! When I send a wrong SOAP to a WebService (Forgot to change Endpoint) I do receive this SoapFault: ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema;

Question abount faultcode Server.userException

Hello! Hopefully a simple question :o) When does Axis throw Server.userException SoapFaults !? I notice I get this when Castor throws a (De)Serializer Exception but are there other cases ? Cheers, Are T. Tysnes

RE: faultcodes in SoapFaults thrown from Axis

have no liability or obligation, legal or otherwise, for any errors, omissions, viruses or computer problems experienced as a result of this transmission since data over the public Internet cannot be guaranteed to be secure or error-free. - Original Message - From: Tysnes Are Thobias

General Exception handling in Axis (SoapFaults)

Title: Message Hello! Wonder if there existsome documentationof all the SoapFaults which may be thrown from the Axis engine !? And dows it exist some documentation on how the SoapFaults thrown from the Axis engine looks like ? Is the details field, for instance, always populated ? I

RE: Where are the Castor serializers?

Title: Message http://marc.theaimsgroup.com/?l=axis-userm=110900523929612w=2 Download the source from CVS and do a custom build Cheers, Are T. Tysnes -Original Message-From: Patrick van Kann [mailto:[EMAIL PROTECTED] Sent: 23. februar 2005 16:29To: