[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-9100) Improve sepration of concerns when creating .dodeploy markers in JBoss7ServerBehavior and JBoss7JSTPublisher

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim resolved JBIDE-9100.
-------------------------------------

    Resolution: Done


> Improve sepration of concerns when creating .dodeploy markers in JBoss7ServerBehavior and JBoss7JSTPublisher 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-9100
>                 URL: https://issues.jboss.org/browse/JBIDE-9100
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.3.0.M1
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.3.0.M2
>
>
> When deploying to AS7 there are 2 components involved:
> * JBoss7JSTPublisher: adds markers that shall be created to the JBoss7ServerBehavior (see #markDeployed)
> * JBoss7ServerBehavior: creates the .dodeploy markers (see #publishFinish)
> IMHO what is not ideal here is that the list of markers that shall be created is passed around in form of an object (the publisher adds a list as a java.lang.Object and the server behavior then gets the java.lang.Object and then cast it to a List.
> If you would want to change the form that shall hold the marker you'd have to figure out and change both components. Both components have to know about the form, which is not ideal in terms of separation of concerns.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira