Discussions

News: Introducing JBoss Remoting

Bookmark and Share Get thread feed

  1. Introducing JBoss Remoting (8 messages)

    • Posted by: Dion Almaer
    • Posted on: February 25 2005 12:32 EST
    Recently, JBoss introduced a new open source remoting framework called JBoss Remoting. It serves as the core framework for the next generation (v5.0) JBoss Application Server (AS) to provide remote services--things like remoting JMX MBeans, remoting EJBs, and so on. JBoss Remoting can also be used as a standalone framework to build network-aware services independent of the JBoss AS.

    Read more: Introducing JBoss Remoting
    Reply to this

    Threaded Messages (8)

  2. Introducing JBoss Remoting[ Go to top ]

    For transport independence we are using WSIF (Apache).

    Are there any compeling reasons for using this framework instead of using WSIF?
    Reply to this Reply to original

  3. Introducing JBoss Remoting[ Go to top ]

    Are there any compeling reasons for using this framework instead of using WSIF?

    What about not beeing dependant on Apache?
    Reply to this Reply to original

  4. Introducing JBoss Remoting[ Go to top ]

    Are there any compeling reasons for using this framework instead of using WSIF?
    What about not beeing dependant on Apache?

    Well, I'm afraid that JBoss Remoting might not be your best choice to become independent from Apache: JBoss in general has numerous Apache dependencies itself: Tomcat, Axis, Log4J, etc. I would assume that JBoss Remoting uses some Apache libraries too.

    Juergen
    Reply to this Reply to original

  5. Introducing JBoss Remoting[ Go to top ]

    The only Apache libraries included in the distribution is commons-logging.jar, log4j.xml, and commons-httpclient.jar. The common-httpclient.jar is not even used because could not gain access to the streams as needed, so had to write it from scratch. Just never deleted the imports and jar.
    Reply to this Reply to original

  6. Introducing JBoss Remoting[ Go to top ]

    Are there any compeling reasons for using this framework instead of using WSIF?
    What about not beeing dependant on Apache?

    What about more than just web services ?
    Reply to this Reply to original

  7. Introducing JBoss Remoting[ Go to top ]

    Someone had mentioned WSIF before and I am not very familiar with it. I will look into it in further detail and respond back with the difference I find(but will be a little while before I have the time).

    Until then, it looks like WSIF is focused on providing a simpler programming interface for the web services model. JBoss Remoting is a little more general in that it is not directly tied to web services (actually our web services project, JBossWS, will sit on top of JBoss Remoting and provide the extra web services specific features).

    Also, at first glance, it did not seem like WSIF has features like sync/async callbacks, remote classloading, and auto discovery.
    Reply to this Reply to original

  8. Spring support[ Go to top ]

    Will Spring remoting support it? :)

    Rong
    http://rongou.blogspot.com
    Reply to this Reply to original

  9. Spring support[ Go to top ]

    Great question. Spring, will you guys be supporting JBoss Remoting in the future?
    Reply to this Reply to original