[ 
https://issues.apache.org/jira/browse/QPID-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048484#comment-15048484
 ] 

ASF subversion and git services commented on QPID-6805:
-------------------------------------------------------

Commit 1718813 from [email protected] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1718813 ]

QPID-6805: [Java Broker Documentation] Replace REST API object table with link 
to /apidocs

Corrected a few other typos too and addressed some review comments from 
[email protected]
------------------------------------------------------------------------
Merged from trunk with command:
svn merge -c r1717626 https://svn.apache.org/repos/asf/qpid/java/trunk

> Update Broker/Client documentation with changes made  for v6
> ------------------------------------------------------------
>
>                 Key: QPID-6805
>                 URL: https://issues.apache.org/jira/browse/QPID-6805
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Lorenz Quack
>            Assignee: Keith Wall
>             Fix For: qpid-java-6.1
>
>         Attachments: update-windows-qpid-folder-content.diff
>
>
> The documentation must be checked to include all changes for v6:
> * Connection/Port/Virtiualhost remodelling
> * REST API changes
> * Thread pool handling for Ports (include both HTTP and AMQP), 
> * Port and virtual host settings for connection thread pools and give the 
> information the user needed to adjust these values sensibly.
> * PropertiesFileInitialContextFactory PROVIDER_URLs should now use the 
> file:// schema for local files.
> * ...?
> What has already been documented as part of other JIRAs
> * logging (QPID-6801)
> * memory usage (QPID-6802)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to