• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

EJB Development

 
Ranch Hand
Posts: 132
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I am a student learning EJB.I would like to develop an application that records and monitors loans taken by people as a learning project.Those who fail to pay are blacklisted and can not get loans. People should be able to check their status but not anyone else's. Please give me guidelines, I am new to EJB.
 
Ranch Hand
Posts: 704
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Patrick,

I try to understand your project requirements. It looks to me like you need to maintain a database of users that take loans. The question is do you need to implement logic for deciding if a client is eligible for a loan? What I mean is kind of credit score that could go from poor to very good, etc. Based on that your application can decide if the client is eligible for the loan and what kind of rates s/he could get. If this kind of logic is part of your requirements as well, then your application could become little bit more complex. The second question is this: do you intend to allow your clients to pay the loan on line, using probably a credit card or other electronically payment methods? Or they only can see their account and their transactions history.
Regards.
 
Patrick Mugabe
Ranch Hand
Posts: 132
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Valentin.

Thanks for your response. well since I am learning I don't want to make it so complex. I don't want people to pay loans on line but for them to be able to see their status, i.e. whether or not they are blacklisted and by who.
I want to maintain a database of users that take loansand I would want to implement logic for deciding if a client is eligible for a loan?
I hope this answers your question. I hope you will be able to assist me further.
Thanks
 
Valentin Tanase
Ranch Hand
Posts: 704
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well to make things easier we shall agree that your systems is only implementing a very basic loan system that allows users to check their status online. They can check their transactions history as well as the overall credit score and they could also receive promotional offers from the same financial institution. Your application is not responsible to update the database with loan specific data, like payments, credit score information, etc and we shall agree that there is another external system that does all these operations (you might run a set of sql to do this manually). Your application however is capable to update and maintain user�s profile information, like address, phone numbers, ssn, first name, last name, etc.
If you do agree with this limited set of ad-hoc requirements, I�ll have to ask you to start with the beginning: design your data model. Please identify the data structures that you need to use and come up with your data model, mostly like a set of tables in the database and we shall see from there. I�ll mostly help you implementing the business logic and probably we�d like to use entity ejbs for mapping to your data model (just for the sake of exercise) and a session fa�ade pattern. You�d also like using code generation tools like XDoclet or ejbgen for simplifying the ejb development. There are several design strategies that you�d like to employee, like using service locator or value objects paradigms, etc.
Regards.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic