[Tomcat, HTTPD, Servlets & JSP] - Loging in an Web ab (JSP) doesnt produce a log file
by MarcReis
I have a JSP which uses a java class as the client to the EJB's. This is the same client that I use in none web apps to invoke the EJB's.
For the "Fat" Client" the loging works, for the "Thin Client" it doesnt produce a "client.log" file.
This is all packed up in an ear, which is made up of an har, and jar for the jar with the ejbs and ofcourse a "war" for the web app.
I have a log4j.xml in the WEB-INF/classes folder. I do not have a log4j.jar in the WEB-INF/lib folder.
I checked the http://wiki.jboss.org/wiki/Wiki.jsp?page=Logging, but didnt pull out any think that seems to help me here.
Some snipits of the code.
log4j.xml
| ### direct log messages to stdout ###
| log4j.appender.stdout=org.apache.log4j.ConsoleAppender
| log4j.appender.stdout.Target=System.out
| log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
| log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{1}:%L - %m%n
|
| ### direct messages to file client.log ###
| log4j.appender.file=org.apache.log4j.FileAppender
| log4j.appender.file.File=client.log
| log4j.appender.file.layout=org.apache.log4j.PatternLayout
| log4j.appender.file.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{1}:%L - %m%n
|
| ### set log levels - for more verbose logging change 'info' to 'debug' ###
| log4j.rootLogger=warn, stdout, file
| ### Set the log level for de.mediacare.* that should be logged
| log4j.logger.de.somewhere=debug
|
The class doing the loging call (shortend to what I thought is important)
| ...
| import org.jboss.logging.Logger;
| ...
| private Logger log;
| ...
| if(doLogging){
| log= (log==null) ?getLogging() :log;
| log.debug(details);
| }
| ...
|
details is a String containing the info to be logged.
I debuged this part and all looks nice.
I'll be glad for any hints, tipps links :)
Thanks ahead!
Sincerely
Marc
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972237#3972237
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972237
19 years, 7 months
[JBoss Seam] - Re: AJAX4JSF: Problems with validation.
by bfo81
I finally found the solution (or let's say wcasatti from Exadel forum told me how to do it right):
With the a4j:region tag you can define which components shall be decoded during the JSF lifecycle. This is where the language barrier was a problem for me since didn't understand that "decode" meant "process" (but I think some native speakers didn't catch that either *g*).
So if define a a4j:region around the select menu 1 then only this single component is validated. That's what I wanted. But in order to create the output for the new menu 2 I need to set the attribute renderRegionOnly to "false", so that the other components are included in the AJAX response, too.
Well, here's the code:
| <a4j:region renderRegionOnly="false">
| <h:selectOneMenu id="menu1" value="..." required="true">
| <f:selectItems ... />
| <a4j:support event="onchange" reRender="menu2" />
| </h:selectOneMenu>
| </a4j:region>
|
| <h:selectOneMenu id="menu2" ....
| ....
PS: I think that the attribute ajaxSingle should be deprecated. It might leads to problems and a4j:region does it much better :).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972227#3972227
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972227
19 years, 7 months
[JBoss Eclipse IDE (users)] - Re: can't create a jboss configuration
by jfrohome
It seems jboss ide 1.5 and 1.6 are intended to be used with ecplise 3.1 and NOT with eclipse 3.2. documentation for jboss ide is overaged and neither their is documentation concerning installation jboss ide 1.6 or 2.0 beta nor there are any helpful information given by jboss which software prequesites are needed to run which jboss ide version.
@jboss: If you want your customer use your software at least there should be more information on how to install, what are software prequesites, what are dependencies on a specific eclipse version, and how to quick start use your NEW software version. Its make no sense to show availability of jboss ide 2.0 beta1 with BIG BANG on your website and customer have problems to install and get this stuff working WITH NO ACTUAL documentation for this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972218#3972218
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972218
19 years, 7 months