anonymous wrote :
| Yes Jason it is working fine but.....
|
| Actually the stack trace is printed twice.
| The first one is from a log instance in the PortProxy class.
| This is the listing in the first message of this topic.
|
| The second one is from my own try and catch block.
| And it is caught in : } catch (FacadeException e) {
|
| So the Logger in PortProxy is informing me that something went wrong.
| At this moment I don't know if I can disable the output from the Logger on
my console. Thomas did used the Logger for some good reason?
| So disabling the output is maybe not a good idea?
|
| Johan.
|
I agree that the log level is too high, it should probably be debug, or at
least warn. As a workaround, you can just make a log4j.properties or
log4j.xml file that filters log messages from that class.
The snippet to log4j.xml would look like this:
| <category name="org.jboss.webservice.client.PortProxy">
| <priority value="OFF"/>
| </category>
|
The snippet to log4j.properties would like this:
| log4j.category.org.jboss.webservice.client.PortProxy=OFF
|
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858571#3858571
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858571
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
