RE: SOAP:Header question
Title: Message I don't know if I should laugh or cry.. but yes.. it looks like this works without warnings.. Thanks alot Anne! :o) Cheers, Are T. Tysnes -Original Message-From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 26. oktober 2005 15:04To: axis-user@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 :o) When I describe headers like you suggests, wsdl.exe in .NET gives me the warning I mentioned (R2210) And if I have several operations (example below) declared in the WSDL both wsdl.exe in .NET and SoapScope Analyzer gives me this warning: "Duplicate Wire Signature Wsdl:Operation myOperation1 with wsdl:part MyHeader has same wire signature as wsdl:operation myOperation2 with wsdl:part MyHeader. W013" The code generated in .NET and Axis looks ok, but I don't like the warnings.. ;o) Cheers, Are T. Tysnes http://schemas.xmlsoap.org/soap/http"/> -Original Message-From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] Sent: 25. oktober 2005 21:43To: axis-user@ws.apache.orgSubject: Re: SOAP:Header questionDid you specify a parts attribute in the description?Here's an example of how your should describe headers: ... transport=" http://schemas.xmlsoap.org/soap/http"/> part="subscribeheader" use="literal"/> Anne On 10/25/05, Tysnes Are Thobias <[EMAIL PROTECTED]> wrote: Hello!I have som issues with SOAP:Header.The solution with multiple parts in a message raise a warningin .NET:"Warning: This web reference does not conform to WS-I Basic Profilev1.1 .R2210: If a document-literal binding in a DESCRIPTION does not specifythe parts attribute on a soapbind:body element, the correspondingabstract wsdl:message MUST define zero or one wsdl:parts. - Operation 'SLSCreateCase' on binding 'SLSCreateCaseSOAPBinding' from namespace 'http://www.edb.com/sls/webservices/createcase/wsdl'." When i split the parts in two messages: element="myheader:AutHeader"/>element="s0:QuerySomething"/>everything is fine in .NET, but AXIS 1.3 (WSDL2Java) refuses to generatethis header for me.Any reason for this !?Cheers;Are T. Tysnes-Original Message-From: Hans Planting (CWEU-USERS/CWNL)[mailto:[EMAIL PROTECTED]]Sent: 20. oktober 2005 17:15 To: axis-user@ws.apache.orgSubject: Re: SOAP:Header questionIt should look like: **... ...soapAction="http://xxx/webservices/GetFinancialDetail " style="document"/> use="literal" /> ... When running wsdl2java you should get something like'getFinancialData(String clientid, Authorization auth)' as thewebservices endpoint method. The clientid will be sent in the soap:body,the auth in the soap:header of the envelope. The Axis java source distribution contains a good example of this in[axishome]/test/wsdl/headerHans>You got the idea: have the endpoint method (getFinancialData) handle>this data - and obviously, it requires extra parameters to do that. The >question is how to transfer this authentication data from the header to>this parameter. Or do I misunderstand?>>Just for clearence:>I got a WSDL from which I created the JAVA sources using WSDL2Java >--server-side, that gave me (amongst others) OrgWebservice.java and>OrgWebServiceImpl.java. The last one is the one that implements the>actual services, amongst the GetFinancialDetails (java.lang.String >clientid). Is that what you call the "endpoint method"?>>Obviously, that one nedds to get the authentication data, and I don't>care if that would be in the form of an object: Object class >Authentication> java.lang.String region ;> ja
RE: SOAP:Header question
Title: Message Hello Anne! Thanks for your reply :o) When I describe headers like you suggests, wsdl.exe in .NET gives me the warning I mentioned (R2210) And if I have several operations (example below) declared in the WSDL both wsdl.exe in .NET and SoapScope Analyzer gives me this warning: "Duplicate Wire Signature Wsdl:Operation myOperation1 with wsdl:part MyHeader has same wire signature as wsdl:operation myOperation2 with wsdl:part MyHeader. W013" The code generated in .NET and Axis looks ok, but I don't like the warnings.. ;o) Cheers, Are T. Tysnes -Original Message-From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 25. oktober 2005 21:43To: axis-user@ws.apache.orgSubject: Re: SOAP:Header questionDid you specify a parts attribute in the description?Here's an example of how your should describe headers: ... transport=" http://schemas.xmlsoap.org/soap/http"/> part="subscribeheader" use="literal"/> Anne On 10/25/05, Tysnes Are Thobias <[EMAIL PROTECTED]> wrote: Hello!I have som issues with SOAP:Header.The solution with multiple parts in a message raise a warningin .NET:"Warning: This web reference does not conform to WS-I Basic Profilev1.1 .R2210: If a document-literal binding in a DESCRIPTION does not specifythe parts attribute on a soapbind:body element, the correspondingabstract wsdl:message MUST define zero or one wsdl:parts. - Operation 'SLSCreateCase' on binding 'SLSCreateCaseSOAPBinding' from namespace 'http://www.edb.com/sls/webservices/createcase/wsdl'."When i split the parts in two messages: element="myheader:AutHeader"/>element="s0:QuerySomething"/>everything is fine in .NET, but AXIS 1.3 (WSDL2Java) refuses to generatethis header for me.Any reason for this !?Cheers;Are T. Tysnes-Original Message-From: Hans Planting (CWEU-USERS/CWNL)[mailto:[EMAIL PROTECTED]]Sent: 20. oktober 2005 17:15 To: axis-user@ws.apache.orgSubject: Re: SOAP:Header questionIt should look like: **... ...soapAction="http://xxx/webservices/GetFinancialDetail " style="document"/> use="literal" /> ... When running wsdl2java you should get something like'getFinancialData(String clientid, Authorization auth)' as thewebservices endpoint method. The clientid will be sent in the soap:body,the auth in the soap:header of the envelope. The Axis java source distribution contains a good example of this in[axishome]/test/wsdl/headerHans>You got the idea: have the endpoint method (getFinancialData) handle>this data - and obviously, it requires extra parameters to do that. The >question is how to transfer this authentication data from the header to>this parameter. Or do I misunderstand?>>Just for clearence:>I got a WSDL from which I created the JAVA sources using WSDL2Java >--server-side, that gave me (amongst others) OrgWebservice.java and>OrgWebServiceImpl.java. The last one is the one that implements the>actual services, amongst the GetFinancialDetails (java.lang.String >clientid). Is that what you call the "endpoint method"?>>Obviously, that one nedds to get the authentication data, and I don't>care if that would be in the form of an object: Object class >Authentication> java.lang.String region ;> java.lang.String department ;> java.lang.String desk ;> java.lang.String username ;>>or whatever, or as separate arguments. Lets assume the first. >>So the service - now generated as:>>FinDetails class getFinancialDetails (java.lang.String clientid)>>would need to be:>>FinDetails class getFinancialDetails (java.lang.String clientid,>Authetication authentication)>>so I could use the data - directly or by a getter.>>Would this be the idea of WSDL:>...> > >> > > >type="s:string" />> >type="s:string" />> >type="s:string" />> >type="s:string" />>> > > > ...> > > >...>> soapAction="http://xxx/webservices/GetFinancialDetail ">style="document" /
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 soapbind:body element, the corresponding
abstract wsdl:message MUST define zero or one wsdl:parts.
- Operation 'SLSCreateCase' on binding 'SLSCreateCaseSOAPBinding'
from namespace 'http://www.edb.com/sls/webservices/
createcase/wsdl'."
When i split the parts in two messages:
everything is fine in .NET, but AXIS 1.3 (WSDL2Java) refuses to generate
this header for me.
Any reason for this !?
Cheers;
Are T. Tysnes
-Original Message-
From: Hans Planting (CWEU-USERS/CWNL)
[mailto:[EMAIL PROTECTED]
Sent: 20. oktober 2005 17:15
To: axis-user@ws.apache.org
Subject: Re: SOAP:Header question
It should look like:
**
...
...
http://xxx/webservices/GetFinancialDetail"; style="document"
/>
...
When running wsdl2java you should get something like
'getFinancialData(String clientid, Authorization auth)' as the
webservices endpoint method. The clientid will be sent in the soap:body,
the auth in the soap:header of the envelope. The Axis java source
distribution contains a good example of this in
[axishome]/test/wsdl/header
Hans
>You got the idea: have the endpoint method (getFinancialData) handle
>this data - and obviously, it requires extra parameters to do that. The
>question is how to transfer this authentication data from the header to
>this parameter. Or do I misunderstand?
>
>Just for clearence:
>I got a WSDL from which I created the JAVA sources using WSDL2Java
>--server-side, that gave me (amongst others) OrgWebservice.java and
>OrgWebServiceImpl.java. The last one is the one that implements the
>actual services, amongst the GetFinancialDetails (java.lang.String
>clientid). Is that what you call the "endpoint method"?
>
>Obviously, that one nedds to get the authentication data, and I don't
>care if that would be in the form of an object: Object class
>Authentication
> java.lang.String region ;
> java.lang.String department ;
> java.lang.String desk ;
> java.lang.String username ;
>
>or whatever, or as separate arguments. Lets assume the first.
>
>So the service - now generated as:
>
>FinDetails class getFinancialDetails (java.lang.String clientid)
>
>would need to be:
>
>FinDetails class getFinancialDetails (java.lang.String clientid,
>Authetication authentication)
>
>so I could use the data - directly or by a getter.
>
>Would this be the idea of WSDL:
>...
>
>
>
>
>
> type="s:string" />
> type="s:string" />
> type="s:string" />
> type="s:string" />
>
>
>
>
> ...
>
>
>
>...
>
> http://xxx/webservices/GetFinancialDetail";
>style="document" />
>
>
>part="Authorization" use="literal" />
>
>
>
>
>
>...
>
>This is in the WSDL already, but the header data is not included in the
>generated JAVA code:
>
>public interface OrgWebServiceSoap extends java.rmi.Remote { ...
>public xxx.FinDetails getFinancialDetail(java.lang.String clientid)
;
>...
>}
>
>and I don't find any refererence to the haeder data either when
>searching all java files.
>
>So HOW to change the WSDL to get this information included in the
>interface? Or should I just add it and create a WSDL from the java
>code? Quite a nasty job since so much needs to be coded. By that: the
>nasty part, at the moment, is that the WSDL is _delivered_ to me -
>there is already a webservice (on another platform) that works with it.
>The good side is that we're in the stage of preparing a new version so
>changes can be incoprorated. If only I had some idea.
>
>Willem
>
>PS. Original names in code adapted for display, because of policy.
>
>-Oorspronkelijk bericht-
>Van: Hans Planting (CWEU-USERS/CWNL)
>[mailto:[EMAIL PROTECTED]
>Verzonden: donderdag 20 oktober 2005 11:29
>Aan: axis-user@ws.apache.org
>Onderwerp: Re: SOAP:Header question
>
>
>Hi Willem,
>
>It sounds to me that you need to use explicit service context: the
>signature of the webservices endpoint method is extended with the parts
>of the soap:header.
>This way the getFinancialDetails method will have an additional
>parameter for the authentication data - however the authentication data
>in the soap envelope is transported in the header. So you don't create
a
>separate handler to deal with the header but instead deal with it in
the
>endpoint method. Make sure that in the wsdl the soapheader element
>refers to a part in the request message.
>
>Regards,
>Hans
>
>
>
>>Hi,
>>Some help is rquired with the following pr
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 program to generate a stub to access webservices. Therefore i only manipulate java object. How can i see xml exange between client and server ? Because i have to see if they are well formed. Thanks
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
Custom (De)Serializer - NoSuchMethodException (Debug information)
Hello! Found this in my JBoss server log: (We are using Castor as (De)Serializer) 2005-05-13 12:33:26,168 DEBUG [org.apache.axis.encoding.ser.BaseSerializerFactory] Exception: java.lang.NoSuchMethodException: org.apache.axis.encoding.ser.castor.CastorSerializerFactory.create(java. lang.Class, javax.xml.namespace.QName) at java.lang.Class.getMethod0(Class.java:1756) at java.lang.Class.getMethod(Class.java:963) at org.apache.axis.encoding.ser.BaseSerializerFactory.createFactory(BaseSer ializerFactory.java:234) ... ... This is Debug information.. I guess it's nothing to worry about !? Cheers, Are T. Tysnes
RE: WebSphere 5.1 does not run Web Applications running Axis SOAPEngine
Thanks for your reply! I will take a look at your suggestions. What's bothering me is that IBM clearly doesn not support Web Applications running Axis SOAP Engine running in WebSphere. I don't know if my company will take the risk to run an unsupported application. Maybe it's time to migrate to JBoss in production.. :o) Cheers, Are T. Tysnes -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 4. mai 2005 10:26 To: axis-user@ws.apache.org Subject: RE: WebSphere 5.1 does not run Web Applications running Axis SOAPEngine I am successfully running a web application on WAS 5.1 using Axis 1.1. I have had some problems with Axis1.2RC3 and WAS 5.1 but I got over those by using Shared libraries to contain all the Axis jars and PARENT_LAST as the classloader policy. I also had to specify a name-value pair assigning the fully-qualified class name of the LogFactory implementation to property org.apache.commons.logging.LogFactory in file commons-logging.properties, and place this file in the classpath to force WAS to use the Apache implementation of LogFactory instead of the IBM one - see http://www-1.ibm.com/support/docview.wss?uid=swg27004610 (but this could be just for WAS on the iSeries). I added the commons-logging.properties file to a config directory which was in a shared library associated with the application and Axis was happy and the web service worked. I also called IBM support for help but in the end I ended up 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 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. I did contact IBM support and they can tell me that it is not possible to run Web Applications containg Axis on WebSphere 5.1. Can anyone confirm this !? Do we realy have to change our Application Server because we decided to use Axis as SOAP Engine !? Cheers, Are T. Tysnes __ This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.
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. I did contact IBM support and they can tell me that it is not possible to run Web Applications containg Axis on WebSphere 5.1. Can anyone confirm this !? Do we realy have to change our Application Server because we decided to use Axis as SOAP Engine !? Cheers, Are T. Tysnes
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 2005 19:00 To: axis-user@ws.apache.org Subject: Axis and Castor - newbie question I've been experimenting using Axis and Castor along the lines described in the IBM article: http://www-106.ibm.com/developerworks/webservices/library/ws-castor/ Everything's working fine, but I have a few questions: 1. I want to test that the WS messages are being validated against my schema (after all, this is one of the main reasons I'm using Castor rather than plain old WSDL2Java). My test set-up involves using the Castor generated code on the client and server side, so it's impossible to generate invalid XML! What's the simplest way to test this? 2. On the server side, I already have a set of DTOs that I must use internal to the app. So I'm currently having to translate between the Castor generated objects and my own DTOs, which is a pain. Ideally, I'd like Castor to unmarshall/marshall directly to/from my DTOs. I've read the provided Castor XML Mapping documentation but I can't see how to integrate my Castor XML mapping file into my Axis+Castor solution. Can this be done? 3. If the answer to 2. is yes, can the incoming WS request messages and the outgoing WS response messages still be validated against my schema? If the answer to 2 & 3 is yes, yipp! Thanks for any help, David
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: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> soapenv:Server.userException org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize. http://xml.apache.org/axis/";>localhost Shouldn't I receive a better Error message !? I can't find any stacktrace in my logs either.. I'm using Castor to (De)Serialize but it looks like this is Exception is thrown from the Axis Deserializer !? Cheers, Are T. Tysnes
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-user&m=111089602014070&w=2 http://marc.theaimsgroup.com/?l=axis-dev&m=111208204315200&w=2 Hopefully this is included in Axis 1.2 Final Cheers, Are T. Tysnes -Original Message- From: Toshiyuki Kimura [mailto:[EMAIL PROTECTED] Sent: 6. april 2005 08:37 To: axis-user@ws.apache.org Subject: Re: List of Possible Exception Messages? How about 'grep -r "throw new" *' for the original question ? Thanks, Toshi <[EMAIL PROTECTED]> On Wed, 6 Apr 2005, Peter Smith wrote: > >> how about the messages in >> ws-axis\java\build\classes\org\apache\axis\i18n\resource.properties? >> > But from what I've remember of that file, the messages were a random > mixture of the following categories: > a) exception messages > b) logging/tracing output > c) gui/console output > d) redundant message that is not used anywhere in Axis code > > Furthermore, the key names seemed to be any old unique string which > don't > necesarily indicate which category they belong to. > > Peter. >
RE: faultcodes in SoapFaults thrown from Axis
Hello!
Looks like the SOAPService handler throws the "Server" faultcode if a
RuntimeException
is thrown.
Should preferably also be located in Constants.java
Anyone knows any other "hidden" faultcodes ? :o)
What about these !?
JavaProvider.java
line 116 - throw new AxisFault("NoSuchObject", null, null,
null);
line 276 - throw new AxisFault("Server.NoClassForService",
Messages.getMessage("noOption00",
getServiceClassNameOptionName(), serviceName),
null, null);
AxisServer.java
line 141 - throw new AxisFault("Server.disabled",
Messages.getMessage("serverDisabled00"), null, null);
line 269 - throw new AxisFault("Server.NoService",
Messages.getMessage("noService05",
"" + msgContext.getTargetService()), null, null );
line 349 - throw new AxisFault("Server.disabled",
Messages.getMessage("serverDisabled00"), null, null);
+
(just search for 'new AxisFault("' in the src folder)
My current list is:
- Client
- Server
- Server.generalException
- Server.userException
- VersionMismatch
- MustUnserstand
- Server.NoService
Dims !?
Cheers,
Are T. Tysnes
-Original Message-
From: Sunil Kothari [mailto:[EMAIL PROTECTED]
Sent: 15. mars 2005 14:48
To: axis-user@ws.apache.org
Subject: Re: faultcodes in SoapFaults thrown from Axis
Yes..Those are the general categories of errors. I have seen it
well documented somewhere but don't no where exactly.
Sunil Kothari
DISCLAIMER:
Any Information contained or transmitted in this e-mail and / or
attachments may contain confidential data, proprietary to Majoris
Systems Pvt Ltd., and / or the authors of the information and is
intended for use only by the individual or entity to which it is
addressed. If you are not the intended recipient or email appears
to have been sent to you by error, you are not authorised to access,
read, disclose, copy, use or otherwise deal with it. If you
have received this e-mail in error, please notify us immediately at
mail to: [EMAIL PROTECTED] and delete this mail from your records.
This is to notify that Majoris Systems Pvt Limited shall 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" <[EMAIL PROTECTED]>
Date: Tuesday, March 15, 2005 6:36 pm
Subject: faultcodes in SoapFaults thrown from Axis
>
> Hello!
>
> It looks to me that Axis throws SoapFaults with the following
> faultcodes:
>
> - Client
> - Server.generalException
> - Server.userException
> - VersionMismatch
> - MustUnserstand
> - Server.NoService
>
> Wonder if someone could confirm this :o)
>
> Cheers,
> Are T. Tysnes
>
RE: faultcodes in SoapFaults thrown from Axis
Thanks for the information Anne :o) "Alternatively, it is acceptable to define custom fault codes in a namespace controlled by the specifying authority" Means this is an acceptable custom faultcode !? http://www.mycompany.com/webservices/ns/";>ns1:CustomFaultcode Cheers, Are T. Tysnes -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: 15. mars 2005 15:13 To: axis-user@ws.apache.org; [EMAIL PROTECTED] Subject: Re: faultcodes in SoapFaults thrown from Axis I've raised this issue on more than one occasion. The use of the "dot" notation in fault error codes is discouraged by the WS-I BP: 3.3.6 SOAP Custom Fault Codes SOAP 1.1 allows custom fault codes to appear inside the faultcode element, through the use of the "dot" notation. Use of this mechanism to extend the meaning of the SOAP 1.1-defined fault codes can lead to namespace collision. Therefore, its use should be avoided, as doing so may cause interoperability issues when the same names are used in the right-hand side of the "." (dot) to convey different meaning. Instead, the Profile encourages the use of the fault codes defined in SOAP 1.1, along with additional information in the detail element to convey the nature of the fault. Alternatively, it is acceptable to define custom fault codes in a namespace controlled by the specifying authority. A number of specifications have already defined custom fault codes using the "." (dot) notation. Despite this, their use in future specifications is discouraged. R1004 When an ENVELOPE contains a faultcode element, the content of that element SHOULD be either one of the fault codes defined in SOAP 1.1 (supplying additional information if necessary in the detail element), or a Qname whose namespace is controlled by the fault's specifying authority (in that order of preference). R1031 When an ENVELOPE contains a faultcode element the content of that element SHOULD NOT use of the SOAP 1.1 "dot" notation to refine the meaning of the fault. It is recommended that applications that require custom fault codes either use the SOAP1.1 defined fault codes and supply additional information in the detail element, or that they define these codes in a namespace that is controlled by the specifying authority. Also note that the whole concept of Server.userException makes absolutely no sense. If the fault is caused by a user exception, then the proper fault code is Client, not Server. Per the SOAP 1.1 specification: Client The Client class of errors indicate that the message was incorrectly formed or did not contain the appropriate information in order to succeed. For example, the message could lack the proper authentication or payment information. It is generally an indication that the message should not be resent without change. See also section 4.4 for a description of the SOAP Fault detail sub-element. Server The Server class of errors indicate that the message could not be processed for reasons not directly attributable to the contents of the message itself but rather to the processing of the message. For example, processing could include communicating with an upstream processor, which didn't respond. The message may succeed at a later point in time. See also section 4.4 for a description of the SOAP Fault detail sub-element. On Tue, 15 Mar 2005 14:06:36 +0100, Tysnes Are Thobias <[EMAIL PROTECTED]> wrote: > > Hello! > > It looks to me that Axis throws SoapFaults with the following > faultcodes: > > - Client > - Server.generalException > - Server.userException > - VersionMismatch > - MustUnserstand > - Server.NoService > > Wonder if someone could confirm this :o) > > Cheers, > Are T. Tysnes >
RE: faultcodes in SoapFaults thrown from Axis
Thanks! The only "documentation" I found was in this java file .. :-/ http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/Const ants.java?rev=1.137&view=markup Cheers, Are T. Tysnes -Original Message- From: Sunil Kothari [mailto:[EMAIL PROTECTED] Sent: 15. mars 2005 14:48 To: axis-user@ws.apache.org Subject: Re: faultcodes in SoapFaults thrown from Axis Yes..Those are the general categories of errors. I have seen it well documented somewhere but don't no where exactly. Sunil Kothari DISCLAIMER: Any Information contained or transmitted in this e-mail and / or attachments may contain confidential data, proprietary to Majoris Systems Pvt Ltd., and / or the authors of the information and is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or email appears to have been sent to you by error, you are not authorised to access, read, disclose, copy, use or otherwise deal with it. If you have received this e-mail in error, please notify us immediately at mail to: [EMAIL PROTECTED] and delete this mail from your records. This is to notify that Majoris Systems Pvt Limited shall 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" <[EMAIL PROTECTED]> Date: Tuesday, March 15, 2005 6:36 pm Subject: faultcodes in SoapFaults thrown from Axis > > Hello! > > It looks to me that Axis throws SoapFaults with the following > faultcodes: > > - Client > - Server.generalException > - Server.userException > - VersionMismatch > - MustUnserstand > - Server.NoService > > Wonder if someone could confirm this :o) > > Cheers, > Are T. Tysnes >
faultcodes in SoapFaults thrown from Axis
Hello! It looks to me that Axis throws SoapFaults with the following faultcodes: - Client - Server.generalException - Server.userException - VersionMismatch - MustUnserstand - Server.NoService Wonder if someone could confirm this :o) Cheers, Are T. Tysnes
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
General Exception handling in Axis (SoapFaults)
Title: Message Hello! Wonder if there exist some documentation of 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 guess most of them looks like this (unvalid targetservice name): http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> ns1:Server.NoServicehttp://xml.apache.org/axis/">ns1:Server.NoService> The AXIS engine could not find a target service to invoke! targetService is TestService2 localhosthttp://xml.apache.org/axis/">localhost> Cheers, Are T. Tysnes
RE: Where are the Castor serializers?
Title: Message http://marc.theaimsgroup.com/?l=axis-user&m=110900523929612&w=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: axis-user@ws.apache.orgSubject: Where are the Castor serializers? There are Castor related classes for serialization described in the API docs and in the CVShttp://ws.apache.org/axis/java/apiDocs/org/apache/axis/encoding/ser/castor/package-summary.htmlhttp://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/encoding/ser/castor/However, these don't seem to be in 1.2 RC2.Do I need to download a source version or build from CVS?Thanks in advance for any guidance.Patrick
RE: getting rid of debug messages in logfile
Hello! Not shure if this help but I had a similar "problem" in JBoss. server.log spooled giggs of debug information when running Axis. I had to enter the following in jboss log4j.xml (jboss-3.2.3\server\default\conf) Cheers, Are T. Tysnes -Original Message- From: James Black [mailto:[EMAIL PROTECTED] Sent: 21. februar 2005 14:39 To: axis-user@ws.apache.org Subject: re: getting rid of debug messages in logfile -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In catalina.out I am getting an enormous number of debug information. How do I go about removing this? In server.xml I don't have anything higher than debug="0" anywhere in the file. Thanx for any help. I am using Axis1.2RC2. - -- "Love is mutual self-giving that ends in self-recovery." Fulton Sheen James Black[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCGeSKikQgpVn8xrARAtF9AJ9P+Vw4l/PQBkWPluOx1LtrbBjtgQCeMk9f jERVfQD+qkULq9CGFY+PGvw= =O2o/ -END PGP SIGNATURE-
RE: Need info on (De)Serializers
Hello, Castor is "custom" (De)Serializers in Axis. Check your (De)Serializer code agains what the Castor peoples has done. You can also read this tutorial on how to use Castor (De)Serializers in Axis: http://www-106.ibm.com/developerworks/webservices/library/ws-castor/ I don't know how you'r classes are loaded in your classloader but I guess just writing the class name is not sufficient. You need the package name too. I.e: serializer="org.apache.axis.encoding.ser.castor.CastorSerializerFactory" deserializer="org.apache.axis.encoding.ser.castor.CastorDeserializerFact ory" Cheers, Are T. Tysnes -Original Message- From: babloosony [mailto:[EMAIL PROTECTED] Sent: 21. februar 2005 12:58 To: axis-user@ws.apache.org Subject: Re: Need info on (De)Serializers Hi Are T. Tysnes, I am implementing my own Axis (De)Serializers. Is my server-config.wsdd file correct. How do I debug axis logs, apis at which point my (De)Serializers are not getting loaded/initialized ? Thanks & Regards, Kumar. On Mon, 21 Feb 2005 12:49:16 +0100, Tysnes Are Thobias <[EMAIL PROTECTED]> wrote: > > Take a look at the Castor (De)Serializers > > http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/enc > od > ing/ser/castor/ > > Cheers, > Are T. Tysnes > > -Original Message- > From: babloosony [mailto:[EMAIL PROTECTED] > Sent: 21. februar 2005 12:44 > To: axis-user@ws.apache.org > Subject: Need info on (De)Serializers > > Hi All, > > Is anybody successful in implementing you own Apache Axis > (De)Serializers. If so can you please share your experiences like > issues you have faced, docs, tutorials, links you have used etc. etc. > > Basically no matter what I do, how I tweak my server-config.wsdd my > custom Axis (De)Serializers are not getting loaded/initialized. > > server-config.wsdd > -- > -- > --- > > name="className" value="SparePartService"/> xmlns:ns="apress" >qname="ns:SparePartBean" >type="java:SparePartBean" >serializer="WroxAxisSerializerFactory" >deserializer="WroxAxisDeserializerFactory" >encodingStyle="" >/> > > > --- > > Thanks & Regards, > Kumar. >
RE: Need info on (De)Serializers
Take a look at the Castor (De)Serializers http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/encod ing/ser/castor/ Cheers, Are T. Tysnes -Original Message- From: babloosony [mailto:[EMAIL PROTECTED] Sent: 21. februar 2005 12:44 To: axis-user@ws.apache.org Subject: Need info on (De)Serializers Hi All, Is anybody successful in implementing you own Apache Axis (De)Serializers. If so can you please share your experiences like issues you have faced, docs, tutorials, links you have used etc. etc. Basically no matter what I do, how I tweak my server-config.wsdd my custom Axis (De)Serializers are not getting loaded/initialized. server-config.wsdd --- --- Thanks & Regards, Kumar.
