AW: Handler question

Use a JAXRPCHandler and return false if you want to stop processing. -Ursprüngliche Nachricht- Von: Mark D. Hansen [mailto:[EMAIL PROTECTED] Gesendet: Montag, 8. Dezember 2003 23:43 An: AXIS Users (E-mail) Betreff: Handler question I need to write a handler (server side) that,

AW: Deploying Providers - one issue

.. -Original Message-From: Thomas Bayer [mailto:[EMAIL PROTECTED]Sent: Wednesday, November 12, 2003 9:43 PMTo: [EMAIL PROTECTED]Subject: AW: Deploying Providers ?Hi,Axis supports also plugable Providers. New Providers could be used with aservice without changing the Axis source

AW: WSDD and explicit headers

Hi, Axis can handle in and out parameters as header elements. The service method is implemented as usual but the parameters are passed in the header. Try: service xmlns:ns=... ... operation name=mymethod parameter qname=ns:param1 inHeader=true/ parameter qname=ns:param2

AW: Deploying Providers ?

Hi, Axis supports also plugable Providers. New Providers could be used with a service without changing the Axis source code. service name=MyService provider=java:ECHO parameter name=param1 value=hossa/ /service Below is a step by step example. In the Provider the service's parameters can be

AW: Services sharing same session

Hi Magnus, a more SOAP conform way is the usage of SOAP headers containing a session id. A custom handler could help to implement it transparent for the client and server. Thomas -Ursprüngliche Nachricht- Von: Magnus Sandberg [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 6.

AW: WSDD question - parameters that control WSDL generation ??

Hallo Mark, yes these parameters control the WSDL generation using the WSDL Querystring. I don't know where documentation can be found. Perhaps that helps: wsdlPortType = name for the port type wsdlServiceElement = name for service element wsdlServicePort = name for the port wsdlTargetNamespace

AW: How do I avoid sending the XSI type

Hi Tommy, try call.setProperty(org.apache.axis.client.Call.SEND_TYPE_ATTR, Boolean.FALSE); at the client side and set in the globalConfiguration at the server side the parameter sendXsiTypes to false. parameter name=sendXsiTypes value=false/ I hope it works with headers too. Thomas

Deploying python WS

Hi, has anybody a working configuration (wsdd) or an example for a WS implementation in Python/Jython or Ruby? I've compiled axis 1.1 with BSF 2.3.0 and managed to access the Jython, but there are still faults. The generation of WSDL with ?WSDL doesn't work either. Is the BSFProvider capable of

AW: Passing parameters to constructor

Hi Massimo, Axis is responsible for the creation of MyClass objects. So Axis creates an instance of the service implementation using the newInstance() method of class Class. Axis expects a default constructor. Normally the Java compiler generates a default constructor, but if you write your own

AW: SOAP Specification regarding literal payload documents

Hi Nicholas, could you post the correspondending WSDL or the client code? Thomas -Ursprüngliche Nachricht- Von: Nicholas Ardlie [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 29. August 2003 03:23 An: axis-user (E-mail) Betreff: SOAP Specification regarding literal payload documents

AW: Passing parameters to constructor

Hi Massimo, the default constructor without any parameters is needed to automatically instanciate an object of the service class. If you want to initialize your service use the JAX-RPC ServiceLifecycle Interface. public class MyService implements ServiceLifecycle { public void init(Object

AW: DOM as parameters using Document style

Hi Joel, you can use the MSGProvider and a signature like public Document process(Document doc) but the MSGProvider only delivers WSDL schema definitions with anyType: schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://message.javamagazin.de; element

XMLType.AXIS_VOID Returntype and document/literal

Hi, I want to call a doc/lit service with a method returning void. In the client I have to use addParameter, so JAX-RPC forces me to specify also a return type: call.setReturnType( XMLType.AXIS_VOID); This works pretty well with RPC/Encoded services. With a doc/lit I got the following

AW: Using beanMapping in WSDD

Hi Chris, only the method getInvoiceDetails is allowed in your wsdd file, but your service hasn't this method: parameter name=allowedMethods value=getInvoiceDetails / change it to: parameter name=allowedMethods value=*/ and you will see the methods. Thomas Orientation in Objects GmbH

Why specify a operationname for a doc/lit client

Hi, I'am wondering why I have to specify an operation name in a no-wrapped document/literal client. If a operationname is specified it isn't used. If no operation name is specified, the exception below is thrown? Thomas Client: call.setOperationStyle( Style.DOCUMENT); call.setOperationUse(

AW: Why specify a operationname for a doc/lit client

Hi, Axis uses the operation name to reference the WSDL description and find the input, output, and fault message definition. I thought once the client is generated, axis doesn't use WSDL for the invokation. This client is yet a static DII client. There must be an other reason. Perhaps JAX-RPC

AW: Is this a wrapped service ?

Hi Dimuthu , you can set the property SEND_TYPE_ATTR in a org.apache.axis.client.Call object to false: call.setProperty( SEND_TYPE_ATTR, "false"); If you use WSDL2Java and WSDL2Java recognizes your service as wrapped the following code is generated automatically:

AW: SOAPMonitor

look at the FAQ: http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/SoapMonitor -Ursprüngliche Nachricht- Von: Vaidya, Raghavendra (CORP, GEITC) [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 19. August 2003 12:16 An: [EMAIL PROTECTED] Betreff: SOAPMonitor Hi, I am