[infinispan-issues] [JBoss JIRA] (ISPN-5238) Maintain session in ispn-mgmt-console (ctrl+R)

[Tomas Sykora (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053885#comment-13053885 ] 

Tomas Sykora commented on ISPN-5238:
------------------------------------

Thinking about that... maybe we just need add some special --dev task for gulp (instead of running only gulp.start('build') in default task. 
In that task we can specify default admin credentials and process some inits (where we are doing logging into the server mgmt). Then when we change a file during development, file change will be detected, pre-set credentials will be passed, init process will run and we will end up in a browser on the same page but with updated files. 

Need to do some research about possibilities here.

This is really annoying have to log-in after every small change when we want to see results.

> Maintain session in ispn-mgmt-console (ctrl+R)
> ----------------------------------------------
>
>                 Key: ISPN-5238
>                 URL: https://issues.jboss.org/browse/ISPN-5238
>             Project: Infinispan
>          Issue Type: Task
>          Components: JMX, reporting and management
>            Reporter: Tomas Sykora
>            Assignee: Vladimir Blagojevic
>             Fix For: 8.0.0.Final
>
>
> When you reload a page in Infinispan Management Console data is lost and you need to re-login. We need to make sure that the session is maintained properly and operations like ctrl+R, F5 etc. does not affect behaviour negatively. 
> It will also help with development and testing when you need to reload a page to see some changes from time to time. 
> I did a small research around this topic and made some experiments but I was not able to achieve what I wanted. Maybe we can come up with even different approach. 
> Anyway I suppose we can stick to the idea that ctrl+R should just reload the page and data successfully.   



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)