On 24 June 2011 12:00, Greg Akins <angryg...@gmail.com> wrote: >> On Fri, Jun 24, 2011 at 6:48 AM, Patrick McCourt <pa...@mc-court.com> wrote: >>> I’ve got 2 Struts 2 applications running on Tomcat 6.0. >>> >>> In summary the main application is a manager application for requests >>> in our company, application 2 is a handler for a specific request >>> type. >>> >>> I want to make a link to go to that application whilst keeping the >>> information from the session in the first. I've only started working >>> with Tomcat and Struts this week so I am completely lost on how to do >>> this. > > I think I need more details.. however, it sounds like you just need to > not think about integrating the two apps at the session level and > treat them like two different web applications. > > Use web services to send the requests from one app1 -> app2; then save > the responses in app1? > > In your case, maybe app2 can just be a web API (RESTful, or WS*) without any > UI. > > -- > Greg Akins > http://twitter.com/akinsgre > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
Okay this is what I've been asked to build: Blackboard tool link (All this will do is link to the application) The RequestsManager creates a new "Request" based on a user choice - (for example Copy a course from Blackboard year 2010-11 to year 2011-12) "Requests" are stored in a database, with a unique reference and user details plus the type of request. The RequestsManager then passes off to the 2nd application, a RequestHandler which will gather the details of the request, the reason this is external is they want to be able to add in new request types by simply building the struts for and deploying it rather than redeploying everything. The user is then presented with a form to gather the details (like which course to copy) the details of these are written back to a database and when the request has been approved, the college's batch systems will make the changes upon the next snapshot update. RequestsManager is then notified that the request is submitted and it send off a confirmation email. This basically automates hours of admin work. Since the RequestsHandler is the form for gathering the details I'm not sure that it could be a UI-less API. What RequestHandler needs to know from the RequestsManager is the primary key generated for the request and the user who is making the request, the rest it will get from the Struts2 form That's the general idea of the project by the end it will have 4 request types each with their own Struts2 form and if done right the flexibility to deploy the form of a new request type and in theory it should all work. Apologies if I've confused you more, Patrick --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
