[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jboss-user
Subject:    [jboss-user] [JBoss Remoting Users] - Re: J2EE remote client HTTP
From:       "ron.sigal () jboss ! com" <do-not-reply () jboss ! com>
Date:       2009-09-30 23:18:04
Message-ID: 31146204.1254352684374.JavaMail.jboss () nukes01 ! app ! mwc ! hst ! phx2 ! redhat ! com
[Download RAW message or body]

"bwarren" wrote : 
  | Is JBoss Remoting the way to go here?
  | 

Well, as it happens, JBossRemoting is the way you've already gone.  EJBs, EJB3s, and \
JBossMessaging connections all, by default, use JBossRemoting as their transport \
layer, each, again by default, with their own Remoting servers listening on ports \
other than 80.  However, one of the primary design principles of Remoting is the \
ability to swap one Remoting transport for another.  In your case, you can get closer \
to your goal with the servlet transport, in which all of the various proxies connect \
to a Remoting servlet, which then passes the invocations to the appropriate \
subsystem.  Of course, you would need a servlet container (i.e., a JBossWeb (aka \
Tomcat) connector) listening on port 80.  Can you do that?  Or will the network \
powers open up, say, 8080 (the default JBossWeb port in the Application Server - see \
$JBOSS_HOME/server/$CONFIG/deploy/jboss-web.deployer/server.xml)?

The configuration details are given in the wiki entry "EJB, JMS and JNDI over HTTP \
with Unified Invoker" at \
http://www.jboss.org/community/wiki/EJBJMSandJNDIoverHTTPwithUnifiedInvoker.

What do you think?

View the original post : \
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258016#4258016

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258016
 _______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[prev in list] [next in list] [prev in thread] [next in thread]