[JBoss JIRA] (RTGOV-416) Investigate solution for deploying ElasticSearch EPN on FSW 6.0
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-416?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-416:
----------------------------------
Yes this is correct - so we will take this approach.
> Investigate solution for deploying ElasticSearch EPN on FSW 6.0
> ---------------------------------------------------------------
>
> Key: RTGOV-416
> URL: https://issues.jboss.org/browse/RTGOV-416
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> This task is to investigate options for supporting ElasticSearch capabilities in FSW 6.0.
> RTGOV-342 has provided an event processor for ElasticSearch. However this introduces a new 'service' to represent a KeyValueStore, which ElasticSearch is the first implementation.
> If we want to deploy an ElasticSearch based EPN, this new abstract class (currently located in rtgov-commons) is the only issue.
> There are two current proposed solutions:
> 1) Move the abstract class (within the same package) into the rtgov-elasticsearch package as a temporary measure for the next release.
> The issue with this potential solution is if the jars in FSW6.0 are signed - then it won't be possible to have two jars containing classes in the same package.
> 2) Another temporary solution for the next community release would be to inherit the ElasticSearchKeyValueStore directly from the Service abstract class.
> The implication of this would be the EPN's would need to directly use the ElasticSearchKeyValueStore class, rather than the more generic KeyValueStore class - which means that it won't simply be a configuration change to be able to use an alternative KeyValueStore implementation.
> However, as the ElasticSearchKeyValueStore will be the only implementation at that point, then this would work - we would just need to remember to change the EPN's java code after the release, to again use the generic KeyValueStore abstract class.
> At this point, the second option appears to be best, as it localises the changes to the rtgov-elasticsearch module. The rtgov-commons module can remain untouched.
--
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
10 years, 8 months
[JBoss JIRA] (RTGOV-416) Investigate solution for deploying ElasticSearch EPN on FSW 6.0
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-416?page=com.atlassian.jira.plugin.... ]
ivan mckinley commented on RTGOV-416:
-------------------------------------
For option 2.
- Will the rtgov-commons remain untouched for fsw 6.0. the KeyValueService remains untouched present rtgov2.0.0
- For FSW 6.0 ElasticSearchKeyValueStore simply extends Service. At a later date, FSW 6.1, it is refactored to extend KeyValueService in rtgov-common
Option seems like the best direction to take.
The fact that the EPNs reference the keystore implementation is not such a big problem. they can be refactored at a later date for fsw 6.1
> Investigate solution for deploying ElasticSearch EPN on FSW 6.0
> ---------------------------------------------------------------
>
> Key: RTGOV-416
> URL: https://issues.jboss.org/browse/RTGOV-416
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.M1
>
>
> This task is to investigate options for supporting ElasticSearch capabilities in FSW 6.0.
> RTGOV-342 has provided an event processor for ElasticSearch. However this introduces a new 'service' to represent a KeyValueStore, which ElasticSearch is the first implementation.
> If we want to deploy an ElasticSearch based EPN, this new abstract class (currently located in rtgov-commons) is the only issue.
> There are two current proposed solutions:
> 1) Move the abstract class (within the same package) into the rtgov-elasticsearch package as a temporary measure for the next release.
> The issue with this potential solution is if the jars in FSW6.0 are signed - then it won't be possible to have two jars containing classes in the same package.
> 2) Another temporary solution for the next community release would be to inherit the ElasticSearchKeyValueStore directly from the Service abstract class.
> The implication of this would be the EPN's would need to directly use the ElasticSearchKeyValueStore class, rather than the more generic KeyValueStore class - which means that it won't simply be a configuration change to be able to use an alternative KeyValueStore implementation.
> However, as the ElasticSearchKeyValueStore will be the only implementation at that point, then this would work - we would just need to remember to change the EPN's java code after the release, to again use the generic KeyValueStore abstract class.
> At this point, the second option appears to be best, as it localises the changes to the rtgov-elasticsearch module. The rtgov-commons module can remain untouched.
--
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
10 years, 8 months
[JBoss JIRA] (SRAMP-392) Documentation: Use single quotes in S-RAMP query examples
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-392:
-----------------------------------
Summary: Documentation: Use single quotes in S-RAMP query examples
Key: SRAMP-392
URL: https://issues.jboss.org/browse/SRAMP-392
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 0.4.0 - Tomcat Support
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.5.0 - API Management
The guide has a section on s-ramp query examples. These examples use double-quotes which makes it hard to copy/paste them into the CLI. Use single quotes instead.
--
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
10 years, 8 months
[JBoss JIRA] (RTGOV-416) Investigate solution for deploying ElasticSearch EPN on FSW 6.0
by Gary Brown (JIRA)
Gary Brown created RTGOV-416:
--------------------------------
Summary: Investigate solution for deploying ElasticSearch EPN on FSW 6.0
Key: RTGOV-416
URL: https://issues.jboss.org/browse/RTGOV-416
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
This task is to investigate options for supporting ElasticSearch capabilities in FSW 6.0.
RTGOV-342 has provided an event processor for ElasticSearch. However this introduces a new 'service' to represent a KeyValueStore, which ElasticSearch is the first implementation.
If we want to deploy an ElasticSearch based EPN, this new abstract class (currently located in rtgov-commons) is the only issue.
There are two current proposed solutions:
1) Move the abstract class (within the same package) into the rtgov-elasticsearch package as a temporary measure for the next release.
The issue with this potential solution is if the jars in FSW6.0 are signed - then it won't be possible to have two jars containing classes in the same package.
2) Another temporary solution for the next community release would be to inherit the ElasticSearchKeyValueStore directly from the Service abstract class.
The implication of this would be the EPN's would need to directly use the ElasticSearchKeyValueStore class, rather than the more generic KeyValueStore class - which means that it won't simply be a configuration change to be able to use an alternative KeyValueStore implementation.
However, as the ElasticSearchKeyValueStore will be the only implementation at that point, then this would work - we would just need to remember to change the EPN's java code after the release, to again use the generic KeyValueStore abstract class.
At this point, the second option appears to be best, as it localises the changes to the rtgov-elasticsearch module. The rtgov-commons module can remain untouched.
--
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
10 years, 8 months