You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Michael Kempf <mi...@student-zw.fh-kl.de> on 2002/05/28 15:20:08 UTC
How to throw a server-side exception at application level ?
hi all,
my soap-client sends a login and password in the body of the
soap-message to the server-server.
How can the soap-server sends a fault-code if the login and password
are not correct ?
-michael
RE: About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
Thank you Mark, it works exactly as you instructed.
Rufeng
-----Original Message-----
From: Mark Childerson [mailto:mark@childersoft.com]
Sent: Wednesday, May 29, 2002 10:10 AM
To: soap-user@xml.apache.org
Subject: RE: About using TcpTunnelGui tool
TcpTunnelGUI works for things other than SOAP. To get a good example of how
it works, try this:
ping www.exdocs.com to get an IP address, let's say it is xxx.xxx.xxx.xxx
TcpTunnelGui 80 xxx.xxx.xxx.xxx 80
Then, go into your browser and go to http://localhost:80
You will see, in the browser, exactly what you would see at www.exdocs.com.
The TcpTunnelGui program shows all the traffic passing through.
Therefore, to test your SOAP setup, you need to do the following:
1. Set up Tomcat on your desired host computer, ren.cs.odu.edu, listening
on port 8989 (which is NOT the default for Tomcat. The default is 8080)
2. TcpTunnelGui 8888 ren.cs.odu.edu 8989
3. Run your SOAP client program, with no jars other than you normally would
have to run the SOAP client without TcpTunnelGUI (ie, you need soap.jar and
xerces.jar, if you ar eusing Apache SOAP as a client). The ONLY change in
your normal setup is that the client should be directed at
http://localhost:8888/soap/servlet/rpcrouter . Port 8888 should be fine,
since it is unlikely your client computer will have any other service
listening on post 8888. TcpTunnelGui would probably tell you if it did.
Hope this helps,
Mark
At 04:30 PM 28/05/2002 -0400, you wrote:
>I am still confused with the usage of the tool. Can anybody show me a
worked
>example? Please let me know the details, like:
>
>1. what you type in the command line on your monitoring machine?
>2. what is needed to be running on your monitoring machine except soap.jar?
>3. what url you specify in your SOAP client, like
>http://localhost:8888/soap/servlet/rpcrouter or http://localhost:8888?
>because the port number 8888 is an randomly selected, will
>http://localhost:8888/soap/servlet/rpcrouter work?
>
>Rufeng
>
>-----Original Message-----
>From: Mark Childerson [mailto:mark@childersoft.com]
>Sent: Tuesday, May 28, 2002 12:16 PM
>To: soap-user@xml.apache.org
>Subject: Re: About using TcpTunnelGui tool
>
>
>Your SOAP client should be looking for
>http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
>automatically translate that to the desired URL.
>
>Mark.
>
>At 11:58 AM 28/05/2002 -0400, you wrote:
> >Hello,
> >
> >I was trying to use the TcpTunnelGui tool like the following on my local
> >machine:
> >
> >c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
> >
> >where 8888 is listenport on my local machine, ren.cs.odu.edu is
tunnelhost
> >(a UNIX machine), and 8989 is tunnelport. My soap service is running on
> >ren.cs.odu.edu:8989 hosted by tomcat.
> >
> >The GUI tool received and showed the request message from the soap
client,
>I
> >see it in the first window and it looks fine, but in the second window it
> >showed the tomcat exception messages and it seemed the soap request
didn't
> >get to the soap service.
> >
> >My question is don't we need to specify the router like
> >http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
> >http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
>TcpTunnelGui
> >konw where to find the soap router and services if we don't provide this
> >detail.
> >
> >Please give me some help.
> >
> >Thanks alot!
> >
> >Rufeng
RE: About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
Thank you Mark, it works exactly as you instructed.
Rufeng
-----Original Message-----
From: Mark Childerson [mailto:mark@childersoft.com]
Sent: Wednesday, May 29, 2002 10:10 AM
To: soap-user@xml.apache.org
Subject: RE: About using TcpTunnelGui tool
TcpTunnelGUI works for things other than SOAP. To get a good example of how
it works, try this:
ping www.exdocs.com to get an IP address, let's say it is xxx.xxx.xxx.xxx
TcpTunnelGui 80 xxx.xxx.xxx.xxx 80
Then, go into your browser and go to http://localhost:80
You will see, in the browser, exactly what you would see at www.exdocs.com.
The TcpTunnelGui program shows all the traffic passing through.
Therefore, to test your SOAP setup, you need to do the following:
1. Set up Tomcat on your desired host computer, ren.cs.odu.edu, listening
on port 8989 (which is NOT the default for Tomcat. The default is 8080)
2. TcpTunnelGui 8888 ren.cs.odu.edu 8989
3. Run your SOAP client program, with no jars other than you normally would
have to run the SOAP client without TcpTunnelGUI (ie, you need soap.jar and
xerces.jar, if you ar eusing Apache SOAP as a client). The ONLY change in
your normal setup is that the client should be directed at
http://localhost:8888/soap/servlet/rpcrouter . Port 8888 should be fine,
since it is unlikely your client computer will have any other service
listening on post 8888. TcpTunnelGui would probably tell you if it did.
Hope this helps,
Mark
At 04:30 PM 28/05/2002 -0400, you wrote:
>I am still confused with the usage of the tool. Can anybody show me a
worked
>example? Please let me know the details, like:
>
>1. what you type in the command line on your monitoring machine?
>2. what is needed to be running on your monitoring machine except soap.jar?
>3. what url you specify in your SOAP client, like
>http://localhost:8888/soap/servlet/rpcrouter or http://localhost:8888?
>because the port number 8888 is an randomly selected, will
>http://localhost:8888/soap/servlet/rpcrouter work?
>
>Rufeng
>
>-----Original Message-----
>From: Mark Childerson [mailto:mark@childersoft.com]
>Sent: Tuesday, May 28, 2002 12:16 PM
>To: soap-user@xml.apache.org
>Subject: Re: About using TcpTunnelGui tool
>
>
>Your SOAP client should be looking for
>http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
>automatically translate that to the desired URL.
>
>Mark.
>
>At 11:58 AM 28/05/2002 -0400, you wrote:
> >Hello,
> >
> >I was trying to use the TcpTunnelGui tool like the following on my local
> >machine:
> >
> >c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
> >
> >where 8888 is listenport on my local machine, ren.cs.odu.edu is
tunnelhost
> >(a UNIX machine), and 8989 is tunnelport. My soap service is running on
> >ren.cs.odu.edu:8989 hosted by tomcat.
> >
> >The GUI tool received and showed the request message from the soap
client,
>I
> >see it in the first window and it looks fine, but in the second window it
> >showed the tomcat exception messages and it seemed the soap request
didn't
> >get to the soap service.
> >
> >My question is don't we need to specify the router like
> >http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
> >http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
>TcpTunnelGui
> >konw where to find the soap router and services if we don't provide this
> >detail.
> >
> >Please give me some help.
> >
> >Thanks alot!
> >
> >Rufeng
RE: About using TcpTunnelGui tool
Posted by Mark Childerson <ma...@childersoft.com>.
TcpTunnelGUI works for things other than SOAP. To get a good example of how
it works, try this:
ping www.exdocs.com to get an IP address, let's say it is xxx.xxx.xxx.xxx
TcpTunnelGui 80 xxx.xxx.xxx.xxx 80
Then, go into your browser and go to http://localhost:80
You will see, in the browser, exactly what you would see at www.exdocs.com.
The TcpTunnelGui program shows all the traffic passing through.
Therefore, to test your SOAP setup, you need to do the following:
1. Set up Tomcat on your desired host computer, ren.cs.odu.edu, listening
on port 8989 (which is NOT the default for Tomcat. The default is 8080)
2. TcpTunnelGui 8888 ren.cs.odu.edu 8989
3. Run your SOAP client program, with no jars other than you normally would
have to run the SOAP client without TcpTunnelGUI (ie, you need soap.jar and
xerces.jar, if you ar eusing Apache SOAP as a client). The ONLY change in
your normal setup is that the client should be directed at
http://localhost:8888/soap/servlet/rpcrouter . Port 8888 should be fine,
since it is unlikely your client computer will have any other service
listening on post 8888. TcpTunnelGui would probably tell you if it did.
Hope this helps,
Mark
At 04:30 PM 28/05/2002 -0400, you wrote:
>I am still confused with the usage of the tool. Can anybody show me a worked
>example? Please let me know the details, like:
>
>1. what you type in the command line on your monitoring machine?
>2. what is needed to be running on your monitoring machine except soap.jar?
>3. what url you specify in your SOAP client, like
>http://localhost:8888/soap/servlet/rpcrouter or http://localhost:8888?
>because the port number 8888 is an randomly selected, will
>http://localhost:8888/soap/servlet/rpcrouter work?
>
>Rufeng
>
>-----Original Message-----
>From: Mark Childerson [mailto:mark@childersoft.com]
>Sent: Tuesday, May 28, 2002 12:16 PM
>To: soap-user@xml.apache.org
>Subject: Re: About using TcpTunnelGui tool
>
>
>Your SOAP client should be looking for
>http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
>automatically translate that to the desired URL.
>
>Mark.
>
>At 11:58 AM 28/05/2002 -0400, you wrote:
> >Hello,
> >
> >I was trying to use the TcpTunnelGui tool like the following on my local
> >machine:
> >
> >c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
> >
> >where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
> >(a UNIX machine), and 8989 is tunnelport. My soap service is running on
> >ren.cs.odu.edu:8989 hosted by tomcat.
> >
> >The GUI tool received and showed the request message from the soap client,
>I
> >see it in the first window and it looks fine, but in the second window it
> >showed the tomcat exception messages and it seemed the soap request didn't
> >get to the soap service.
> >
> >My question is don't we need to specify the router like
> >http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
> >http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
>TcpTunnelGui
> >konw where to find the soap router and services if we don't provide this
> >detail.
> >
> >Please give me some help.
> >
> >Thanks alot!
> >
> >Rufeng
RE: About using TcpTunnelGui tool
Posted by Mark Childerson <ma...@childersoft.com>.
TcpTunnelGUI works for things other than SOAP. To get a good example of how
it works, try this:
ping www.exdocs.com to get an IP address, let's say it is xxx.xxx.xxx.xxx
TcpTunnelGui 80 xxx.xxx.xxx.xxx 80
Then, go into your browser and go to http://localhost:80
You will see, in the browser, exactly what you would see at www.exdocs.com.
The TcpTunnelGui program shows all the traffic passing through.
Therefore, to test your SOAP setup, you need to do the following:
1. Set up Tomcat on your desired host computer, ren.cs.odu.edu, listening
on port 8989 (which is NOT the default for Tomcat. The default is 8080)
2. TcpTunnelGui 8888 ren.cs.odu.edu 8989
3. Run your SOAP client program, with no jars other than you normally would
have to run the SOAP client without TcpTunnelGUI (ie, you need soap.jar and
xerces.jar, if you ar eusing Apache SOAP as a client). The ONLY change in
your normal setup is that the client should be directed at
http://localhost:8888/soap/servlet/rpcrouter . Port 8888 should be fine,
since it is unlikely your client computer will have any other service
listening on post 8888. TcpTunnelGui would probably tell you if it did.
Hope this helps,
Mark
At 04:30 PM 28/05/2002 -0400, you wrote:
>I am still confused with the usage of the tool. Can anybody show me a worked
>example? Please let me know the details, like:
>
>1. what you type in the command line on your monitoring machine?
>2. what is needed to be running on your monitoring machine except soap.jar?
>3. what url you specify in your SOAP client, like
>http://localhost:8888/soap/servlet/rpcrouter or http://localhost:8888?
>because the port number 8888 is an randomly selected, will
>http://localhost:8888/soap/servlet/rpcrouter work?
>
>Rufeng
>
>-----Original Message-----
>From: Mark Childerson [mailto:mark@childersoft.com]
>Sent: Tuesday, May 28, 2002 12:16 PM
>To: soap-user@xml.apache.org
>Subject: Re: About using TcpTunnelGui tool
>
>
>Your SOAP client should be looking for
>http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
>automatically translate that to the desired URL.
>
>Mark.
>
>At 11:58 AM 28/05/2002 -0400, you wrote:
> >Hello,
> >
> >I was trying to use the TcpTunnelGui tool like the following on my local
> >machine:
> >
> >c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
> >
> >where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
> >(a UNIX machine), and 8989 is tunnelport. My soap service is running on
> >ren.cs.odu.edu:8989 hosted by tomcat.
> >
> >The GUI tool received and showed the request message from the soap client,
>I
> >see it in the first window and it looks fine, but in the second window it
> >showed the tomcat exception messages and it seemed the soap request didn't
> >get to the soap service.
> >
> >My question is don't we need to specify the router like
> >http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
> >http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
>TcpTunnelGui
> >konw where to find the soap router and services if we don't provide this
> >detail.
> >
> >Please give me some help.
> >
> >Thanks alot!
> >
> >Rufeng
RE: About using TcpTunnelGui tool
Posted by Mark Childerson <ma...@childersoft.com>.
You dn't need Tomcat on your local machine. The URLs are correct, though.
TcpTunnelGUI "magically" makes it seem to your client as if the Tomcat
service which is in fact running on the ren.cs.odu.edu machine is in fact
running locally.
M.
At 12:28 PM 28/05/2002 -0400, you wrote:
>Thank you Mark. So I need to have a Tomcat running on my local machine while
>I am using TcpTunnelGUI, right? Also my SOAP client should communicate with
>the URL of http://localhost:8888/soap/servlet/rpcrouter, not
>http://localhost:8888, right?
>
>Thanks,
>Rufeng
>
>-----Original Message-----
>From: Mark Childerson [mailto:mark@childersoft.com]
>Sent: Tuesday, May 28, 2002 12:16 PM
>To: soap-user@xml.apache.org
>Subject: Re: About using TcpTunnelGui tool
>
>
>Your SOAP client should be looking for
>http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
>automatically translate that to the desired URL.
>
>Mark.
>
>At 11:58 AM 28/05/2002 -0400, you wrote:
> >Hello,
> >
> >I was trying to use the TcpTunnelGui tool like the following on my local
> >machine:
> >
> >c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
> >
> >where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
> >(a UNIX machine), and 8989 is tunnelport. My soap service is running on
> >ren.cs.odu.edu:8989 hosted by tomcat.
> >
> >The GUI tool received and showed the request message from the soap client,
>I
> >see it in the first window and it looks fine, but in the second window it
> >showed the tomcat exception messages and it seemed the soap request didn't
> >get to the soap service.
> >
> >My question is don't we need to specify the router like
> >http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
> >http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
>TcpTunnelGui
> >konw where to find the soap router and services if we don't provide this
> >detail.
> >
> >Please give me some help.
> >
> >Thanks alot!
> >
> >Rufeng
RE: About using TcpTunnelGui tool
Posted by Mark Childerson <ma...@childersoft.com>.
You dn't need Tomcat on your local machine. The URLs are correct, though.
TcpTunnelGUI "magically" makes it seem to your client as if the Tomcat
service which is in fact running on the ren.cs.odu.edu machine is in fact
running locally.
M.
At 12:28 PM 28/05/2002 -0400, you wrote:
>Thank you Mark. So I need to have a Tomcat running on my local machine while
>I am using TcpTunnelGUI, right? Also my SOAP client should communicate with
>the URL of http://localhost:8888/soap/servlet/rpcrouter, not
>http://localhost:8888, right?
>
>Thanks,
>Rufeng
>
>-----Original Message-----
>From: Mark Childerson [mailto:mark@childersoft.com]
>Sent: Tuesday, May 28, 2002 12:16 PM
>To: soap-user@xml.apache.org
>Subject: Re: About using TcpTunnelGui tool
>
>
>Your SOAP client should be looking for
>http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
>automatically translate that to the desired URL.
>
>Mark.
>
>At 11:58 AM 28/05/2002 -0400, you wrote:
> >Hello,
> >
> >I was trying to use the TcpTunnelGui tool like the following on my local
> >machine:
> >
> >c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
> >
> >where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
> >(a UNIX machine), and 8989 is tunnelport. My soap service is running on
> >ren.cs.odu.edu:8989 hosted by tomcat.
> >
> >The GUI tool received and showed the request message from the soap client,
>I
> >see it in the first window and it looks fine, but in the second window it
> >showed the tomcat exception messages and it seemed the soap request didn't
> >get to the soap service.
> >
> >My question is don't we need to specify the router like
> >http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
> >http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
>TcpTunnelGui
> >konw where to find the soap router and services if we don't provide this
> >detail.
> >
> >Please give me some help.
> >
> >Thanks alot!
> >
> >Rufeng
RE: About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
I am still confused with the usage of the tool. Can anybody show me a worked
example? Please let me know the details, like:
1. what you type in the command line on your monitoring machine?
2. what is needed to be running on your monitoring machine except soap.jar?
3. what url you specify in your SOAP client, like
http://localhost:8888/soap/servlet/rpcrouter or http://localhost:8888?
because the port number 8888 is an randomly selected, will
http://localhost:8888/soap/servlet/rpcrouter work?
Rufeng
-----Original Message-----
From: Mark Childerson [mailto:mark@childersoft.com]
Sent: Tuesday, May 28, 2002 12:16 PM
To: soap-user@xml.apache.org
Subject: Re: About using TcpTunnelGui tool
Your SOAP client should be looking for
http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
automatically translate that to the desired URL.
Mark.
At 11:58 AM 28/05/2002 -0400, you wrote:
>Hello,
>
>I was trying to use the TcpTunnelGui tool like the following on my local
>machine:
>
>c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
>
>where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
>(a UNIX machine), and 8989 is tunnelport. My soap service is running on
>ren.cs.odu.edu:8989 hosted by tomcat.
>
>The GUI tool received and showed the request message from the soap client,
I
>see it in the first window and it looks fine, but in the second window it
>showed the tomcat exception messages and it seemed the soap request didn't
>get to the soap service.
>
>My question is don't we need to specify the router like
>http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
>http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
TcpTunnelGui
>konw where to find the soap router and services if we don't provide this
>detail.
>
>Please give me some help.
>
>Thanks alot!
>
>Rufeng
RE: About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
I am still confused with the usage of the tool. Can anybody show me a worked
example? Please let me know the details, like:
1. what you type in the command line on your monitoring machine?
2. what is needed to be running on your monitoring machine except soap.jar?
3. what url you specify in your SOAP client, like
http://localhost:8888/soap/servlet/rpcrouter or http://localhost:8888?
because the port number 8888 is an randomly selected, will
http://localhost:8888/soap/servlet/rpcrouter work?
Rufeng
-----Original Message-----
From: Mark Childerson [mailto:mark@childersoft.com]
Sent: Tuesday, May 28, 2002 12:16 PM
To: soap-user@xml.apache.org
Subject: Re: About using TcpTunnelGui tool
Your SOAP client should be looking for
http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
automatically translate that to the desired URL.
Mark.
At 11:58 AM 28/05/2002 -0400, you wrote:
>Hello,
>
>I was trying to use the TcpTunnelGui tool like the following on my local
>machine:
>
>c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
>
>where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
>(a UNIX machine), and 8989 is tunnelport. My soap service is running on
>ren.cs.odu.edu:8989 hosted by tomcat.
>
>The GUI tool received and showed the request message from the soap client,
I
>see it in the first window and it looks fine, but in the second window it
>showed the tomcat exception messages and it seemed the soap request didn't
>get to the soap service.
>
>My question is don't we need to specify the router like
>http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
>http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
TcpTunnelGui
>konw where to find the soap router and services if we don't provide this
>detail.
>
>Please give me some help.
>
>Thanks alot!
>
>Rufeng
RE: About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
Thank you Mark. So I need to have a Tomcat running on my local machine while
I am using TcpTunnelGUI, right? Also my SOAP client should communicate with
the URL of http://localhost:8888/soap/servlet/rpcrouter, not
http://localhost:8888, right?
Thanks,
Rufeng
-----Original Message-----
From: Mark Childerson [mailto:mark@childersoft.com]
Sent: Tuesday, May 28, 2002 12:16 PM
To: soap-user@xml.apache.org
Subject: Re: About using TcpTunnelGui tool
Your SOAP client should be looking for
http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
automatically translate that to the desired URL.
Mark.
At 11:58 AM 28/05/2002 -0400, you wrote:
>Hello,
>
>I was trying to use the TcpTunnelGui tool like the following on my local
>machine:
>
>c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
>
>where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
>(a UNIX machine), and 8989 is tunnelport. My soap service is running on
>ren.cs.odu.edu:8989 hosted by tomcat.
>
>The GUI tool received and showed the request message from the soap client,
I
>see it in the first window and it looks fine, but in the second window it
>showed the tomcat exception messages and it seemed the soap request didn't
>get to the soap service.
>
>My question is don't we need to specify the router like
>http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
>http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
TcpTunnelGui
>konw where to find the soap router and services if we don't provide this
>detail.
>
>Please give me some help.
>
>Thanks alot!
>
>Rufeng
RE: About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
Thank you Mark. So I need to have a Tomcat running on my local machine while
I am using TcpTunnelGUI, right? Also my SOAP client should communicate with
the URL of http://localhost:8888/soap/servlet/rpcrouter, not
http://localhost:8888, right?
Thanks,
Rufeng
-----Original Message-----
From: Mark Childerson [mailto:mark@childersoft.com]
Sent: Tuesday, May 28, 2002 12:16 PM
To: soap-user@xml.apache.org
Subject: Re: About using TcpTunnelGui tool
Your SOAP client should be looking for
http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
automatically translate that to the desired URL.
Mark.
At 11:58 AM 28/05/2002 -0400, you wrote:
>Hello,
>
>I was trying to use the TcpTunnelGui tool like the following on my local
>machine:
>
>c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
>
>where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
>(a UNIX machine), and 8989 is tunnelport. My soap service is running on
>ren.cs.odu.edu:8989 hosted by tomcat.
>
>The GUI tool received and showed the request message from the soap client,
I
>see it in the first window and it looks fine, but in the second window it
>showed the tomcat exception messages and it seemed the soap request didn't
>get to the soap service.
>
>My question is don't we need to specify the router like
>http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
>http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will
TcpTunnelGui
>konw where to find the soap router and services if we don't provide this
>detail.
>
>Please give me some help.
>
>Thanks alot!
>
>Rufeng
Re: About using TcpTunnelGui tool
Posted by Mark Childerson <ma...@childersoft.com>.
Your SOAP client should be looking for
http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
automatically translate that to the desired URL.
Mark.
At 11:58 AM 28/05/2002 -0400, you wrote:
>Hello,
>
>I was trying to use the TcpTunnelGui tool like the following on my local
>machine:
>
>c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
>
>where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
>(a UNIX machine), and 8989 is tunnelport. My soap service is running on
>ren.cs.odu.edu:8989 hosted by tomcat.
>
>The GUI tool received and showed the request message from the soap client, I
>see it in the first window and it looks fine, but in the second window it
>showed the tomcat exception messages and it seemed the soap request didn't
>get to the soap service.
>
>My question is don't we need to specify the router like
>http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
>http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will TcpTunnelGui
>konw where to find the soap router and services if we don't provide this
>detail.
>
>Please give me some help.
>
>Thanks alot!
>
>Rufeng
Re: About using TcpTunnelGui tool
Posted by Mark Childerson <ma...@childersoft.com>.
Your SOAP client should be looking for
http://localhost:8888/soap/servlet/rpcrouter TcpTunnelGUI will
automatically translate that to the desired URL.
Mark.
At 11:58 AM 28/05/2002 -0400, you wrote:
>Hello,
>
>I was trying to use the TcpTunnelGui tool like the following on my local
>machine:
>
>c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
>
>where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
>(a UNIX machine), and 8989 is tunnelport. My soap service is running on
>ren.cs.odu.edu:8989 hosted by tomcat.
>
>The GUI tool received and showed the request message from the soap client, I
>see it in the first window and it looks fine, but in the second window it
>showed the tomcat exception messages and it seemed the soap request didn't
>get to the soap service.
>
>My question is don't we need to specify the router like
>http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
>http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will TcpTunnelGui
>konw where to find the soap router and services if we don't provide this
>detail.
>
>Please give me some help.
>
>Thanks alot!
>
>Rufeng
About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
Hello,
I was trying to use the TcpTunnelGui tool like the following on my local
machine:
c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
(a UNIX machine), and 8989 is tunnelport. My soap service is running on
ren.cs.odu.edu:8989 hosted by tomcat.
The GUI tool received and showed the request message from the soap client, I
see it in the first window and it looks fine, but in the second window it
showed the tomcat exception messages and it seemed the soap request didn't
get to the soap service.
My question is don't we need to specify the router like
http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will TcpTunnelGui
konw where to find the soap router and services if we don't provide this
detail.
Please give me some help.
Thanks alot!
Rufeng
About using TcpTunnelGui tool
Posted by Rufeng Liu <rl...@automark.net>.
Hello,
I was trying to use the TcpTunnelGui tool like the following on my local
machine:
c:\>java org.apache.soap.util.net.TcpTunnelGui 8888 ren.cs.odu.edu 8989
where 8888 is listenport on my local machine, ren.cs.odu.edu is tunnelhost
(a UNIX machine), and 8989 is tunnelport. My soap service is running on
ren.cs.odu.edu:8989 hosted by tomcat.
The GUI tool received and showed the request message from the soap client, I
see it in the first window and it looks fine, but in the second window it
showed the tomcat exception messages and it seemed the soap request didn't
get to the soap service.
My question is don't we need to specify the router like
http://ren.cs.odu.edu:8989/soap/servlet/rpcrouter or
http://ren.cs.odu.edu:8989/soap/servlet/messagerouter? How will TcpTunnelGui
konw where to find the soap router and services if we don't provide this
detail.
Please give me some help.
Thanks alot!
Rufeng