Re: jboss normal client/server communication

From: Jon Martin Solaas (jonmartin.solaas_at_mail.link.no)
Date: 10/20/03 

Date: Mon, 20 Oct 2003 10:14:15 GMT

bigbinc wrote:
> I have been using jboss for a short time and am pretty interested, but
> how should I research using jboss on one machine and a non j2ee on
> another machine.
> The non-j2ee will communicate through a servlet, the jboss will
> receive the messages with its bean protocol.
>
> Could I use SOAP, normal socket communication?

You could use both soap or webservices to achieve this, but you'd need
some client side libraries for marshalling and setting up the
communications in both cases.

Setting up a servlet on the server and communicate directly with this
from your client should also work, for many purposes «inventing» a small
protocol on top of http works just fine. The servlet could even emit
xml. If your client talk TCP you should be able to get along with no
specific client libs.

Communicating thru sockets should also work, but I'm not sure how you
should configure your serverside component. EJB's can't use sockets. I
guess servlets can, but using servlets (or jsp), talking http would be a
much more natural choice. (Actually EJB's can use sockets, nobody checks
that, but it's in violation of the spec, and taking into account how
ejb's are implemented (on various servers) you'd end up getting some
quite unexpected results, I suppose ...)

It's pretty important to consider the needs of your app before settling
for a specific architecture. Exactly how is the client meant to be
implemented? Swing? Web-pages? Is it perhaps a Windows-program? Is it
going to run in the same local area network as the server, or are they
going to communicate over the Internet? The most usual way to do this
today is to have everything running on the server and let users access
the app with a browser. 

-- 
jonmartin.solaas¤h0tm4i1

Relevant Pages

  • Re: Clarification on firewall issues with Java networking APIs
    ... work properly when either the client or the server is behind a proxy unless ... A RMI server registers its service with the rmiregistry, ... assigned or tells the registry the port that it actually listen on. ... routine and the servlet can send a reply on that already established socket. ...
    (comp.lang.java.programmer)
  • Re: jboss normal client/server communication
    ... > some client side libraries for marshalling and setting up the ... > Setting up a servlet on the server and communicate directly with this ... The servlet could even emit ... > going to run in the same local area network as the server, ...
    (comp.lang.java.programmer)
  • Re: Clarification on firewall issues with Java networking APIs
    ... work properly when either the client or the server is behind a proxy unless tunneling is used and that tunneling is slow and prevents callbacks from being used. ... assigned or tells the registry the port that it actually listen on. ... routine and the servlet can send a reply on that already established socket. ...
    (comp.lang.java.programmer)
  • Trying to send XML with HTTP POST to a Servlet
    ... I am trying to send some XML stuff through HTTP POST using a Java HTTP ... client and a Servlet, and it doesn't seem to work! ... Here is my client code: ... Here is my server code: ...
    (comp.lang.java.programmer)
  • Re: can i recive a txt file from client to my servlet?
    ... A servlet (or any server) cannot reach out to a client and retrieve a file. ... The client is an applet loaded from a web page. ...
    (comp.lang.java.help)
Loading