[jira] [Updated] (ISIS-748) Improve the way we setup logging to vary between prod and test, and independent of viewer.

2014-09-26 Thread Jeroen van der Wal (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeroen van der Wal updated ISIS-748:

Fix Version/s: (was: viewer-wicket-1.7.0)
   (was: core-1.7.0)
   core-2.0.0

 Improve the way we setup logging to vary between prod and test, and 
 independent of viewer.
 --

 Key: ISIS-748
 URL: https://issues.apache.org/jira/browse/ISIS-748
 Project: Isis
  Issue Type: Improvement
  Components: Core, Viewer: Wicket
Affects Versions: viewer-wicket-1.4.1, core-1.4.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
 Fix For: core-2.0.0


 There is very similar code in both IsisWebAppBootstrapper and the 
 IsisWicketApplication, using IsisLoggingConfigurer.  This should be factored 
 out into something reusable by both, as a context initlaizer (global webapp 
 scope).
 Then, in both cases let the logging.properties be picked up from some other 
 directory outside of WEB-INF.
 ~~~
 UPDATE: it seems that specifying log4j.configuration seems to override this 
 already???
 /usr/lib/jvm/java-7-openjdk-amd64/bin/java 
 -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties 
 -Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms128m -Xmx768m 
 -XX:PermSize=64m -XX:MaxPermSize=256m -XX:+DisableExplicitGC 
 -Dlog4j.configuration=/etc/tomcat7/estatio/logging.properties 
 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
 -Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath 
 /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar 
 -Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 
 -Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp 
 org.apache.catalina.startup.Bootstrap start



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ISIS-748) Improve the way we setup logging to vary between prod and test, and independent of viewer.

2014-03-18 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood updated ISIS-748:
-

Fix Version/s: (was: viewer-wicket-1.4.2)
   (was: core-1.4.2)
   core-1.6.0
   viewer-wicket-1.6.0

 Improve the way we setup logging to vary between prod and test, and 
 independent of viewer.
 --

 Key: ISIS-748
 URL: https://issues.apache.org/jira/browse/ISIS-748
 Project: Isis
  Issue Type: Improvement
  Components: Core, Viewer: Wicket
Affects Versions: viewer-wicket-1.4.1, core-1.4.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
 Fix For: viewer-wicket-1.6.0, core-1.6.0


 There is very similar code in both IsisWebAppBootstrapper and the 
 IsisWicketApplication, using IsisLoggingConfigurer.  This should be factored 
 out into something reusable by both, as a context initlaizer (global webapp 
 scope).
 Then, in both cases let the logging.properties be picked up from some other 
 directory outside of WEB-INF.
 ~~~
 UPDATE: it seems that specifying log4j.configuration seems to override this 
 already???
 /usr/lib/jvm/java-7-openjdk-amd64/bin/java 
 -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties 
 -Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms128m -Xmx768m 
 -XX:PermSize=64m -XX:MaxPermSize=256m -XX:+DisableExplicitGC 
 -Dlog4j.configuration=/etc/tomcat7/estatio/logging.properties 
 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
 -Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath 
 /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar 
 -Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 
 -Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp 
 org.apache.catalina.startup.Bootstrap start



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (ISIS-748) Improve the way we setup logging to vary between prod and test, and independent of viewer.

2014-03-17 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood updated ISIS-748:
-

Description: 
There is very similar code in both IsisWebAppBootstrapper and the 
IsisWicketApplication, using IsisLoggingConfigurer.  This should be factored 
out into something reusable by both, as a context initlaizer (global webapp 
scope).

Then, in both cases let the logging.properties be picked up from some other 
directory outside of WEB-INF.

~~~
UPDATE: it seems that specifying log4j.configuration seems to override this 
already???

/usr/lib/jvm/java-7-openjdk-amd64/bin/java 
-Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties 
-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms128m -Xmx768m 
-XX:PermSize=64m -XX:MaxPermSize=256m -XX:+DisableExplicitGC 
-Dlog4j.configuration=/etc/tomcat7/estatio/logging.properties 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath 
/usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar 
-Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 
-Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp org.apache.catalina.startup.Bootstrap 
start



  was:
