Jira is down it seems currently, so this is what I have updated the
loadProfile javadoc to:
/**
* Load and associate the given profile with the ManagementView
* for future operations. This must be called before the other
ManagementView
* operations may be used. Currently there can only be one actively
loaded
* profile against which a client is performing management
operations.
*
* @param key - the profile key to load
* @throws NoSuchProfileException
*/
public void loadProfile(ProfileKey key)
throws Exception;
-------- Original Message --------
[ https://jira.jboss.org/jira/browse/JBAS-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12438349#action_12438349 ]
Ian Springer commented on JBAS-5370:
------------------------------------
Thanks, adding the call to DeploymentManager.loadProfile() did the trick. Could you possibly add some more javadoc on that method? If the DeploymentManager is a singleton, then how does one prevent threads from interfering with each other by loading different profiles via loadProfile()?
> Deploy an ear/war app through ProfileService
> --------------------------------------------
>
> Key: JBAS-5370
> URL: https://jira.jboss.org/jira/browse/JBAS-5370
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Mark Spritzler
> Assignee: Scott M Stark
> Priority: Critical
> Fix For: JBossAS-5.0.0.GA
>
>
--
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