Portlet Factory, Version 6.1.2

---

 

About using built-in logging in Web Service Call and SQL Call builders

The Web Service Call and SQL Call builders connect to resources outside of your working model. Therefore, it is useful in development to be able to log the events that occur within these builders to ensure that the data from the resources is being accessed correctly. Before looking for an error in your model, determine that the builders are acquiring valid data from the resource. The logging feature in these builders allows you to log the communication between the model and the data resource.

Web Service Call and SQL Call builders write their output to the debugTracing.txt log located in the ...\wpf.war\WEB-INF\logs directory.

For the Web Service Call builder, the log4j features will log the initial call of the model associated with the Web Service Call builder. It would then log the web service call request with argument name, type and value followed by the response, if any, with the same type information that was logged in the request. With each log entry in the debugTracing.txt is the Time/Date, Category, Priority, Thread, and the Message.

A typical log entry might look as follows:

Example of a request:

*-- TIME: [2004-08-26 11:36:25,061] --* Category: bowstreet.system.debugTracing Priority: INFO Thread: http-8080-Processor3 Msg: ServiceCall: arg name=registrationInfo class=com.bowstreet.util.IXml val=<RegistrationRequest xmlns="http://bowstreet.com/registrationinfo"><userName>johnDoe</userName>
<firstName>John</firstName>
<lastName>Doe</lastName>
<address1>200 Ames Pond Drive</address1>
<address2>Suite 200</address2>
<city>Tewks</city>
<state>MA</state>
<zip>02155</zip>
<phone>9788631500</phone>
<email>johnD@bowstreet.com</email>
<isBusiness>true</isBusiness>
</RegistrationRequest>

Parent topic: Overview: application logging Parent topic: Logging application behavior

---

Library | Support |