nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Editing live JSPs on Dev Box

System

Hey guys,

I'm doing a lot of jsp development, and as I'm new to some of the technologies (and can't use EL), I'm restarting, alot. Each restart is pretty lengthy, as we all know.

What I'm wondering is how I might go about editing the live JSP so that it's picked up and changes without a full rebuild.

I know that I'll have to replicate changes back to livesite_customer_src before rebuilding, and that this would be horrible practice on a production server, but I'm okay with both those things.

What I'm not okay with is waiting 5 minutes to see a change on a JSP because I forgot a semicolon.

Edit: I've already tried simply modifying the .jsp files from within iw-cc.war/WEB-INF all to no avail.

Find more posts tagged with

Comments

Rick Poulin

Edit: I've already tried simply modifying the .jsp files from within iw-cc.war/WEB-INF all to no avail.

That's because JSPs are only ever compiled the first time they're accessed. After you make your changes, you need to delete the equivalent compiled .class file from JBoss' "work" folder. It'll more or less have the name of your jsp with a _jsp.class extension and possibly some random number. When that file no longer exists, the next HTTP call will cause JBoss to recompile from source.

Migrateduser

Ahhh, okay, so it's a really rudimentary caching system. When a request is made, it checks for a compiled version of the JSP, and when it doesn't find it, it makes one.

That makes a ton of sense. thanks for the help!