[
https://issues.apache.org/jira/browse/TINKERPOP-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157618#comment-15157618
]
Bob Briody commented on TINKERPOP-1102:
---------------------------------------
Yeah that sounds fine. I don't see a good fix for this either. At first I
thought it might be possible to do generic serialization based on the
Collection Interface types, but I see why that's weird. The only possible
improvement might be to invalidate when addArg() is called, but I don't feel
strongly about that at all. I'm totally fine w/ just closing.
> Request message does not handle immutable map
> ---------------------------------------------
>
> Key: TINKERPOP-1102
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1102
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
> Affects Versions: 3.1.0-incubating
> Reporter: Bob Briody
>
> When building a RequestMessage with the java Gremlin Client Driver, things
> don't work correctly if an Immutable Map is used as shown here:
> {code}
> requestMessage.addArg(Tokens.ARGS_ALIASES, ImmutableMap.builder().put("g",
> "some_alias.g").build());
> {code}
> Note that the RequestMessage can be built, and even executed, but the alias
> does not bind correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
