[JBoss JIRA] (SRAMP-543) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-543 stopped by Brett Meyer.
> Logout not working
> ------------------
>
> Key: SRAMP-543
> URL: https://issues.jboss.org/browse/SRAMP-543
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: UI
> Affects Versions: 0.5.0.Beta3, 0.5.0.Final
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
> Fix For: 0.6.0
>
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-543) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-543:
-----------------------------------
Reproduced it as well -- will take a look
> Logout not working
> ------------------
>
> Key: SRAMP-543
> URL: https://issues.jboss.org/browse/SRAMP-543
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: UI
> Affects Versions: 0.5.0.Beta3, 0.5.0.Final
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
> Fix For: 0.6.0
>
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-543) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-543:
------------------------------
Fix Version/s: 0.6.0
> Logout not working
> ------------------
>
> Key: SRAMP-543
> URL: https://issues.jboss.org/browse/SRAMP-543
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: UI
> Affects Versions: 0.5.0.Beta3, 0.5.0.Final
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
> Fix For: 0.6.0
>
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-543) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-543 started by Brett Meyer.
> Logout not working
> ------------------
>
> Key: SRAMP-543
> URL: https://issues.jboss.org/browse/SRAMP-543
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: UI
> Affects Versions: 0.5.0.Beta3, 0.5.0.Final
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
> Fix For: 0.6.0
>
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-541:
-----------------------------------
[~sbunciak], [~eric.wittmann] and I discussed this a bit more today.
http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/cs01/part2-atom-binding/s-r...
That part of the spec mentions that PUT (the only update mechanism) is "only used to update an existing Atom entry document." When it says "Atom entry", to me that signifies metadata-only, not the actual artifact content. So, I think we'll probably press on with stripping out updateContent, unless someone has a point I'm overlooking.
> Consider removing artifact/content updates
> ------------------------------------------
>
> Key: SRAMP-541
> URL: https://issues.jboss.org/browse/SRAMP-541
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> From [~eric.wittmann] on SRAMP-539:
> {quote}
> In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail.
> All in all I am disappointed in myself for implementing the updateContent feature to begin with.
> {quote}
> I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-433:
------------------------------
Description:
Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about.
Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server.
Event design thoughts: https://community.jboss.org/message/884274
was:
Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about.
Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server.
> Create a proper Event producer for s-ramp
> -----------------------------------------
>
> Key: SRAMP-433
> URL: https://issues.jboss.org/browse/SRAMP-433
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about.
> Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server.
> Event design thoughts: https://community.jboss.org/message/884274
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-541:
-----------------------------------
[~sbunciak], that was the thought -- removing it across the board. However, before we jump to conclusions, let's think it through completely. The S-RAMP Atom spec does have bits about updating content through PUT, but it's fairly vague.
> Consider removing artifact/content updates
> ------------------------------------------
>
> Key: SRAMP-541
> URL: https://issues.jboss.org/browse/SRAMP-541
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> From [~eric.wittmann] on SRAMP-539:
> {quote}
> In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail.
> All in all I am disappointed in myself for implementing the updateContent feature to begin with.
> {quote}
> I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-543) Logout not working
by Stefan Bunciak (JIRA)
Stefan Bunciak created SRAMP-543:
------------------------------------
Summary: Logout not working
Key: SRAMP-543
URL: https://issues.jboss.org/browse/SRAMP-543
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: UI
Affects Versions: 0.5.0.Final, 0.5.0.Beta3
Environment: Fedora 20
S-RAMP installed into JBoss EAP 6.1.1.GA
Firefox 31
Chrome 36
Reporter: Stefan Bunciak
Assignee: Brett Meyer
Priority: Blocker
I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0
by Gary Brown (JIRA)
Gary Brown created RTGOV-556:
--------------------------------
Summary: RTGov UI no longer working on FSW 6.0
Key: RTGOV-556
URL: https://issues.jboss.org/browse/RTGOV-556
Project: RTGov (Run Time Governance)
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months