[JBoss JIRA] (SRAMP-200) Overlord Commons installer: update to work against vanilla EAP
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-200:
-----------------------------------
Summary: Overlord Commons installer: update to work against vanilla EAP
Key: SRAMP-200
URL: https://issues.jboss.org/browse/SRAMP-200
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.3.0 - JBPM6 Integration
Currently the overlord commons installer assumes that picketlink is installed in standalone.xml. Need to update it so that it installs all the required config (e.g. picketlink extension).
--
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, 6 months
[JBoss JIRA] (SRAMP-148) Add "repo-only" option to s-ramp distro Ant installer
by Kurt Stam (JIRA)
[ https://issues.jboss.org/browse/SRAMP-148?page=com.atlassian.jira.plugin.... ]
Kurt Stam commented on SRAMP-148:
---------------------------------
The only thing missing seems to be the picketlink extension in the standalone.xml. This needs to be updated in the overlord-commons module.
> Add "repo-only" option to s-ramp distro Ant installer
> -----------------------------------------------------
>
> Key: SRAMP-148
> URL: https://issues.jboss.org/browse/SRAMP-148
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Distro
> Reporter: Eric Wittmann
> Assignee: Kurt Stam
> Priority: Minor
> Fix For: 0.3.0 - JBPM6 Integration
>
>
> Currently the Ant installer pulls down everything, including jbpm and drools guvnor. We can get a quicker quickstart if we have a path through the Ant installer that just installs S-RAMP in a standard JBoss AS 7.1.1.Final.
--
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, 6 months
[JBoss JIRA] (RTGOV-188) Change order mgmt app quickstart from war to jar
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-188?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-188.
------------------------------
Resolution: Done
> Change order mgmt app quickstart from war to jar
> ------------------------------------------------
>
> Key: RTGOV-188
> URL: https://issues.jboss.org/browse/RTGOV-188
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.Final
>
>
> Change from war to jar. Issue when previously attempted was the dependencies.
> Other problem is that the ActivityReporter used by the beans will not work, unless packaged with the app - which requires it to be a war.
> To options with this:
> 1) Change to instantiate the DefaultActivityReporter, so use the external dependency from a jar - but not as convenient as using injection.
> 2) Leave this example as a war, but ensure that test exists for swyd app packaged as jar with an auditor performing a sync policy.
--
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, 7 months
[JBoss JIRA] (RTGOV-207) Service overview gadget requires separate basic auth signin
by Gary Brown (JIRA)
Gary Brown created RTGOV-207:
--------------------------------
Summary: Service overview gadget requires separate basic auth signin
Key: RTGOV-207
URL: https://issues.jboss.org/browse/RTGOV-207
Project: RTGov (Run Time Governance)
Issue Type: Bug
Reporter: Gary Brown
Assignee: Eric Wittmann
Priority: Critical
Fix For: 1.0.0.Final
Security is now enabled on rtgov REST services, which has highlighted an issue with the service overview gadget.
After normal SSO signin, when the service overview gadget is added to the page, its first interaction with the server results in a login dialog being displayed.
On investigation, Eric found that the gadget's xml includes a direct request to the overlord-rtgov REST service to retrieve the SVG, which is bypassing the gadget IO layer.
Eric's suggestion is to create an SVG proxy servlet in gadget-web.war, which can deal with the authentication.
--
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, 7 months
[JBoss JIRA] (RTGOV-64) Activity collector event filtering
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-64?page=com.atlassian.jira.plugin.s... ]
Gary Brown commented on RTGOV-64:
---------------------------------
Other thing to investigate here is where the process information step could be moved from the intercepting thread to the batch reporting thread.
> Activity collector event filtering
> ----------------------------------
>
> Key: RTGOV-64
> URL: https://issues.jboss.org/browse/RTGOV-64
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Priority: Critical
> Fix For: 1.0.0.Final
>
>
> Collector activity event filtering mechanism to enable administrator to control what level of events are reported.
> Some level of filtering may be performed based on which interceptors are installed. However may need more fine level of control.
--
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, 7 months
[JBoss JIRA] (RTGOV-172) Represent switchyard service components
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-172?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-172.
------------------------------
Fix Version/s: (was: 1.0.0.Final)
Resolution: Rejected
The service is the component. The only requirement may be to record the containing switchyard app as a property for information purposes.
> Represent switchyard service components
> ---------------------------------------
>
> Key: RTGOV-172
> URL: https://issues.jboss.org/browse/RTGOV-172
> Project: RTGov (Run Time Governance)
> Issue Type: Enhancement
> Reporter: Gary Brown
> Assignee: Gary Brown
>
> Currently the individual service components included in a switchyard application are recorded as the service type in the activity events. However this means that the context (i.e. the switchyard application) is not recorded.
> However when considering switchyard applications from a management perspective, it may be more nature to consider the application as being the 'service', which exposes its capabilities via interfaces defined in the bindings.
> Therefore the switchyard app type could be recorded as the service type, and introduce a new field to define the type of the component.
> We then need to consider whether the inbound binding should be treated as a separate component? At present the binding interface is used in place of the one associated with the initial component - so the binding and the initial component are collapsed into a single set of events.
--
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, 7 months