[JBoss JIRA] (SRAMP-185) Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-185:
--------------------------------
Fix Version/s: 0.2.0 - Milestone 4
> Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
> ---------------------------------------------------------------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Eric Wittmann
> Fix For: 0.2.0 - Milestone 4
>
>
> Update
> ------
> The s-ramp Query CLI command should be updated to require a single argument (rather than accepting multiple arguments and concat'ing them). In addition, the tab-completion should be updated to add at least the leading " (so users don't forget it). Even better, if the tab-completion can add *both* the leading and trailing quotes and position the cursor between them, that would be ideal.
> Original Report (historical context)
> ------------------------------------
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-185) Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-185:
-------------------------------------
I think we have a path forward to more consistent and useful behavior for the Query CLI command. I have updated the title and description to reflect our decisions.
> Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
> ---------------------------------------------------------------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Eric Wittmann
> Fix For: 0.2.0 - Milestone 4
>
>
> Update
> ------
> The s-ramp Query CLI command should be updated to require a single argument (rather than accepting multiple arguments and concat'ing them). In addition, the tab-completion should be updated to add at least the leading " (so users don't forget it). Even better, if the tab-completion can add *both* the leading and trailing quotes and position the cursor between them, that would be ideal.
> Original Report (historical context)
> ------------------------------------
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-185) Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Eric Wittmann reassigned SRAMP-185:
-----------------------------------
Assignee: Eric Wittmann (was: Kurt Stam)
> Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
> ---------------------------------------------------------------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Eric Wittmann
>
> Update
> ------
> The s-ramp Query CLI command should be updated to require a single argument (rather than accepting multiple arguments and concat'ing them). In addition, the tab-completion should be updated to add at least the leading " (so users don't forget it). Even better, if the tab-completion can add *both* the leading and trailing quotes and position the cursor between them, that would be ideal.
> Original Report (historical context)
> ------------------------------------
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-185) Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-185:
--------------------------------
Description:
Update
------
The s-ramp Query CLI command should be updated to require a single argument (rather than accepting multiple arguments and concat'ing them). In addition, the tab-completion should be updated to add at least the leading " (so users don't forget it). Even better, if the tab-completion can add *both* the leading and trailing quotes and position the cursor between them, that would be ideal.
Original Report (historical context)
------------------------------------
s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
Querying the S-RAMP repository:
/s-ramp[xp2:matches(@contentType, .* )]
FAILED to query the repository.
Unterminated argument list.
s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
Querying the S-RAMP repository:
/s-ramp[xp2:matches(@contentType, .* )]
FAILED to query the repository.
Unterminated argument list.
s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
Querying the S-RAMP repository:
/s-ramp[xp2:matches(@contentType, a )]
FAILED to query the repository.
Expected a string literal as the argument (the only supported argument type for the argument).
was:
s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
Querying the S-RAMP repository:
/s-ramp[xp2:matches(@contentType, .* )]
FAILED to query the repository.
Unterminated argument list.
s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
Querying the S-RAMP repository:
/s-ramp[xp2:matches(@contentType, .* )]
FAILED to query the repository.
Unterminated argument list.
s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
Querying the S-RAMP repository:
/s-ramp[xp2:matches(@contentType, a )]
FAILED to query the repository.
Expected a string literal as the argument (the only supported argument type for the argument).
> Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
> ---------------------------------------------------------------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Kurt Stam
>
> Update
> ------
> The s-ramp Query CLI command should be updated to require a single argument (rather than accepting multiple arguments and concat'ing them). In addition, the tab-completion should be updated to add at least the leading " (so users don't forget it). Even better, if the tab-completion can add *both* the leading and trailing quotes and position the cursor between them, that would be ideal.
> Original Report (historical context)
> ------------------------------------
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-185) Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-185:
--------------------------------
Summary: Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments) (was: "matches" query parsing error in CLI?)
> Query CLI command - require the query to be in quotes (no more concat'ing multiple arguments)
> ---------------------------------------------------------------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Kurt Stam
>
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-185) "matches" query parsing error in CLI?
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-185:
-------------------------------------
The problem is using quotes in CLI commands. The s-ramp:query command *tries* to be helpful and mash all of its arguments together into a single s-ramp query, but it doesn't always do the right thing. Try this:
s-ramp:query "/s-ramp[xp2:matches(@contentType, '.*')]"
This will cause the query command to receive only one argument - the query. Your other variants cause the query command to receive three arguments:
s-ramp:query /s-ramp[xp2:matches(@contentType,
.*
)]
The command tries to be helpful by concat'ing all its arguments, but by that time the quotes have been lost.
> "matches" query parsing error in CLI?
> -------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Kurt Stam
>
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-185) "matches" query parsing error in CLI?
by Kurt Stam (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Kurt Stam commented on SRAMP-185:
---------------------------------
lkrejci: it's the SPACES!
[11:26am] lkrejci: s-ramp:query /s-ramp[xp2:matches(@contentType,'.*')] works
[11:26am] lkrejci: s-ramp:query /s-ramp[xp2:matches(@contentType, '.*')] doesn't
> "matches" query parsing error in CLI?
> -------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Kurt Stam
>
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (SRAMP-185) "matches" query parsing error in CLI?
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-185?page=com.atlassian.jira.plugin.... ]
Eric Wittmann edited comment on SRAMP-185 at 4/24/13 11:28 AM:
---------------------------------------------------------------
The problem is using spaces and quotes in CLI commands. The s-ramp:query command *tries* to be helpful and mash all of its arguments together into a single s-ramp query, but it doesn't always do the right thing. Try this:
s-ramp:query "/s-ramp[xp2:matches(@contentType, '.*')]"
This will cause the query command to receive only one argument - the query. Your other variants cause the query command to receive three arguments:
s-ramp:query /s-ramp[xp2:matches(@contentType,
.*
)]
The command tries to be helpful by concat'ing all its arguments, but by that time the quotes have been lost.
was (Author: eric.wittmann):
The problem is using quotes in CLI commands. The s-ramp:query command *tries* to be helpful and mash all of its arguments together into a single s-ramp query, but it doesn't always do the right thing. Try this:
s-ramp:query "/s-ramp[xp2:matches(@contentType, '.*')]"
This will cause the query command to receive only one argument - the query. Your other variants cause the query command to receive three arguments:
s-ramp:query /s-ramp[xp2:matches(@contentType,
.*
)]
The command tries to be helpful by concat'ing all its arguments, but by that time the quotes have been lost.
> "matches" query parsing error in CLI?
> -------------------------------------
>
> Key: SRAMP-185
> URL: https://issues.jboss.org/browse/SRAMP-185
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Client, Core
> Affects Versions: 0.1.1
> Reporter: Lukas Krejci
> Assignee: Kurt Stam
>
> s-ramp> query /s-ramp[xp2:matches(@contentType, '.*')]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, ".*")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, .* )]
> FAILED to query the repository.
> Unterminated argument list.
> s-ramp> query /s-ramp[xp2:matches(@contentType, "a")]
> Querying the S-RAMP repository:
> /s-ramp[xp2:matches(@contentType, a )]
> FAILED to query the repository.
> Expected a string literal as the argument (the only supported argument type for the argument).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months