At the time I didn't find any fix to this problem and since I later implemented
the solution using a different approach, I didn't bother finding out if it has
been fixed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200497#4200497
Reply to the post :
http
Apperently, it doesn't work when you specify the allowLinking attribute to the
default context. You need to define a seperate context for you application and
specify it there. It should work just fine.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041787#404
Even better, instead of creating a seperate context for your application, add
the "allowLinking" attribute to the Context element in the context.xml file in
the Tomcat directory.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041806#4041806
Reply to the post
I have a problem using a custom pattern in the AccessLogValve. JBoss simply
ignores it and defaults to the "common" pattrn. I even tried using a simple
pattern e.g. only "%t" just to be sure that I'm not using illegal pattern codes.
I'm using JBoss version 4.0.5GA on a Linux platform.
View the
I need to create a custom access log valve similar to the
FastCommonAccessLogValve which I guess is the default one used in Tomcat. The
difference is that I want to output to more than one different log files
depending on the value of a session object.
The application for which the Valve will b
