1 Reply Latest reply on Oct 2, 2002 9:48 PM by Juha Lindfors

    JBoss compliance with J2EE application clients

    Volkmar Newbie

      Hi all,

      I've already posted a few questions on this(in sheer desperation ;) but I am only getting closer to finding answers ever-so-slowly.
      Firstly, it seems to me that non-web clients to J2EE applications are going out of fashion fast. This is evidenced by the fact that just about EVERY tutorial from just about ANY vendor assumes you want to build some web-based whatever. Well, I don't. And thats probably half my problem; I have built a Swing/AWT client, that's supposed to run in the application server and be accessed remotely by the workstations.
      Now, I may be mistaken, but according to SUNs documentation [http://java.sun.com/j2ee/sdk_1.2.1/techdocs/guides/ejb/html/Client3.html#13349]
      it should be possible to port my application to JBoss by just changing the deployment descriptors, right ?!?
      Well, appearantly this is not so. At least not according to the answers I've gotten to my questions so far.
      So all I want to know is this:
      Can JBoss run a Swing/AWT (in other words, N-O-T web-based) client the way it is described in SUNs documentation ? Or do I have to turn it into a standalone Java application that interacts with JBoss ?
      [If that is the case, then how do I handle Authentication and Transactions ?!?]
      I am grateful for any hints that can shed some light on this, because at the moment, what little info I've looked at has been confusing and incomplete.

      Thanks a lot,

      Volkmar