I have a confusion about the re-usability of the 'Frequent Flyer' system. I wud like to know, what assumptions did u make about the system? According to the requirements, it cannot be re-written.
In fact, there are 2 prominent points:
1. While it is understandable that the Oracle database in the 'Frequent Flyer' system can be accessed by the Business Entities and DAO(s) of the new application, but how do u propose to reuse CGI & perl scripts?
2. Let's assume that we create links from the new j2ee application, to the pages of the 'Frequent Flyer' system. That would mean that the HttpSession established in the j2ee web-app, be carried over to the 'Frequent Flyer' web-app. This can be achieved by session replication techniques. However, the big qs is: if a Customer, after visiting the pages of the 'Frequent Flyer' web-app, wishes to return to the j2e web-app? To do this, we need to introduce links/buttons in the 'Frequent Flyer' web-app, which point to the j2ee web-app. But, as per requirements, the 'Frequent Flyer' system cannot be re-written!
Considering these issues, I am proposing that ONLY THE DATABASE from the 'Frequent Flyer' system will be reused, and NOT THE WEB COMPONENTS
Unfortunately I do not think this group can answer this question as it is a design decision which you must make for yourself. I woudl say the following though: There is rarely just one right solution so provided yours makes sense - go with it!
sorry I can't help more
keep an eye out for scorpions and black widows. But the tiny ads are safe.
Free, earth friendly heat - from the CodeRanch trailboss