Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 491
  • Last Modified:

How to restrict method access outside of jar or set of packages

Hi all
I have a base class – WebContainer from which I derive two classes, Request class and Response class.
WebContainer is a like aMap and donate both get() and set() methods for both derived classes .
The entire project is packaged into a jar and distributed to other development teams.
The team's has no need of calling request.set(objId) or response.get(objId), they only use request.get(objId) and
All set() method usages are restricted to classes in the jar file (sevarel of packages) .
What I can do is declare the request.set , and response.get methods as deprecated, so the teams will no not to use them ,
Is there any other way I can prevent them from accessing these methods?
Thank you
Sharon
0
sharon669
Asked:
sharon669
  • 4
  • 2
1 Solution
 
CEHJCommented:
Try installing a SecurityManager
0
 
objectsCommented:
best would be to declare them package protected, and put any of your classes that need them in the same package
0
 
objectsCommented:
if you just want to mark them then use deplecated

http://java.sun.com/j2se/1.4.2/docs/guide/misc/deprecation/deprecated.html
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
sharon669Author Commented:
objects  >>>  and put any of your classes that need them in the same package
The project is large scale entrprise application ,and  we commonly use the Request/Reponse objects in all packages ,

objects  >>>  if you just want to mark them then use deplecated
quote from the question :
>What I can do is declare the request.set , and response.get methods as deprecated, so ....
this way the programmers who develop the Jar will be bothered from the warning generated by the compiler .
isn't there any elegant solution ?

thank you for your time !
Sharon
0
 
objectsCommented:
> and  we commonly use the Request/Reponse objects in all packages

you can still use the objects, you just want to limit the visibility of those methods
0
 
sharon669Author Commented:
will SecurityManager cause significant overhead  to a large scale j2ee app ?
0
 
objectsCommented:
how would you use a security manager?
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now