Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: markspace <-@.> Newsgroups: comp.lang.java.programmer Subject: Re: Dealing with application names in a JEE web app Date: Thu, 26 May 2011 12:51:28 -0700 Organization: A noiseless patient Spider Lines: 10 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Thu, 26 May 2011 19:51:39 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="vC/D6dGm0fSTzVD8lukD1w"; logging-data="6431"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18jUIKM+E6kvlb+6rtkDQgSIqfmkvA19Ho=" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 In-Reply-To: Cancel-Lock: sha1:MqAiRYvx/mK1PaFokBAu/ljae4U= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4609 On 5/26/2011 10:07 AM, Tom Anderson wrote: > > In which case it's not static CSS! Anything that gets mangled by code > before being served is dynamic, and is able to evade this problem. Well, true, I was just surprised that JSF was capable of taking a resource that looked like it should be static and treating it dynamically.