There is very similar code in both IsisWebAppBootstrapper and the 
IsisWicketApplication, using IsisLoggingConfigurer.  This should be factored 
out into something reusable by both, as a context initlaizer (global webapp 
scope).

Then, in both cases let the logging.properties be picked up from some other 
directory outside of WEB-INF.



 Improve the way we setup logging to vary between prod and test, and 
 independent of viewer.
 --

 Key: ISIS-748
 URL: https://issues.apache.org/jira/browse/ISIS-748
 Project: Isis
  Issue Type: Improvement
  Components: Core, Viewer: Wicket
Affects Versions: viewer-wicket-1.4.1, core-1.4.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
 Fix For: viewer-wicket-1.5.0, core-1.5.0


 There is very similar code in both IsisWebAppBootstrapper and the 
 IsisWicketApplication, using IsisLoggingConfigurer.  This should be factored 
 out into something reusable by both, as a context initlaizer (global webapp 
 scope).
 Then, in both cases let the logging.properties be picked up from some other 
 directory outside of WEB-INF.
 ~~~
 UPDATE: it seems that specifying log4j.configuration seems to override this 
 already???
 /usr/lib/jvm/java-7-openjdk-amd64/bin/java 
 -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties 
 -Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms128m -Xmx768m 
 -XX:PermSize=64m -XX:MaxPermSize=256m -XX:+DisableExplicitGC 
 -Dlog4j.configuration=/etc/tomcat7/estatio/logging.properties 
 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
 -Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath 
 /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar 
 -Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 
 -Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp 
 org.apache.catalina.startup.Bootstrap start



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (ISIS-748) Improve the way we setup logging to vary between prod and test, and independent of viewer.

2014-03-17 Thread Dan Haywood (JIRA)

 [ 
https://issues.apache.org/jira/browse/ISIS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Haywood updated ISIS-748:
-

Fix Version/s: (was: viewer-wicket-1.5.0)
   (was: core-1.5.0)
   core-1.4.2
   viewer-wicket-1.4.2

 Improve the way we setup logging to vary between prod and test, and 
 independent of viewer.
 --

 Key: ISIS-748
 URL: https://issues.apache.org/jira/browse/ISIS-748
 Project: Isis
  Issue Type: Improvement
  Components: Core, Viewer: Wicket
Affects Versions: viewer-wicket-1.4.1, core-1.4.0
Reporter: Dan Haywood
Assignee: Dan Haywood
Priority: Minor
 Fix For: viewer-wicket-1.4.2, core-1.4.2


 There is very similar code in both IsisWebAppBootstrapper and the 
 IsisWicketApplication, using IsisLoggingConfigurer.  This should be factored 
 out into something reusable by both, as a context initlaizer (global webapp 
 scope).
 Then, in both cases let the logging.properties be picked up from some other 
 directory outside of WEB-INF.
 ~~~
 UPDATE: it seems that specifying log4j.configuration seems to override this 
 already???
 /usr/lib/jvm/java-7-openjdk-amd64/bin/java 
 -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties 
 -Djava.awt.headless=true -Dfile.encoding=UTF-8 -server -Xms128m -Xmx768m 
 -XX:PermSize=64m -XX:MaxPermSize=256m -XX:+DisableExplicitGC 
 -Dlog4j.configuration=/etc/tomcat7/estatio/logging.properties 
 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
 -Djava.endorsed.dirs=/usr/share/tomcat7/endorsed -classpath 
 /usr/share/tomcat7/bin/bootstrap.jar:/usr/share/tomcat7/bin/tomcat-juli.jar 
 -Dcatalina.base=/var/lib/tomcat7 -Dcatalina.home=/usr/share/tomcat7 
 -Djava.io.tmpdir=/tmp/tomcat7-tomcat7-tmp 
 org.apache.catalina.startup.Bootstrap start



--
This message was sent by Atlassian JIRA
(v6.2#6252)