Hi,
I'm looking for an Win64 (Windows xp Pro64) version of the axis_client.lib .
Sadly, I'm not able to bild my own file. I get a lot of compiling
errors while ant is running (step Running the ANT build - ant
without parameters,
http://ws.apache.org/axis/cpp/antbuild-guide.html), e.g.:
To unsubscribe, you need to send a mail to axis-user-unsubscr...@ws.apache.org.
Andreas
On Tue, Jul 14, 2009 at 07:26, Agila
Govindarajuagila.govindar...@oracle.com wrote:
Is there a way to accomplish the same without using the axis2 ? Since my
Web Service client library was created using the org.apache.axis API.
Best rebgards,
---
Miha Vitorovic
Inženir v tehničnem področju
Customer Support Engineer
NIL Data Communications, Tivolska cesta 48, 1000
I'm not familiar with Axis, but it should have something similar,
except that it uses DOM instead of Axiom (OMElement is an Axiom
interface).
Andreas
2009/7/14 Miha Vitorovic mvitoro...@nil.si:
Is there a way to accomplish the same without using the axis2 ? Since my Web
Service client library
Hi all,
I am trying to deploy sample-mtom.aar file. This file has been created by
running 'ANT' for 'build.xml' available in 'samples\mtom' directory in
axis2-1.4.1 home directory.
My problem is that when I deploy this .aar file in 'services' directory of
tomcat 5.5.27 server on local
same question here
Joel Grandin schreef:
Does anyone have any suggestions or best practices for the deployment
of multiple version of the same service name in axis 2.
Thanks.
I send xml string as a param no problem.
Is the parameter type String?
Seem schreef:
Is it possilbe to put an XML string with tags as an parameter? When i invoke
my service, I allways get errors because of the tags. when I replace them
with the gt; and lt; code, then everything works fine. But
Getting a header like this.
If im not mistaking, there is a
javax.servlet.http.HttpServletResponse.setHeader(sometype foo) too.
import org.apache.axis2.context.MessageContext;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
Well, my service parameter are like this:
xsd:element name=queryOntology
xsd:complexType
xsd:sequence
xsd:element name=sparqlQuery type=xsd:string/
/xsd:sequence
/xsd:complexType
/xsd:element
wsdl:operation name=queryContext
soap:operation
If you don't want to escape the tags then you need to change the type
to xsd:any. If it is xsd:string then the content must be a string -
and that means escaping any XML tags.
Paul
On Tue, Jul 14, 2009 at 11:11 AM, Seemsim...@gmx.de wrote:
Well, my service parameter are like this:
Hi all,
Is there any solution for the .aar (MTOM web service) deployment error?
Waiting for the response,
Thanks regards,
Vaibhav Kr. Arya
_
From: Vaibhav Arya [mailto:vaibhav.a...@otssolutions.com]
Sent: Tuesday, July 14, 2009 13:58
To: axis-user@ws.apache.org
Subject:
Hi,
I downloaded the lates axis2 (1.5 .war) and edited my Eclipse settings to
use this but the error remains? Is there anyting else I can try?
Thanks,
Tori
On Mon, Jul 13, 2009 at 11:03 PM, Deepal Jayasinghe deep...@gmail.comwrote:
I fixed this issue recently, if you can please check with
From: William Shatner [mailto:shatner.will...@gmail.com]
Sent: Monday, July 13, 2009 6:00 PM
To: axis-user@ws.apache.org
Subject: UnsupportedOperationException - changing non void method to
void
Hi all...
I've returned to this project and I still have the
Hi,
We'd like to provide several web services with a number of methods.
When calling one of the web service methods with a test client we always
get the following error in the response no matter which service or
method we are calling. For example for the login()-method:
The ServiceClass
Yes, you are using the wrong message receiver. Use RPCMessageReceiver.
Thanks,
Deepal
On Tue, Jul 14, 2009 at 9:44 AM, Nora Serineknseri...@berlin-sws.de wrote:
Hi,
We'd like to provide several web services with a number of methods. When
calling one of the web service methods with a test
Hi everybody,
I got work around for this problem.
The root cause was that when I deployed my MTOM web service on
remote server, It shows java.lang.UnsupportedClassVersionError:
Because code was compiled on newer version of java (1.6) but deployed on
tomcat 5.5.27 which is
Yep, that's working. Thanks a lot!
Am Dienstag, den 14.07.2009, 09:50 -0400 schrieb Deepal Jayasinghe:
Yes, you are using the wrong message receiver. Use RPCMessageReceiver.
Thanks,
Deepal
On Tue, Jul 14, 2009 at 9:44 AM, Nora Serineknseri...@berlin-sws.de wrote:
Hi,
We'd like
Hi Sameera.
Sorry for such a long pause. My problem was actually that I have had an old
java. It is OK now when I installed 1.6.
Thanks
Vadim.
From: Sameera Jayasoma [mailto:sameera.madus...@gmail.com]
Sent: Saturday, June 27, 2009 10:56 PM
To:
-Original Message-
From: KARR, DAVID (ATTCINW)
Sent: Monday, July 13, 2009 3:51 PM
To: axis-user@ws.apache.org
Subject: Axis skips generating type if it thinks it can just make an
array
I'm using Axis 1.3. I have a schema with a complexType which has a
single sequence of one
Hello,
I have a problem while developing a web service client in Eclipse, using
axis1.
As long as I rely only on the generated code (from the New Web Service
Client) I can happily use the service from my client app, but as soon
as I
set the endpoint URL manually I get the following
Hello,
I have implemented a web service and deployed it on Apache Axis2 1.4
One of the XML elements (Payload element) declared as XML type 'String' may
include text containing CRLF (carriage-return, linefeed) character sequence.
The problem is that CRLF character sequence is normalized by Axis
And one more pt -
If most likely we need to have entities in the WSDL file namespace
qualified, and the
WSDL parsers on the client side complain if they are not (as in the case
of wsdl:types
vs. types) then is this an exceptional case that should not occur? Why
would Axis
generate WSDL tags
In case it helps the case here is the exception I get on the client side -
[java] WSDLException (at /wsdl:definitions/types):
faultCode=INVALID_WSDL: Encountered illegal
extension element 'types' in the context of a 'javax.wsdl.Definition'.
Extension elements must be in a namespace
other
Ich werde ab 15.07.2009 nicht im Büro sein. Ich kehre zurück am
20.07.2009.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. In dringenden
Fällen wenden Sie sich bitte an: w...@westlb.de
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten
24 matches
Mail list logo