Skip to main content
Did you ever wonder if you can have 2 servlets.xml files?

My new employer uses a machine generated servlets.xml. I'm not sure why someone thought that was a win, but whatever. My new part of the application is being rapidly developed and I didn't want to have to regen the servlets.xml file whever I added something, nor did I want to manually edit a file that says at the top "DO NOT EDIT BY HAND" (even though I did at first).

My solution was to add an entity to the web.xml

So

<!DOCTYPE web-app [

    <!ENTITY servlets SYSTEM "servlets.xml">

]>


Became

<!DOCTYPE web-app [

    <!ENTITY servlets SYSTEM "servlets.xml">

    <!ENTITY objectServlets SYSTEM "objectServlets.xml">

]>



And then futher into web.xml


&servlets;

became

&servlets;
&objectServlets;

And of course I made the objectServlets.xml file in the same dir and format as servlets.xml
Labels:

Comments

Post a Comment

Popular posts from this blog

Preventing accidental large deletes.

Instructions for Developers on Using the safe_delete Stored Procedure To enhance safety and auditability of delete operations within our databases, we have implemented a controlled deletion process using a stored procedure named safe_delete . This procedure relies on a temporary table ( temp_delete_table ) that lists complete records intended for deletion, not just their IDs. This approach helps prevent accidental deletions and provides a traceable audit log of delete actions. Why We Are Doing This Controlled Deletions : Centralizing delete operations through a stored procedure reduces the risk of erroneous or unauthorized deletions. Auditability : Using a temporary table to store complete records before deletion allows for an in-depth review and verification process, enhancing our ability to confirm and audit delete operations accurately. Security : Restricting direct delete permissions and channeling deletions through a specific proced...
Post a Comment
Read more
 In software engineering, accumulating code behind a release wall is akin to gathering water behind a dam. Just as a dam must be built higher and stronger to contain an increasing volume of water, the more code we delay releasing, the more resources we must allocate to prevent a catastrophic flood—major bugs or system failures—while also managing the inevitable trickles—minor issues and defects. Frequent, smaller releases act like controlled spillways, effectively managing the flow of updates and reducing the risk of overwhelming both the system and the team. The ideal of ci/cd may not be achievable for all teams, but smaller and faster is always better.
Post a Comment
Read more

October is Cyber Security Month

The President has declared October as Cybersecurity month.  It's not a bad idea -- just like you change the batteries in your smoke detectors once a year, maybe you should review your electronic vulbnerabilities? My top ten security tips: 1) Change your passwords.  You've had them too long, you use the same password in too many places.  Somewhere someone has hacked a site that has your username and password in plain text.  Now they are getting ready to try that username/password somewhere else.  Beat them to the punch. 2) Use a safe browser.  That means anything that's not Internet Explorer.   I prefer chrome. 3) Use 2 step verification for your email account.  If your email doesn't provide 2 step authentication consider switching. 4) Get a free credit report  and review it.  You are entitled to one free report a year.   BE VERY CAREFUL!  There are man scam sites that offer free credit reports.  Go through the s...
16 comments
Read more