RE: porting from socket to SOAP
Most implementations of SOAP use HTTP which means the connection is closed after each client request (or possibly closed). This means that any data sent from the server must first come from a client request. It also depends on the nodes that are communicating. To implement effecient communication along the lines of what you want would mean having 2 J2EEcommunicating using message driven beans, a bit like B2B. 1. [A] sends a SOAP request to [B] which is then forwarded to a Message Driven Bean. 2. The bean then periodically sends SOAP updates to [A], you can catch this using any method you like on node [A]. The hard part is once you have received the message on server [A] then you would need to forward this message to the client application a. One way of doing that would be to have the client application become a SocketServer. you could then connect to this from within the J2EE server on node [A] using an EJB as a socketClient (which is permitted in the specifications) and forward the data down the socket... You may ask what you gain from the above setup since you are aready using SOAP?? The biggest advantage would be that you can communicate across the internet with the above example through any fire wall. Another example is that you never have to have a continuous connection. You could make your client application server socket a pooled resource making the code more scalable... Although it does seem overkill and probably harder to setup at first there would be advantages. The reason you have not found anyone doing this yet is because it is only really just being developed to its potential by individual companies...you would be a first! -Original Message-From: Mike Brown [mailto:[EMAIL PROTECTED]]Sent: 28 February 2002 06:36To: [EMAIL PROTECTED]Subject: porting from socket to SOAP Hi, I am currently researching the use of XML based protocols for messaging in an application we currently have that uses TCP/IP sockets. In the application, two programs A and B communicate using sockets. A connects to B and asks B to send asyncronous data updates over the socket. If B terminates, A is notified (uses a select() behavior) and marks the data from B as stale (so it won't be displayed to a user, etc...). I need to keep the functionality of the existing application, but would like to use SOAP if possible as it seems to be the upcoming standard. Any ideas? I know I'm not the first to try to solve this problem, but I can't seem to find the solution posted anywhere. I'm not really sure that sessions or cookies can solve my problem. Thanks! Mike This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: porting from socket to SOAP
With comments like this "This means that any data sent from the server must first come from a client request." (SEEBELOW) you would think that it was Monday morning!! (doh...)my apologies but you get what I mean...(I hope!!) -Original Message-From: Colin Saxton [mailto:[EMAIL PROTECTED]]Sent: 28 February 2002 09:39To: '[EMAIL PROTECTED]'Subject: RE: porting from socket to SOAP Most implementations of SOAP use HTTP which means the connection is closed after each client request (or possibly closed). This means that any data sent from the server must first come from a client request. It also depends on the nodes that are communicating. To implement effecient communication along the lines of what you want would mean having 2 J2EEcommunicating using message driven beans, a bit like B2B. 1. [A] sends a SOAP request to [B] which is then forwarded to a Message Driven Bean. 2. The bean then periodically sends SOAP updates to [A], you can catch this using any method you like on node [A]. The hard part is once you have received the message on server [A] then you would need to forward this message to the client application a. One way of doing that would be to have the client application become a SocketServer. you could then connect to this from within the J2EE server on node [A] using an EJB as a socketClient (which is permitted in the specifications) and forward the data down the socket... You may ask what you gain from the above setup since you are aready using SOAP?? The biggest advantage would be that you can communicate across the internet with the above example through any fire wall. Another example is that you never have to have a continuous connection. You could make your client application server socket a pooled resource making the code more scalable... Although it does seem overkill and probably harder to setup at first there would be advantages. The reason you have not found anyone doing this yet is because it is only really just being developed to its potential by individual companies...you would be a first! -Original Message-From: Mike Brown [mailto:[EMAIL PROTECTED]]Sent: 28 February 2002 06:36To: [EMAIL PROTECTED]Subject: porting from socket to SOAP Hi, I am currently researching the use of XML based protocols for messaging in an application we currently have that uses TCP/IP sockets. In the application, two programs A and B communicate using sockets. A connects to B and asks B to send asyncronous data updates over the socket. If B terminates, A is notified (uses a select() behavior) and marks the data from B as stale (so it won't be displayed to a user, etc...). I need to keep the functionality of the existing application, but would like to use SOAP if possible as it seems to be the upcoming standard. Any ideas? I know I'm not the first to try to solve this problem, but I can't seem to find the solution posted anywhere. I'm not really sure that sessions or cookies can solve my problem. Thanks! MikeThis email and any files transmitted with it are confidential andintended solely for the use of the individual or entity to whomthey are addressed. Any views or opinions are solely those ofthe author and do not necessarily represent those of ExelComputer Systems plc. If you have received this email in errorplease notify Customer Services on 0115 946 0101.
Inspection of a returned Response-Object
Hi, trying invoke(URLStringValue, SOAPActionValue) on my Call-Object, I receive a response-object. Using the method getParams() and size() on the returned Vector [myParaVector = myResp.getParams(); int myVecSize = myParaVector.size();] to inspect the field params of the returned response-object, I get a NullPointerException. How is it possible to set the field params of the response-object, that is returned by the method invoke(...), so that within the client a detailed inspection of the field params of the response-object is possible. May be, that it's a trivial question, but any help would be appreciated. Thanks in advance Michael Buchardt Zeitschriftenabos online bestellen - jetzt neu im Infoboten! http://www.epost.de
RE: porting from socket to SOAP
Our system received asynchronous callbacks from B using our own custom protocol that was similar to HTTP. When we decided to switch to SOAP for messaging, we also changed the transport to HTTP. HTTP uses a request-response method of transmission, whereas our systems also require a solicit-response model. I posted about this in the Axis User list, but got no response. See my message and my solution at http://marc.theaimsgroup.com/?l=axis-userm=101430720610385w=2 cheers, Simon
Re: get real XML message of Call instance
Would somebody please give me the email address that I can unsubscribe from this user list? Thanks. Tim --- Fred Meredith [EMAIL PROTECTED] wrote: --- I'm assuming you want to do this on the client side? But anyway, you can call the buildEnvelope method of the Call object to return an Envelope object. Then with the Envelope object call the marshall method and pass it a StringWriter (or whatever, FileWriter, StreamWriter, etc.), SOAPMappingRegistry, and SOAPContext. You may have to instantiate new instances of SOAPMappingRegistry and SOAPContext for this to work. The XML text can then be read from the *Writer object you passed in the marshall method. I need to get the real XML message which will be generated by a Call instance. Is that possible? Thanks in advance Oliver *** BITTE BEACHTEN *** Diese Nachricht (wie auch allfällige Anhänge dazu) beinhaltet möglicherweise vertrauliche oder gesetzlich geschützte Daten oder Informationen. Zum Empfang derselben ist (sind) ausschliesslich die genannte(n) Person(en) bestimmt. Falls Sie diese Nachricht irrtümlicherweise erreicht hat, sind Sie höflich gebeten, diese unter Ausschluss jeder Reproduktion zu zerstören und die absendende Person umgehend zu benachrichtigen. Vielen Dank für Ihre Hilfe. = Tim's home page: http://www.geocities.com/timwei __ Do You Yahoo!? Yahoo! Greetings - Send FREE e-cards for every occasion! http://greetings.yahoo.com
Re: porting from socket to SOAP
Thanks Colin and Simon for your responses! After further reading, I'm wondering if there is a way to do this using HTTP/SSL. (I also need to tackle our security problem). Can I setup a HTTPS connection between the two programs and ensure that the connection is persistent? Program A connects to program B with a persistent HTTPS connection. SOAP-RPC is used to exchange information while the connection is active. If B terminates, A could know by periodically checking the connection status? I'm pretty new to all this so it may/may not be feasible. I would like to use SSL though. I'm currently using Java/Tomcat/Axis, but I would like to ensure that VB, C++, C#, Perl, PHP programs would be able to play nicely with my programs. Thanks. Mike - Original Message - From: Colin Saxton To: '[EMAIL PROTECTED]' Sent: Thursday, February 28, 2002 3:49 AM Subject: RE: porting from socket to SOAP With comments like this This means that any data sent from the server must first come from a client request. (SEE BELOW) you would think that it was Monday morning!! (doh...) my apologies but you get what I mean...(I hope!!) -Original Message- From: Colin Saxton [mailto:[EMAIL PROTECTED]] Sent: 28 February 2002 09:39 To: '[EMAIL PROTECTED]' Subject: RE: porting from socket to SOAP Most implementations of SOAP use HTTP which means the connection is closed after each client request (or possibly closed). This means that any data sent from the server must first come from a client request. It also depends on the nodes that are communicating. To implement effecient communication along the lines of what you want would mean having 2 J2EE communicating using message driven beans, a bit like B2B. 1. [A] sends a SOAP request to [B] which is then forwarded to a Message Driven Bean. 2. The bean then periodically sends SOAP updates to [A], you can catch this using any method you like on node [A]. The hard part is once you have received the message on server [A] then you would need to forward this message to the client application a. One way of doing that would be to have the client application become a SocketServer. you could then connect to this from within the J2EE server on node [A] using an EJB as a socketClient (which is permitted in the specifications) and forward the data down the socket... You may ask what you gain from the above setup since you are aready using SOAP?? The biggest advantage would be that you can communicate across the internet with the above example through any fire wall. Another example is that you never have to have a continuous connection. You could make your client application server socket a pooled resource making the code more scalable... Although it does seem overkill and probably harder to setup at first there would be advantages. The reason you have not found anyone doing this yet is because it is only really just being developed to its potential by individual companies...you would be a first! -Original Message- From: Mike Brown [mailto:[EMAIL PROTECTED]] Sent: 28 February 2002 06:36 To: [EMAIL PROTECTED] Subject: porting from socket to SOAP Hi, I am currently researching the use of XML based protocols for messaging in an application we currently have that uses TCP/IP sockets. In the application, two programs A and B communicate using sockets. A connects to B and asks B to send asyncronous data updates over the socket. If B terminates, A is notified (uses a select() behavior) and marks the data from B as stale (so it won't be displayed to a user, etc...). I need to keep the functionality of the existing application, but would like to use SOAP if possible as it seems to be the upcoming standard. Any ideas? I know I'm not the first to try to solve this problem, but I can't seem to find the solution posted anywhere. I'm not really sure that sessions or cookies can solve my problem. Thanks! Mike This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
RE: sun j2ee ref impl and soap 2.2
I also agree. Use the JBoss/Tomcat or JBoss/Jetty 2.4.4 packages and simply drop the soap .war file into the deploy directory. Cheers! -Original Message- From: Colin Saxton [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 28, 2002 1:19 AM To: '[EMAIL PROTECTED]' Subject: RE: sun j2ee ref impl and soap 2.2 Use JBoss instead! its free (www.jboss.org) -Original Message- From: Paul Baker [mailto:[EMAIL PROTECTED]] Sent: 27 February 2002 23:18 To: [EMAIL PROTECTED] Subject: sun j2ee ref impl and soap 2.2 Anyone have a receipe (or success story) to install soap 2.2 on the latest j2ee ref implementation (1.3.1) from Sun? I'm not having much luck deploying the soap war file. I'm new to soap, and relatively new to the deployment thing... if theres any resource one could point me to I'd be grateful. Regards, Paul -Original Message- From: Mark Childerson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 5:27 PM To: [EMAIL PROTECTED] Subject: Re: soap 2.2 and Tomcat 4.0 It seems to. We are using it that way at our office. M. At 02:03 PM 2/27/02 -0800, you wrote: thanks for the responsewill soap 2.2 work with the lastest jdk 1.4? thanks in advance! - Original Message - From: Harnish, Michael [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 27, 2002 1:37 PM Subject: RE: soap 2.2 and Tomcat 4.0 Joo, It works with Tomcat 4.0. The installation procedures are pretty much the same, if I remember correctly, as they are in http://xml.apache.org/soap/docs/index.html, which explains how to install it under Tomcat 3.2. One exception: tomcat.bat and tomcat.sh referenced in those instructions have been replaced by catalina.bat and catalina.sh. Change *those* files to put the xerces.jar at the beginning of the TC4 classpath, as instructed in the aforementioned link. Caveat: I got it working by deploying the soap.war file, not by adding a context to the conf/server.xml. I assume that way will work too. Regards, Mike -Original Message- From: Joo Park [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 2:19 PM To: [EMAIL PROTECTED] Subject: soap 2.2 and Tomcat 4.0 Does Soap 2.2 work with Tomcat 4.0 and do I have to do anything special to get it working? thanks in advance! This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions are solely those of the author and do not necessarily represent those of Exel Computer Systems plc. If you have received this email in error please notify Customer Services on 0115 946 0101.
WSDL vs SOAP service
What is difference of web service(WSDL) and SOAP service? Are they same? Deploy the web service in SOAP server is same as deploy soap service? Thanks Harden
RE: WSDL vs SOAP service
Harden, Webservices is really more of a concept that a tangible entity. Basically webservices is the idea of transmitting self-describing objects over layer 7 protocols. SOAP and WSDL are components which comprise a working implementation of the web services concept. For more information see the following links: http://www-106.ibm.com/developerworks/webservices/ http://www.w3.org/2002/ws/ http://java.sun.com/webservices/ http://msdn.microsoft.com/library/default.asp?url=/nhp/Default.asp?contentid=28000442 -Brian Abbott -Original Message- From: Harden ZHU [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 28, 2002 2:41 PM To: [EMAIL PROTECTED] Subject: WSDL vs SOAP service What is difference of web service(WSDL) and SOAP service? Are they same? Deploy the web service in SOAP server is same as deploy soap service? Thanks Harden
error to run a installation command
When I run the following command, I got the error: java org.apache.soap.server.ServiceManagerClient rcp-router-url list Exception in thread main java.net.MalformedURLException: no protocol: rcp-rout er-url at java.net.URL.init(URL.java:473) at java.net.URL.init(URL.java:376) at java.net.URL.init(URL.java:330) at org.apache.soap.server.ServiceManagerClient.main(ServiceManagerClient .java:216) My soap web site is up and server is running. Thanks, Emily
Java SOAP call
Please can someone answer this... I have written a port listener and redirected my soap calls to go through this listener (proxy). Why does the header start like this: POST HTTP/1.0 with no path supplied in between? The call still seems to work but I am confused as to how, if there is no path given for the server Hopefully someone can answer what is probably a very simple question? Thank you Regards Neil
RE: Urgent Help requirred - Limitations of the TcpTunnel
I believe the tunnel uses an AWT TextArea to display data. There is a 32k character limit on the display - furthermore, the tunnel works with small chunks of characters, repeatedly adding them to the TextArea - this does not work well with large messages. To capture large messages, modify the Relay.java class to write to files instead of to TextAreas [EMAIL PROTECTED] Author of Soap Programming with Java - Sybex; ISBN: 0782129285 -Original Message- From: Aniruddha Shevade [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 7:45 PM To: [EMAIL PROTECTED] Subject: Urgent Help requirred - Limitations of the TcpTunnel Hello All Another question about the tunnel. Is there a limitation on the buffer size of teh data which can be handled by th tunnel. There seems to be some problem when very huge amount of Data , ( Such as a large File download being sent through a Tunnel ). I am seeing the application crash Has anybody seen similar problems Thanks -Aniruddha
