Thank you for the suggestion. I have downloaded a
recent version (November 18) but it still fails to compile under
VC7.
I tried the ANT build but it also got into a tangle.
Rather than boring everyone with the details, can I ask first whether this is
the right forum?
Also I noticed that
I have a very simple service (implemented in Java) with two methods:
String echo(String message)
and
Future getFuture()
I have tested both through a browser and they are both known to work.
I have used the binary version of Axis C++ 1.5 to generate stubs and
wrote a very simple client that
The Jira for Axis2C is here: http://issues.apache.org/jira/browse/AXIS2C
Please report bugs and improvements in this Jira.
Thanks,
Samisa...
Lilantha Darshana wrote:
I'm copying Dims here in case he has not seen this since as I remember
Dims helps us setting that up for Axis1 C++.
Thanks
Hi All,
The first milestone release of Axis2C, M0.1 has been released and could be downloaded at
http://www.apache.org/dist/ws/axis2c/
This release includes the C implementation of AXIOM, an important part of Axis2C web service stack.
Following features are included
1. OM module
2. Guththila
This is well answered in the followingthread in the dev list. An issue caused due tocross posting..
http://www.opensubscriber.com/message/axis-dev@ws.apache.org/2642402.html
~Thilina
On 11/24/05, Ajith Ranabahu [EMAIL PROTECTED]
wrote:
hi all, Well I'm not sure why nobody seems to answer
Hi,
I’m currently working on a simple web service working with Axis 1.2.1
and Tomcat 5.
This web service is working perfectly but I have a problem with long
running calls.
In fact I would like to know how I can cancel a call which is taking to
much time?
Did anybody have this problem before
Hi!
My approach would be to have a second service that is provided with some unique
parameters of the first (long running) call, that internally aborts the first
call with traditional thread communication means.
Another approach would be to decompose the long running WS into smaller
fractions
Hi,
That's seems a good idea but how can I know which thread I should abort.
I mean if I running my first web service and it is too long I want to
abort and call a second web service doing that. But how can I give the
second one an unique parameter on the first one as the first is still
Hi
I have a small problem with my ws. I'm exposing an api on a framework
I'm using and would like to know if a custom handler can get the
instance of the backend service, before the request is made, in order
to set a parameter in the service class?
Basicly I'm trying to get a param from an URL
Title: Nachricht
Hi
all,
does anyone here
have knowledge of how to add a fault to a service in a WSDD file that is
serializable by AXIS and therefore appears in the auto-generated WSDL
file?
Since now I have
tried to add this:
faultclass="my.package.MyException/
where 'MyException'
Hi,
In the simplest case you can send a unique id as an additional parameter to the
first call. If you want to abort the call you send the id to the abortion
service.
You have to register the thread servicing the first call in a central map with
the id. Then you can lookup the thread in the
Hi,
I guess you want your service to access some parameter made available by the
handler.
You don't need to get the instance of the backend service in the handler.
Besides, the service's implementation can access the instance of MessageContext
being manipulated by the request chain using
Hi,
The problem is that the service bean is in another package (both
packages are in jboss), does that work with the static method
getCurrentContext()?
And just to be sure... is there no way for the handler to call a
method in the backend service before the actual call is made?
Regards
Arnaldur
Title: Nachricht
MyExtension should extend AxisFault.
Best regards,--DI Günter
GrossbergerConsultant
Tel: +43 1 329 50 161Software AG Österreich Fax: +43 1 329 50
171Guglgasse 7-9 GSM:
+43 676 833 29 2611030
Wien
http://www.softwareag.com/austria
From: Denis Schlesinger
I haven't tried using getCurrentContext() with EJB's deployed in other
packages. It may work, because the current instance of MessageContext must stay
in scope until the full treatment of the response message is completed.
It is normally not possible for the handler to access the backend
Hi,
I was looking at the DataDeser in examples/encoding and I'm still at a
loss. If someone has written a deserializer for a map/hashmap
(especially for nested maps), could you please help?
Thanks,
Don Tam wrote:
Hi,
Thank you for the response. Do you have a complete example of how to
Hi,
i've just started to build my first app using web services and Axis.
My business interface has a simple logon method that (if successful)
returns a token. This token is to be used for subsequent method calls
(it essentially allows me to have a timed session).
The question I have is that
Hi,
Axis lets you define and deploy HANDLERS in order to customize the SOAP
processing chain. Handlers are similar in many ways to the filters used for
interception in webapps. The use case you described could be easily implemented
using handlers.
For more information on this, please refer
Hi,
I already have an old web service running JWSDP. So if I write a
deserializer for a datatype, how would I register it with my client so
that Axis knows I need to use it for said datatype? Is there a way I can
declare this in the code once I have the stub (because I have nothing to
Em Quinta 24 Novembro 2005 15:16, o Don Tam escreveu:
Hi,
I already have an old web service running JWSDP. So if I write a
deserializer for a datatype, how would I register it with my client so
that Axis knows I need to use it for said datatype? Is there a way I can
declare this in the code
If you want to cancel the call from the client side, do
call.setTimeout(mSecToWait) before making the call.
-K
--- HOFFMANN Camille [EMAIL PROTECTED] wrote:
Hi,
Im currently working on a simple web service working with Axis 1.2.1
and Tomcat 5.
This web service is working perfectly but
Title: Nachricht
Hallo,
I have a declared a
fault message type in the WSDD file as follows:
operation name="create" returnQName="resultValue"
returnType="ns:ServerLogEntry" parameter name="material"
type="ns:Material"/
fault name="RIACOMFault" qname="ns:RIACOMFault"
Title: Nachricht
Hallo,
I have a declared a
fault message type in the WSDD file as follows:
operation name="create"
returnQName="resultValue" returnType="ns:ServerLogEntry" parameter
name="material" type="ns:Material"/
fault name="MyFault" qname="ns:MyFault" type="ns:MyFaultType"
Title: Nachricht
Don't
worry, I did notthrow 'MyFault' in my web service method... sorry, my
fault ;)
-Ursprüngliche Nachricht-Von: Denis Schlesinger
Gesendet: Donnerstag, 24. November 2005 19:33An:
axis-user@ws.apache.orgBetreff: fault message type is not being
Let me answer my own posting here again.
If we support a signed applet that allows us to ask question to allow
this SOAPMonitor applet to run in browser. When user gives permission to
run the applet has access to system clip board.
That way we can cut and paste the text from soap monitor to
Title: SEC:U How do I stop WSDL2Java from unwrapping my arrays?
Hi,
I have a couple of Wrapped style services.
When defining these services in WSDL, I wrapped all the arrays I defined.
However, it appears that WSDL2Java is unwrapping these arrays. The published WSDL files (name?WSDL)
Hi All,
The first milestone release of Axis2C, M0.1 has been released and could be downloaded at
http://www.apache.org/dist/ws/axis2c/
This release includes the C implementation of AXIOM, an important part of Axis2C web service stack.
Following features are included
1. OM module
2. Guththila
27 matches
Mail list logo
