5 Replies Latest reply on Aug 23, 2005 12:28 PM by tom.elrod

    Application server configuration confusion

    mafor

      I have scanned the forums and the web for information on this but haven't found adequate information. If I simply missed some wiki page somewhere please let me know.

      1. What version of JBR is included in JBoss AS 4.0.3RC1?

      2. Is it possible to run AS4.0.3RC1/EJB3 with only JBR 1.2.0, i.e. replacing the old transport stack? If it is, please give some hints on how to do this.

      Sorry if I missed something obvious.

      Thanks!

        • 1. Re: Application server configuration confusion
          • 2. Re: Application server configuration confusion
            mafor

            Thanks Tom for the link. It seems though to be an older version included in RC1 since it has no SSL support.

            I have written a simple JBR server invocation handler that invokes an arbitrary method on an arbitrary EJB. Is this in line with the intended design if you want the clients to use JBR only? Is there any gotchas with this approach? Also, the old UnifiedInvoker seems to be only a bridge between the old transports and JBR. Is there any design document available regarding this or is it an open issue?

            • 3. Re: Application server configuration confusion

              Is certainly fine to use remoting as transport for making remote calls on EJBs indirectly. Just wondering what the reason would be for this? Will cut out all the EJB logic on the client side, such as adding transaction context, principal/credential, etc.

              You are right about the UnifiedInvoker really just being an adapter between the old way of using invokers and using remoting. There is still work being done this, but should be completed soon (although will work as is and is the default invoker in HEAD). Only current doc on this is at http://wiki.jboss.org/wiki/Wiki.jsp?page=Unified_Invoker_configuration.


              • 4. Re: Application server configuration confusion
                mafor

                Thanks for the clarification. The reason I want to use JBR directly on the client is to be able to hook up non-Java clients using a lightweight non-IIOP protocol. The server side client dispatcher (i.e. the server invoker handler) will have to deal with the tx context/principals in some way.

                It would be great if you could sched some light on any plans you have using JBR on the client side in JBoss AS.

                • 5. Re: Application server configuration confusion

                  Hmm. Not sure how much light I'll be able to shed on that in particular. I know that we have a UnifiedInvokerProxy that uses remoting to make ejb calls from the client side. The new web services implementation uses remoting to make web services calls from the client. Nothing that I know of specifically being used for fat clients that use remoting to talk to the server.