https://issues.jboss.org/browse/AS7-4296
On 18 October 2013 11:10, Martin Hoeller wrote:
> On 18 Okt 2013, Adrien Rivard wrote:
>
> > Most server allow you to externally override context-param without
> > modifying the war
>
> I can't find anything for JBoss 7, which is the application-server i
On 18 Okt 2013, Adrien Rivard wrote:
> Most server allow you to externally override context-param without
> modifying the war
I can't find anything for JBoss 7, which is the application-server i use.
If this is not possible, your suggestion doesn't work for me :(
> (which would be even worst tha
Most server allow you to externally override context-param without
modifying the war (which would be even worst than using profiles IMO)
see
http://tomcat.apache.org/tomcat-6.0-doc/config/context.html#Context_Parameters
for
tomcat
On Fri, Oct 18, 2013 at 10:45 AM, Martin Hoeller wrote:
> On 1
On 18 Okt 2013, Adrien Rivard wrote:
> You should just override the context-param when deploying on the real
> production server.
What do you mean by "override"?
You don't want me to extract the released WAR artifact (which is actually
included in an EAR), modify the web.xml and repackage it. Do
Hi,
You should just override the context-param when deploying on the real
production server.
On Fri, Oct 18, 2013 at 9:40 AM, Martin Hoeller wrote:
> Hi!
>
> Here is the short version of what I want: I've got a JEE6 webapp with a
> web.xml file, where the context-parameter facelets.DEVELOPME
Hi!
Here is the short version of what I want: I've got a JEE6 webapp with a
web.xml file, where the context-parameter facelets.DEVELOPMENT should be
enabled in development mode but disabled for releases.
My idea to solve this problem is as follows:
1) Define the context parameter in web.xml like
