search

Letractively / owasp-esapi-java

Automatically exported from code.google.com/p/owasp-esapi-java
Other
0 stars 0 forks source link

New XML config and config management needed #154

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
XML-Validation is a good thing but only part of the story.
It would be cool if there was an additional test that checked the configuration 
for dependencies.
For example if you have a reference to a class, it would check if the class 
exists and this before you launch the application server.

Another thing that would be cool would be to split HTTPUtilities.
A quick look at the documentation shows that this interface is a case of 
excessive SRP* violation...

 * The HTTPUtilities interface is a collection of methods that provide additional security related to HTTP requests,
 * responses, sessions, cookies, headers, and logging.

-Sebastian Kübeck

* The Single Responsibility Principle is one
  of the oldest and most respected design principles...

http://www.objectmentor.com/resources/articles/srp.pdf

Original issue reported on code.google.com by manico.james@gmail.com on 29 Sep 2010 at 6:35

GoogleCodeExporter commented 9 years ago 
I agree with this 100%. I'd like to do this before 2.0

Original comment by manico.james@gmail.com on 2 Nov 2010 at 7:52

GoogleCodeExporter commented 9 years ago 
and PS: Ignore the top section, please only consider the following for this bug:

Another thing that would be cool would be to split HTTPUtilities.
A quick look at the documentation shows that this interface is a case of 
excessive SRP* violation...

 * The HTTPUtilities interface is a collection of methods that provide additional security related to HTTP requests,
 * responses, sessions, cookies, headers, and logging.

-Sebastian Kübeck

* The Single Responsibility Principle is one
  of the oldest and most respected design principles...

http://www.objectmentor.com/resources/articles/srp.pdf

Original comment by manico.james@gmail.com on 2 Nov 2010 at 7:53

GoogleCodeExporter commented 9 years ago 
This issue would then seem to be duplicated in issue #172.

172 is tagged with a different milestone.

Original comment by brent.sh...@gmail.com on 7 Nov 2010 at 3:57

GoogleCodeExporter commented 9 years ago 
This is different than 172, but I still bumped this milestone up to 2.1

Original comment by manico.james@gmail.com on 19 Nov 2010 at 2:37

GoogleCodeExporter commented 9 years ago

Original comment by manico.james@gmail.com on 19 Nov 2010 at 2:37

GoogleCodeExporter commented 9 years ago

Original comment by manico.james@gmail.com on 29 May 2012 at 3:24