[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3362) Inconsistency with publish status when using in-workspace deploy

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Sat Dec 6 02:57:36 EST 2008


    [ https://jira.jboss.org/jira/browse/JBIDE-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12441507#action_12441507 ] 

Max Rydahl Andersen commented on JBIDE-3362:
--------------------------------------------

sorry, was unclear - but yes, I mean See X as in open or refresh a browser that points to the url where X is supposed to be. i.e. http://localhost:8080/X

If you do add the deploy url at startup then we need to add some error handling (or at least save that something is wrong so when publish occur you can tell about it) in the case of the deploy url does not exist for some reason or other.

> Inconsistency with publish status when using in-workspace deploy
> ----------------------------------------------------------------
>
>                 Key: JBIDE-3362
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3362
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.cr1
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.0.0.cr1, 3.0.0.GA
>
>
> Use the default in workspace deploy to AS
> Deploy X to AS
> Start AS
> See that X is there
> Stop AS
> Start AS
> Now X is gone - most likely because the URL location of X is not registered ?
> Deploy X
> Now X is there
> Not sure if this is intended,if it is we need to handle it better. Why do I have to deploy to see something that is already there according to the ui (i.e. Published)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbosstools-issues mailing list