S
Scorpio
Hi folks,
i'm currently developing a distribuited server application, accessible via
standard browser... I'm using Servlet, JSP and some architectural classes of
my own...
For sharing some resources (obviously, concurrency is managed), like token
generators or decoder, I use static instances in some business-logic
classes. This works, but I was suggested it's not a best-practice.
So, I'd like to know:
1) why it's not a good practice, and what are the risks can occour;
2) if a possible solution it's using JNDI API, to put and get resources in
application server context.
Thanx in advance,
Scorpio.
i'm currently developing a distribuited server application, accessible via
standard browser... I'm using Servlet, JSP and some architectural classes of
my own...
For sharing some resources (obviously, concurrency is managed), like token
generators or decoder, I use static instances in some business-logic
classes. This works, but I was suggested it's not a best-practice.
So, I'd like to know:
1) why it's not a good practice, and what are the risks can occour;
2) if a possible solution it's using JNDI API, to put and get resources in
application server context.
Thanx in advance,
Scorpio.