-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 "Arthur D'Alessandro III" <[EMAIL PROTECTED]> writes:
> references from the default context. Now that we're trying to move to a jsp > form action handler framework, questions have arisen as to where those > variables should be initialized. It is my understanding that the logic, and I do not know how to use JSP within Jetspeed as I have been using Velocity. One thing I do know is, as you have multiple portlets communicating with each other, there is a need for a Singleton entity that at least acts as the communication bus between portlets. The sanctioned way of doing a singleton is to create a TurbineService: http://jakarta.apache.org/turbine/turbine-2.3/howto/services-howto.html You can also use a Service to store your business logic (get customer list, update customer, save purchases, etc). That business logic service may, in turn, make use of other backends that actually do the database access (like Hibernate, torque, etc). This way, there is no direct access from JSP to the database, which is good, since it layers things properly. The UI guys concern themselves only with the business logic, and the backend guys concern themselves only with how to access the database. > initializes once. Does anyone have any best practices for where the > database logic should be defined, and how to do so with the least amount of > overall overhead. Well, minimising the overhead means removing the layers. It is your call whether to allow the UI guys direct access to the dbase or not. YS -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iEYEARECAAYFAkDmgS4ACgkQ/G3tTyzWJhX7LACffZyuAUrhV5lByd9zBg8og4O2 +YIAmwfPQr/uzKLDXNmzMMgjICbVWlB8 =fDVQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
