Service specific client side serializers

Title: Service specific client side serializers I have a number of client stubs that use Axis 1.1, I currently have some global type mappings in the client-config.wsdd. I'd like to make some of them service specific (so they can use different serializers for the same type), it not clear what

Re: Deployment problem with Axis 1.2.1/Tomcat 5.5.9/ JDK 1.5

Unfortunately that did not do the trick, still have the same error :-/ Developer Developer wrote: I got similar error, I solved it by copying all the jar files from axis/lib to tomcat shared lib ( i.e ../shared/lib). On 10/10/05, *Bolke de Bruin* <[EMAIL PROTECTED]

Re: Deployment problem with Axis 1.2.1/Tomcat 5.5.9/ JDK 1.5

  I got similar error, I solved it by copying all the jar files from   axis/lib to tomcat shared lib ( i.e ../shared/lib).     On 10/10/05, Bolke de Bruin <[EMAIL PROTECTED]> wrote: I did some further digging (thanks for the pointers), but still I amfacing the same problem. The Service class does

Re: Deployment problem with Axis 1.2.1/Tomcat 5.5.9/ JDK 1.5

I did some further digging (thanks for the pointers), but still I am facing the same problem. The Service class does get accessed (I have a static part which logs things), but still I have 2 errors (and no service). I did some searching on the net but could not find anything except that my "ty

Re: BeanSerializer on JavaBean class with protected getters/setters?

I'll answer (a part of) my own question: setters can be protected, getters must be public. -nikita Nikita Tovstoles wrote: If I take a typical JavaBean class, and modify it so that some fields' getters and setters are 'protected' and not public, will those properties still be serialized by

type mapping for org.wc3.dom.Document?

I have the following type mapping

RE: Fault - makeTypeElement()

Yeah…I followed what you had done.  I changed everything to a complex type, fixed the WSDL using the WSDL validator from eclipse, put everything in the same namespace, but now I get the following error:   AxisFault  faultCode: {http://xml.apache.org/axis/}Server.generalException  faultS

Axis via Tomcat connector to IIS, HTTPD and SOAPaction Header issues

Hello, I have Axis up and running in a Tomcat 5.5 container. I have created a test server and client and have successfully used the client directly against the Tomcat hosted service. I have also installed Apache HTTPD 2 with JK1.2 and successfully tested the client -> HTTPD -> Tomcat. Now I have

How to check the cause of non deployed service?

Hello all,   I generated a service by WSDL2Java. I changed the ServiceSoapBindingImpl.java to my procedure. When I deploy it using AdminClient I get this:   Processing file deploy.wsdd Done processing   But when I list deployed services, my service isn’t there! :-(   How can I see

serialization due to java beans

Hello, I have read the same question in the list and the reply is that: the object to be serialized has to be a java bean I have the same problem: I try to Java2WSDL and I get the result: Java2WSDL etm.axis.tmapi.TopicMapObjectAxis - The class etm.axis.tmapi.LocatorAxis does not contain a defaul

problem with WSDL2Java using a schema import with "attributeGroup"

I'm having a problem with WSDL2Java generating the wrong java code for a wsdl that defines an array of (attribute, array) touples. When I inline the schema into the wsdl file, it works fine. When I export the schema to a separate xsd file, it seems to collapse everything into an array of arrays.

[axis2 0.92] 0.92 Code generator is creating alot more artifacts than 0.91

Hi,   The version 0.92 wsdl2java generator is creating way more files than the 0.91 one.   The few wsdl:s I tried in the 0.92 resulted in archives (after generate, compile and jar) that are 10-12 times the size of the same wsdl in version 0.91.   One example: a _very_simple_ webservice went

[Axis 1.2.1] Incorrect element names of items in a list

Title: Nachricht Hi all,   I have a wrapped/literal web service whose input parameters and output values are de-/serialized via .   In my WSDL file generated by AXIS an Array of custom types in my return bean looks like this:                 So far so good...   As you see in the

AW: Accessing HTTP headers

Title: Nachricht Hi David,   try this: MessageContext context = AxisEngine.getCurrentMessageContext();   From the context object you can get the Properties of the HTTP header   Denis -Ursprüngliche Nachricht-Von: David Easley [mailto:[EMAIL PROTECTED] Gesendet: Montag, 10.

Accessing HTTP headers

I need to access some HTTP header data from incoming web service requests. I’m using doc/lit style web services using Axis and Castor. If anyone can point me in the right direction I’d be most grateful.   David