Hi Sunil,
I had a look at that posting, but I think this is not exactly what I
need. I need the opposite: Not shortening the path but extending it.
But it is not simply extending the path component by an additional
string, because there must be some mechanism ("Magic") which maps
the
I downloaded Axis 1.2 RC2.
The problem seems to be gone now.
However is Axis 1.2 JDK1.3 compatible?
Regards,
Harm de Laat
Ciber
The Netherlands
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Mon 1/24/2005 10:21 PM
To: [EMAIL PROTECTED]; [EMAIL
Did you get an answer to this problem?
I have a similar problem running in an AppServer. I want to set http.proxyHost
but not at the System level. I am using WSDL2Java so I cannot get to the call
object to set the properties on the Call.
Graeme Riddell wrote:
I have a multithreaded app that is
Using AXIS 1.1
Our webservice client is running in an AppServer.
We are using WSDL2Java to generate a set of client bindings.
Is it possible to connect via a proxy server without setting the JVM level
http.proxyHost System properties?
ta,
Stuart
yes, it is...
-- dims
On Tue, 25 Jan 2005 10:24:07 +0100, Harm de Laat [EMAIL PROTECTED] wrote:
I downloaded Axis 1.2 RC2.
The problem seems to be gone now.
However is Axis 1.2 JDK1.3 compatible?
Regards,
Harm de Laat
Ciber
The Netherlands
-Original Message-
From:
Thanks Dims. I just tried last nights cvs and I get the same results. I will
log a Jira issuse as you recommend.
Cheers,
Joel
On Monday 24 January 2005 21:17, Davanum Srinivas wrote:
Joel,
1) Try latest CVS version/nightly build of axis.
2) Log a bug in JIRA
thanks,
dims
On Mon, 24 Jan
http://marc.theaimsgroup.com/?l=axis-devm=105787295106872w=2
On Tue, 25 Jan 2005 11:53:51 +, Stuart Barlow [EMAIL PROTECTED] wrote:
Did you get an answer to this problem?
I have a similar problem running in an AppServer. I want to set http.proxyHost
but not at the System level. I am
No everything works fine with version 1.2 RC1. It's just that I was
using version 1.1 as this is shown as the latest stable release. So far
I haven't found any problems with the new version although I hope there
is an final release soon.
So, the problem exists if you use version 1.1 but is fixed
Hi,
I'm trying to make a GUI application which is getting data through
SOAP using Apache Axis.
User can make a request for fetching data (by pressing some button),
after which action he can deside, he don't need that data - by
pressing stop button.
When a user presses that request button, I
If your spawning a new thread to handle the 'request and invoke', I
would imagine all you need to do is to terminal that thread and forward
to the client a custom response of your choice like 'request
successfully terminated, try again ?'
Once your at this point you can consider further options
Title: Message
Hi,
How Could i run
AdminClient, if my Tomcat server is running on port 80 and not on port 8080
??
Regards
yep. i think so.
-- dim
On Tue, 25 Jan 2005 13:29:01 +, Stuart Barlow [EMAIL PROTECTED] wrote:
Thanks for the details Davanum. My theaimsgroup search did not
hit this stuff so much appreciated.
Taking a look inside the DefaultHTTPTransportClientProperties class
I can see that it gets
Usage: AdminClient [Options] [list | deployment-descriptor-files]
Processes a set of administration commands.
The following Options are available:
-lurl sets the AxisServlet URL
-hhostName sets the AxisServlet host
-pportNumber sets the AxisServlet port
Oh, sorry for doublepost, I had some problems with gmail..
Thanks for your reply, but it's not so simple. You cannot kill or
terminate thread in java. You can only set some boolean value, that
you want to terminate and the thread have to terminate on it's own.
Like this:
public void run() {
You cannot kill or
terminate thread in java
Not directly no, but there are work arounds - this link seems to fit
your request.
http://forum.java.sun.com/thread.jspa?threadID=231781messageID=829622
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 January
I tried the Thread.join(), recommended in that discussion, but it does nothing.
Title: Message
Thread.join() only **waits** for the thread to finish. It does NOT
kill/finish/interrupt it. There is no way to kill/abort/destroy/suicide a
thread in Java, as it caused problems in the past with synchronization.
Perhaps JDK1.5 added functionalitiesfor this, didnt have time to
I have set...
System.setProperty(org.apache.axis.components.net.TransportClientProperties,
com.peopledoc.jura.dmintegration.spi.impl.AXISTransportClientProperties);
Unfortunatly I am now getting...
2005-01-25 15:20:57,187 ERROR axis.AxisProperties [Jura Thread #12] Exception:
looks like it...this is not a good fix, but just add your
com.peopledoc.jura.dmintegration.spi.impl.AXISTransportClientProperties
to axis jar itself to see if it works and then tackle the classloader
issue.
-- dims
On Tue, 25 Jan 2005 15:32:23 +, Stuart Barlow [EMAIL PROTECTED] wrote:
I
Hello,
I recently discovered the usage of log4j to show me Axis debuging
information,
now I wonder what is the best way to be able to debug or log any errors
from my server side classes,
so far I was only able to get understandable exceptions form my client
code (obviously that's as easy as
Assuming that you did this inside a class:
...
private static final Logger logger = LogManager.getLogger(SomeClass.class);
...
You can use the extra parameter to debug(), info(), error(), fatal(),
etc. Like so:
try {
throw new Exception(Ouch!);
} catch (Exception e) {
// The second
Thanks for that idea with connection, that sounds really promising.
But can you push me near the process of getting the Axis connection,
please? I am digging throught Axis sources and its JavaDoc help and
can't find any glue..
You can use Thread.join(long m) to solve your problem like this:
===
public class Tester {
InvokerThread invoker;
static boolean gotResponse = false;
public Tester() throws Exception {
invoker = new InvokerThread();
invoker.start();
Hello all.
What is the best way to configure the SecurityProvider for the
SimpleAuthenticationHandler? I know that I need to set it in the
message context, and that it needs to be set before the SAH gets called.
One way I can think of is to create a handler that performs my
authentication by
I am looking at bug http://issues.apache.org/jira/browse/AXIS-986.
Someone submitted the patch but looks ike this was not added to CVS. This bug
surely is a huge bug for those who are using Contaienr based session management
on server side. I am really surprised why this patch was not added
Praveen,
Would you be able to port this to latest Axis cvs? i need a diff -u
against latest CVS.
thanks,
dims
On Tue, 25 Jan 2005 14:30:27 -0500, Praveen Peddi
[EMAIL PROTECTED] wrote:
I am looking at bug http://issues.apache.org/jira/browse/AXIS-986. Someone
submitted the patch but looks
I don't mind doing that but I have to get the source, build, change the
code, test etc. We are trying another work around that was suggested at
http://article.gmane.org/gmane.text.xml.axis.user/16296. If this doesn't
work, I will be happy to send you the patch for bug 986.
Thanks
Praveen
-
Just a few comments
Petr is describing two problems I think: the blocking nature of Call.invoke,
and the lack of a cancellation method for halting a Call.invoke.
As to the blocking problem, there is no documentation on it, but in the
org.apache.axis.client.async package, there is an
sure. yep, it's a lot of work :)
-- dims
On Tue, 25 Jan 2005 15:47:14 -0500, Praveen Peddi
[EMAIL PROTECTED] wrote:
I don't mind doing that but I have to get the source, build, change the
code, test etc. We are trying another work around that was suggested at
Hi,
I am having a lot of trouble installing the WS-I example. I have compiled
the code with ant which created a directory structure as follows
axis-1_2RC2\build\classes\org\apache\axis\wsi\scm which do not contain
deploy.wsdd files but the source directory does. I ran the AdminClient from
both
I'm looking at the SOAPHeaderElement in Axis 1.1, it appears that for
serialization I can pass it a strongly typed object, but for
de-serialization (either on the server trying to read a header passed by
the client, or on the client trying to read a header returned by the
server) there doesn't
I mapped the Axis servlet to a custom URL (e.g. /app/ws) rather than the
default /axis/services/ or whatever it is.
Now if I simply go to: http://server:port/app/ws I see a bunch of links
to the (wsdl) files for each service, but the link is wrong, it is of
the form /app/services/Foo?wsdl
Hello,
How can I turn off these features for an Axis production deployment:
1) Disable the generation of WSDL when one goes to
http://server:port/app/ws/ServiceName?wsdl
2) Turn off listing the available services and their methods by going to
http://server:port/app/ws/
3) Turn off all Admin
To: 皆様
木村です。
アパッチのインフラ管理チームから、サーバOSのセキュリティパッチ適用等の
理由で、本日サーバを再起動するとの緊急アナウンスがありました。
■日時: 2005年1月16日 14:00〜 (数分
−
木村です。
[EMAIL PROTECTED];W$$$^$9$,!"F|IU$Ktypoがありました。
本日ですので、16日ではなく26日です。
■日時: 2005年1月26日 14:00〜 (数分
− 数十分程度) [日本時間]
宜しく御願いします。
We were having our application running fine under
websphere 4.0
Now, we are upgrading to websphere 5.0, keeping the same
setup and code and we are getting error,
sslhandshakeexception: unknown
certificate
We have the certificate in the keystore file.
When we look at the system properties,
Greetings!
I have used Axis Java before in both our client and
server.
I am wondering if it is possible if the server is
Axis C++ and the client is Axis Java.
How about custom objects serializability? will it
work?
Thanks!
Regards,
Benedick
37 matches
Mail list logo
