[arquillian-issues] [JBoss JIRA] (ARQ-1166) Check if current deployment is same as from metadata

[Bernard Labno (JIRA)]

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

Bernard Labno commented on ARQ-1166:
------------------------------------

[10:53] <aslak> http://pastebin.com/bQP8rJiS line:50
[10:53] <aslak> the original file name is linked in. the Asset might have a different name in the Archive then on the Filesystem
[10:54] <aslak> in this case we're setting up rebel.xml to monitor test-web.xml, but does rebel know that that is our web.xml ?
[10:55] == jharting [jharting at redhat/jboss/jharting] has joined #jbosstesting
[10:56] <aslak> most of those shouldn't be linked under "web".
[10:57] <blabno> aslak, sorry, but i don't understand
[10:57] == kpiwko [kpiwko at redhat/jboss/kpiwko] has joined #jbosstesting
[10:57] <blabno> i think jrebel will not know that test-web.xml is web.xml in archive
[10:58] <aslak> but it should ?
[10:58] <blabno> well, would be nice for use
[10:58] <blabno> for us, but I don't think they have forseen this
[10:58] <blabno> and I would not expet them to support this
[10:59] <aslak> blabno, mm, I can't seem to find any 'rename/redirect' type element
[11:00] <aslak> we basically want to say: as / in web, link from src/test/resources/ file test-web.xml as web.xml
[11:00] <blabno> i think that we will need to copy all resources that have different name in archive then in filesystem to jrebel temp
[11:01] <aslak> mm yea, rebel should still be able to detect the changes when you run so. the user shouldn't notice
[11:02] <aslak> i'll add it to my 'jrebel-feature-request' list
[11:02] <blabno> :) yes and let's gather bunch of people to vote for it :D
                
> Check if current deployment is same as from metadata
> ----------------------------------------------------
>
>                 Key: ARQ-1166
>                 URL: https://issues.jboss.org/browse/ARQ-1166
>             Project: Arquillian
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Extension - JRebel
>            Reporter: Bernard Labno
>            Assignee: Bernard Labno
>
> [10:09] <aslak> one example from the JavaOne demo: I had ran the example with jrebel earlier and it worked during preparation.
> [10:10] <aslak> but not during the demo, because at demo time i had disabled the extension and ran a few other tests, then enabled it again. strange exceptions started to happen
> [10:10] == mnovak [mnovak at nat/redhat/x-vnphfxzlziqohqfq] has joined #jbosstesting
> [10:10] <aslak> the reason was that i hadn't cleaned up target, so the extension falsely found the old deployment metadata and assumed it was deployed
> [10:11] <blabno> aslak: that's what i suspected
> [10:11] == chm007 [~cmoulliar at ip-83-134-24-63.dsl.scarlet.be] has joined #jbosstesting
> [10:11] <blabno> aslak: devs need to remember to cleanup target
> [10:12] <aslak> just wondering if there is some kind of check we can do to know if we're running within the same 'run' or not
> [10:12] <aslak> basically knowing if what we assume is deployed is actually deployed.
> [10:13] <aslak> pr spi now, we can't check if a deployment is deployed
> [10:13] <aslak> but can we detect this in some other way
> [10:15] <blabno> aslak: we could add servlet that would return deployments checksum
> [10:15] <blabno> same as in metadata
> [10:15] <aslak> hmm.. that's an option
> [10:16] <aslak> we have the ProtocolMetadata stored, so we know the details of where that should be deployed
> [10:16] <aslak> ip/port/context

--
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