[
https://jira.jboss.org/jira/browse/JBAS-5682?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber resolved JBAS-5682.
---------------------------------------
Resolution: Out of Date
Assignee: Emanuel Muckenhuber (was: Scott M Stark)
Closing this jira as out of date. addDeployment does not necessarily need to include it in
getModifiedDeployments(). Therefore the DeploymentManager should be used to deploy
applications.
Profile service does not include newly added content in
getModifiedDeployments()
--------------------------------------------------------------------------------
Key: JBAS-5682
URL:
https://jira.jboss.org/jira/browse/JBAS-5682
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: JBossAS-5.1.0.Beta1
If a new deployment is added to a profile via Profile.addDeployment(VFSDeployment,
DeploymentPhase), a subsequent call to Profile.getModifiedDeployments() will not include
that deployment. Basically, the various getModifiedDeployments() impls do a VFS scan for
new content, but ignore anything that they already know about from an addDeployment(...)
call.
See forum thread for more in depth discussion.
--
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