[jboss-dev-forums] [Design of JBoss/Tomcat Integration] - Re: JBIDE-3394, hot deployment management api

[emuckenhuber]

"max.andersen at jboss.com" wrote : any example that does not require days spent in reverse engineering AS 5 testsuite to figure out how this remote deployment works and what the minimal dependencies are ? ;)
  | 

The minimal dependencies for compiling is quite easy:


  |     <dependency>
  |         <groupId>org.jboss.integration</groupId>
  |         <artifactId>jboss-profileservice-spi</artifactId>
  |         <version>5.0.3.GA</version>
  |     </dependency>
  | 

And i guess the minimal dependencies for running are something like this (plus the one above), but not really sure.


  |     <dependency>
  |        <groupId>org.jboss.naming</groupId>
  |        <artifactId>jnp-client</artifactId>
  |     </dependency>
  |       <dependency>
  |         <groupId>org.jboss.aspects</groupId>
  |         <artifactId>jboss-security-aspects</artifactId>
  |       </dependency>
  |      <dependency>
  |         <groupId>org.jboss.aspects</groupId>
  |         <artifactId>jboss-remoting-aspects</artifactId>
  |       </dependency>
  | 

And you get the DeploymentManager like this:


  |  InitialContext ctx = new InitialContext();
  |  ProfileService ps = (ProfileService) ctx.lookup("ProfileService");
  |  dm = ps.getDeploymentManager();
  |  // Load the default profile
  |  dm.loadProfile(new ProfileKey("default"), false);
  |  // deploy
  |  ...
  | 

For the jndi properties you can look at: http://www.jboss.org/community/docs/DOC-10949

And one note to the ProfileKey - "default" means the -c default for the moment.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199598#4199598

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199598