I think it is possible. You can have a fat client talk to the Action servlet
all the time and the Action Servlet forwards the response to the fat client
all the time. this way you can use the struts architecture. I don't have
experience with this but i think this will involve designing your client in
such a way that it always sends information based on the mappings in the
struts-config.xml
In a web client, you post info to a servlet and you map each and every
response to some action in the struts-config.xml. Similarly when you post
information from your fat client you will also have to do the same thing. I
think the java.net package will help you more on how to do this ( i believe
i have done something similar before ). Hope this helps (or) start a lengthy
thread on how to do this :)
cheers,
Amar..
-----Original Message-----
From: Michelle Popovits [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 29, 2001 9:48 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Non-Web-based Application with STRUTS
Andy,
Perhaps you could create your application as an EJB application where the
application state, business logic, data access are all managed by the EJB
tier. Create a set of workflow 'Session Facade' session ejb's to be your
interface between your various clients and your ejb business tier. Also,
create a Business Delegate class which your java client classes will use to
communicate with the EJB tier (this will abstract the logic of ejb lookup
from the client/presentation logic).
Then you code your front ends to this EJB application:
1) a struts/jsp application that calls the ejb 'Session Facade' objects via
the business delegate.
2) a Java application that calls the ejb 'Session Facade' objects via the
business delegate.
3) if you are using a non-java client, then you may be able to access your
ejb layer using xml/rpc (web services).
In order for this multi-client approach to work, you may have to keep model
information that you would normally keep in the users HttpSession in the
workflow ('Session Facade') objects (otherwise you duplicate this logic in
the client.
When the application is developed this way, then the front-end applications
are simply used for view and to some degree flow of control.
See the J2EE Patterns catalog for more information on the design patterns I
mentioned above (Session Facade, Business Delegate, etc.) at
http://developer.java.sun.com/developer/restricted/patterns/J2EEPatternsAtAG
lance.html
HTH,
Michelle
----- Original Message -----
From: "Andreas Dejung" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 29, 2001 9:20 AM
Subject: Non-Web-based Application with STRUTS
> Hi there
>
> I have done some prototyp with Struts.
> Now a new requirement is that the application runs not only with a
Broser.
> It should also run with a fat java client.
>
> Has somebody experiences with this?
>
> Is it possible? and if yes, with what kind of architecture?
>
>
> I very intressted in your answer
>
>
> Andy
>
>
>
>
>
>
> ******************* PLEASE NOTE *******************
> This message, along with any attachments, may be confidential or legally
> privileged. It is intended only for the named person(s), who is/are the
> only authorized recipients. If this message has reached you in error,
> kindly destroy it without review and notify the sender immediately. Thank
> you for your help.
> **********************************************************
