-
Notifications
You must be signed in to change notification settings - Fork 10
FAQ
Chris Smith edited this page Dec 19, 2018
·
2 revisions
Q: I am having trouble running the samples, what can I do to debug them?
A: The following steps are generally useful for debugging the client/samples:
Ensure the prerequisites for the OpenDXL JavaClient have been met.
Switch the root logger from
infotodebugin thelog4j.propertiesfile located in thesamples/srcdirectory:log4j.rootLogger=info, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout # Pattern to output the caller's file name and line number. log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%nChange to:
log4j.rootLogger=debug, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout # Pattern to output the caller's file name and line number. log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
Data Exchange Layer (DXL) Overview
OpenDXL Java Client
Documentation
Main Classes
- DxlClient
- DxlClientConfig
- ServiceRegistrationInfo
- Messages
- Message (Base Class)
- Event
- Request
- Response
- ErrorResponse
- Callbacks
Examples