David Jencks wrote: >>Could work, but I'd rather do something portable. Plus, it's non-trivial >>to break up our app (it's rather monolithic). Plus, several EAR's -> >>several web deployments -> several web contexts -> no session sharing -> >>no good. >> > > You're talking about a non-portable development environment anyway aren't > you? Putting pieces of your 1500 jsps in different files might not be so > hard???
Yes, I am talking about non-portable development environment. When I'm done, I package an EAR anyway. And no, again, splitting the app into multiple WAR's is Not An Option. > ??????? > Are you proposing to change a copy of the source for the jsp rather than > the source?? That's what I thought *you* meant... which would be dumb.. > Cmon, you change your jsp in src, deployment of change consists of copying > changed file to temp deployment directory?? That's much better, assuming I know where the tmp directory is. And I don't, since the name keeps changing for each deployment. :-( > You rebuild from source, you > pick up the changes. Only problem I see is automatically finding the > correct tmp deploy directory again after redeployment of the whole ear. Exactly. Paaain.. /R -- Rickard Öberg _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
