[jboss-jira] [JBoss JIRA] Issue Comment Edited: (JBAS-4078) DeploymentManager.getAvailableModules() returns null

Vladimir Vedernikov (JIRA) jira-events at lists.jboss.org
Thu Feb 3 07:20:39 EST 2011


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

Vladimir Vedernikov edited comment on JBAS-4078 at 2/3/11 7:20 AM:
-------------------------------------------------------------------

DeploymentManager.getAvailableModules() returns null because you had been tried to receive modules from jsr88 DeploymentManager ("http://org.jboss.deployment/jsr88"). It returs modules if they had been deployed by jsr88 DeploymentManager and had not just copied into the deploy directory.

In JBoss AS Administration Console all modules are visible. I guess it's better to use its API for those purposes.

      was (Author: vladimir.vedernikov):
    DeploymentManager.getAvailableModules() returns null because you had been tried to receive modules from jsr88 DeploymentManager ("http://org.jboss.deployment/jsr88"). It returs modules if they had been deployed by jsr88 DeploymentManager and not just copied into the deploy directory.

In JBoss AS Administration Console all modules are visible. I guess it's better to use its API for those purposes.
  
> DeploymentManager.getAvailableModules() returns null
> ----------------------------------------------------
>
>                 Key: JBAS-4078
>                 URL: https://issues.jboss.org/browse/JBAS-4078
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: JBoss 5.0.0.beta2 trunk build 20070206, JDK 1.5.0_08
>            Reporter: Libor Kotouc
>            Priority: Critical
>
> This issue blocks an integration of JBoss AS 5 into NetBeans IDE.
> Steps to reproduce the behavior:
> 1. create a simple web application and copy the .war file into the deploy directory (I used the 'default' server)
> 2. start JBoss server (./run.sh)
> 3. run the following code from a J2SE application (I added JBoss jars to the classpath):
> public class Main {
>     public static void main(String[] args) {
>         try {
>             javax.enterprise.deploy.spi.factories.DeploymentFactory df = new org.jboss.deployment.spi.factories.DeploymentFactoryImpl();
>             javax.enterprise.deploy.spi.DeploymentManager dm;
>             dm = df.getDeploymentManager("http://org.jboss.deployment/jsr88", null, null);
>             javax.enterprise.deploy.spi.Target[] targets = dm.getTargets();
>             javax.enterprise.deploy.spi.TargetModuleID[] modules;
>             modules = dm.getAvailableModules(javax.enterprise.deploy.shared.ModuleType.WAR, targets);
>             System.out.println(targets.length + " " + targets[0]);
>             System.out.println(modules);
>             
>         } catch (javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException ex) {
>         } catch (javax.enterprise.deploy.spi.exceptions.TargetException ex) {
>         }
>     }
> }
> The output of System.out.println statements is:
> 1 org.jboss.deployment.spi.JMXTarget at 161d36b
> null
> I expect the module representing the web application, but null is returned.

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

        


More information about the jboss-jira mailing list