[
https://issues.apache.org/jira/browse/QPID-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934179#comment-16934179
]
ASF GitHub Bot commented on QPID-8361:
--------------------------------------
vavrtom commented on pull request #36: QPID-8361: [Broker-J] Create a developer
guide for Qpid Broker-J
URL: https://github.com/apache/qpid-broker-j/pull/36#discussion_r326506479
##########
File path: doc/developer-guide/src/main/markdown/architecture.md
##########
@@ -544,3 +545,49 @@ other attributes. For example, `PortFactory` examines
attribute `protocols` to i
The Broker allows alternative implementations for various entities. For
example, alternative implementations for
`ProtocolEngine`, `MessageConverter`, `MessageFormat`, etc can be plugged into
the `Broker`. Please, check Broker code
for all extension points by building type hierarchy for `Pluggable`.
+
+## Logging
+
+Qpid Broker-J use **slf4j** API for logging. The **slf4j** abstraction allows
to plug-in any logging framework.
+The logback logging framework is used by the broker. However, it is optional.
Any other framework can be used with
+the Broker if required.
+
+`VirtualHost` logs can be segregated from other `VirtualHost` and `Broker`
logs in order to isolate applications
+on dedicated VirtualHosts from each other. Thus, specific `VirtualHost` users
would be able to access their logs
+without seeing Broker logs not related to the `VirtualHost` or logs from other
applications on different VirtualHosts.
+
+The Broker defines a number of `ConfigutredObject` categories to be able to
dynamically configure logging settings
Review comment:
Typo in 'ConfigutredObject'
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Broker-J] Create a developer guide for Qpid Broker-J
> -----------------------------------------------------
>
> Key: QPID-8361
> URL: https://issues.apache.org/jira/browse/QPID-8361
> Project: Qpid
> Issue Type: Task
> Components: Broker-J
> Reporter: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-8.0.0
>
>
> The developer documentation is currently scattered over various Qpid
> confluence pages. It could be challenging for people interested in
> contributing to the project to find that documentation. A developer guide
> could be added to cover such aspects as
> * Environment Setup
> * Building project
> * Running tests
> * Releasing
> * Architecture overview
> The following wiki pages are good candidates for inclusion into a developer
> guide:
> [High Level
> Architecture|https://cwiki.apache.org/confluence/display/qpid/High+Level+Architecture]
> [How To Build Qpid
> Broker-J|https://cwiki.apache.org/confluence/display/qpid/How+To+Build+Qpid+Broker-J]
> [Releasing Qpid
> Broker-J|https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J]
> The wiki pages below might be included as well
> [Java Coding
> Standards|https://cwiki.apache.org/confluence/display/qpid/Java+Coding+Standards]
> [Qpid Java Run
> Scripts|https://cwiki.apache.org/confluence/display/qpid/Qpid+Java+Run+Scripts]
> The developer documentation should be easy to modify, maintain and preview.
> Thus, it can be written in markdown or
> [asciidoc|https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/]. The
> latter is also supported on github.
> Potentially, it can be published on Qpid project site as part of release
> process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
