Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Originally posted by Kyle Brown:
You should put everything inside the WAR. The J2EE specification really tries to restrict visibility to what is within the WAR. You can add classes to the classpath of the WAR file by editing its manifest if the classes are in the EAR that contains the WAR, but trying to use external classpaths is really not recommended.
Kyle
P.S. If the USER is customizing things then each user might want it different. This should be stored on the session scope probably rather than the application scope. Also, do you want the cusstomizations to last past this particular user session? If so, you should consider storing this kind of information persistently, either in a long-lived cookie or in a database table.
Originally posted by Mike Curwen:
What about thinking 'less fancy' and just go for a simple style sheet that they can customize. It would be packaged up with everything else, but in your administrator's guide, you could say "to alter the look and feel of your site, change this file ..."
Bad assumption. Not all application servers run the application off the filesystem!Originally posted by Mike Curwen:
About the WAR file and CSS being inside. At some point, that WAR file will be expanded.
Peter den Haan | peterdenhaan.com | quantum computing specialist, Objectivity Ltd
CJP (Certifiable Java Programmer), AMSE (Anti-Microsoft Software Engineer)
Author of Posts in the Saloon
CJP (Certifiable Java Programmer), AMSE (Anti-Microsoft Software Engineer)
Author of Posts in the Saloon
This parrot is no more. It has ceased to be. Now it's a tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|