Hello Tomas,
Getting a DataSource is not specific to Axis Web Application but is
general to Servlet Containers. DataSources in Tomcat is documented
here :
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html
Hope this helps,
Cyrille
--
Cyrille Le Clerc
[EMAIL
Title: RE: Consuming Axis2 webservice with c# client?
xml schema type attribute is serialized with wrong namespace (should be http://www.w3.org/2001/XMLSchema-instance, is currently not namespace qualified).
to test it, you could write a quick jsp that returns the modifed response and point
Hi.
How is best way to get DataSource from ConnectionPooling in Axis server Class?
I can't find it.
I have Axis on Tomcat server.
--
Tomas Prochazka
All server code is autogenerated by Axis2 0.94 WSDL2java. Could you
perhaps give me a detailed description that I can use to log the bug.
Unfortunately, I do not really understand the differences, and what they
mean.
Do you think there amy be some other workaround, or maybe a simple way
to t
Do you have code that adds the type attribute, or are you letting axis do it ?
(if the later, then you'll need to log a bug in JIRA)
Cheers
Simon
-Original Message-
From: Justin Schoeman [mailto:[EMAIL PROTECTED]
Sent: Sat 2/18/2006 11:12 AM
To: axis-user@ws.apache.org
Cc: Simon Fell
Su
If that is the case, how do I convince the Axis server to append the
'xsi:' to the type? Is there a simple way, or do I need to hack the
generated Axis code?
Thanks,
Justin
Simon Fell wrote:
type="GenericDeviceID" should be xsi:type="GenericDeviceID"
Cheers
Simon
-Original Message---
Title: RE: Consuming Axis2 webservice with c# client?
type="GenericDeviceID" should be xsi:type="GenericDeviceID"
Cheers
Simon
-Original Message-
From: Justin Schoeman [mailto:[EMAIL PROTECTED]]
Sent: Fri 2/17/2006 8:08 AM
To: axis-user@ws.apache.org
Subject: Re: Consuming Axis2 we
No, this isn't the same problem. I suggest you ask your question on a .NET discussion list. .NET should be able to interpret the response.AnneOn 2/18/06,
Justin Schoeman <[EMAIL PROTECTED]> wrote:
How could it possibly expect an abstract type - an abstract type has noimplementation?Is this not pos
When using doc style, all content that goes in the SOAP Body must be defined as an element, but the attachments are defined as types. So you must define elements to contain your fileName and return strings. e.g., the messages should be defined like so...
An
this is exactly swa specification... MIME message or not?On 2/18/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:
I am not sure what your problem is. I found the following snippet from your WSDL file.
You use doc-lit style, yet your message have two parts. I am not sure wheth
How could it possibly expect an abstract type - an abstract type has no
implementation?
Is this not possibly the interop problem that was mentioned before (I am
sure I read about it on the list, but can not find it again), where .net
clients had problems understanding a type attribute when the
I am not sure what your problem is. I found the following snippet from your WSDL file.
You use doc-lit style, yet your message have two parts. I am not sure whether this will cause problem. But anyway, this is not a good practice to have more than one part in a message.
12 matches
Mail list logo
