Thursday, 15 September 2011

jsp for business layer -


Why should not we use JSP for business layer?

Is this demonstration? Or is it just a good practice? Absolutely rationality is a reason. Apart from this, is there any killer reason that we should use JSP for the commercial layer?

itemprop = "text">

  1. Reusability: You can not reuse the scriptlet.
  2. Replacement: You can not make scripts abstract.
  3. O-Capability: You can not use inheritance / structure.
  4. Debugability: If the scriptlet throws exceptions on halfway, you get a blank page.
  5. Test Qualification: The scripts units are not maintenance.
  6. Maintenance: More time is needed to maintain perpetual / annoyance code logic.

is more, strong> bad behavior

You can do a lot at the presentation level with it. If you come to a point that it is not possible with any of them and you have been forced to catch skiplets, then code logic finally comes under an real java class. You can use classes to control the class / preprocess / postprocess Vinyl, you can use a class to filter requests, you can use a class for database interaction You can use a class to store / transfer / access data, for business logic, the domain class, a utility class for the stable device You can use.


No comments:

Post a Comment