[
https://issues.apache.org/jira/browse/QPID-7550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760850#comment-15760850
]
Keith Wall commented on QPID-7550:
----------------------------------
The metadata does not change at run time. The WMC loads it once at startup.
The issue strikes when adding a dependency JARs to the Broker's classpath to
enable an optional plugin (for instance BDB). If the user had a previous WMC
session open in a Browser, then stops the Broker, adds the dependency JAR and
restarts, on refreshing the WMC, the Browser might use the cached (now stale)
version of the metadata. This may lead the user to believe he had installed
the JAR incorrectly.
> Metadata service does not set cache control headers
> ---------------------------------------------------
>
> Key: QPID-7550
> URL: https://issues.apache.org/jira/browse/QPID-7550
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: qpid-java-6.2
>
>
> The metadata service does not set cache control headers, it should.
> Especially in IE the WMC would frequently show me stale picklists.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
