[
https://issues.apache.org/jira/browse/QPID-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644086#action_12644086
]
Andrea Gazzarini commented on QPID-1411:
----------------------------------------
Another thing : I removed the log4j configuration file too. I mean : it is no
longer included in qman bndle because :
a) if you are running QMan standalone you can put your log4j configuration file
under an external directory and set that folder on classpath;
b) if you are running QMan on JBoss (or another AS) the log configuration file
of the Application Server is used for Qman logging; In JBoss for example you
can find it under $JBOSS_HOME/server/<default | all minimal>/conf
Regards,
Andrea
> Simplify QMan configuration
> ----------------------------
>
> Key: QPID-1411
> URL: https://issues.apache.org/jira/browse/QPID-1411
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tools
> Affects Versions: M4
> Reporter: Arnaud Simon
> Fix For: M4
>
>
> Currently QMan is configured through a an xml file "config.xml" that must be
> located in src\main\java\org\apache\qpid\management. This configuration file
> is use for defining the type mappings and the brokers.
> I would suggest that we do the following
> - As default QMan does not connect to any broker
> - The type mappings are part of the code
> - Brokers can be configured via a VM parameter "qman-config" pointing on a
> xml file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
