[jboss-dev-forums] [Design of JCA on JBoss] - Re: Programmatic deployment--Redux

[weston.price@jboss.com]

Ugh...this won't work either. 

In the ServiceXSLDeployer


  | ServiceDeployment parsed = new ServiceDeployment();
  | 
  |       List<ServiceDeploymentClassPath> classPaths = parseXMLClasspath(document);
  |       parsed.setClassPaths(classPaths);
  | 
  |       LoaderRepositoryConfig repository = parseLoaderRepositoryConfig(document);
  |       if (repository != null)
  |          parsed.setLoaderRepositoryConfig(repository);
  | 
  |       // We can't parse the services yet, because it requires the classloader
  |       parsed.setConfig(document.getDocumentElement());
  | 
  | 

In the ServiceDeploymentDeployer


  |   List<ServiceMetaData> services = deployment.getServices();
  |             if (services == null)
  |             {
  |                Element config = deployment.getConfig();
  |                if (config == null)
  |                {
  |                   log.debug("Service deployment has no services: " + deployment.getName());
  |                   return;
  |                }
  |                
  |                ServiceMetaDataParser parser = new ServiceMetaDataParser(config);
  |                services = parser.parse();
  |                deployment.setServices(services);
  |             }
  | 
  | 

So, basically the ServiceXSLDeployer is parsing the *-ds.xml file. Using XSLT this creates the typical MBean configuration. Once this is done, the resulting ServiceDeployment is passed off to the ServiceDeploymentDeployer. He simply parses the XML configuration generated by the XSLT. The new stuff won't have this because being that no XML is created, it's all MetaData at that point. 

Damnit...back to square one.




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

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