[
https://issues.apache.org/jira/browse/GSHELL-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670710#action_12670710
]
Guillaume Nodet commented on GSHELL-157:
----------------------------------------
Sending
gshell-support/gshell-vfs/src/main/java/org/apache/geronimo/gshell/vfs/FileSystemAccessImpl.java
Sending
gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/registry/CommandResolverImpl.java
Sending
gshell-wisdom/gshell-wisdom-core/src/main/java/org/apache/geronimo/gshell/wisdom/registry/GroupDirectoryResolver.java
Transmitting file data ...
Committed revision 741069.
The previous commit did break things. A better idea is to force a refresh on
the underlying file when resolving a DelegateFileObject
> Dynamically adding / removing commands does not work well
> ---------------------------------------------------------
>
> Key: GSHELL-157
> URL: https://issues.apache.org/jira/browse/GSHELL-157
> Project: GShell
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 1.0-alpha-2
>
>
> When resolving commands, the command resolver uses a virtual file system.
> Unfortunately, the data for virtual file systems is always cached, which
> means that removing a command will still make it available for resolution.
> The cache problem is caused by the DelegateFileObject which does not refresh
> the underlying file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
