[jboss-user] [JBoss/Spring Integration] - Re: JBOSS5 + Spring Deployer version confusion

[alesj]

"dlmiles" wrote : 
  | The point I was getting at, is that no deployer should mindlessly attempt to deploy all files it finds at any nesting depth ending in *-beans.xml.
  | 
It is not.
Like I said, only those that are in metadata path.
See StructureDeployers for more info.

"dlmiles" wrote : 
  | But I would be happy for it to have a look at all files and then attempt to parse the file as a JBoss specific deployment descriptor.  Now during this process it should immediately see that my file has an XML Schema that belongs to Spring Framework.  Upon seeing this the deployer should stop considering that file as a JBoss deployment descriptor and no exception should be thrown.
  | 
  | This is the point of having XSDs to ensure an application that is not meant to process some data, does not attempt to process it!
  | 
  | The JBoss deployer does not own all the files ending in *-beans.xml that the JBoss VFS can find, it only own those files that also match the DTD/XSD schemes that JBoss understands.
  | 
Feel free to open this discussion in 'Deployers on JBoss' or 'Design of POJO server' forum.
No point of discussing this here, since this is getting out of the scope of this forum.

"dlmiles" wrote : 
  | Of course it has to parse the file, its bl**dy well doing that now is not it!  
  | 
:-)
The problem that I see here is, that most of the xml parsing/handling has the most awful exceptions, which would make it hard for us to distinguish between what's a real exception or just not the right combination of deployer+dtd/schema.

"dlmiles" wrote : 
  | The error I reported is due to a deployment failure because the contents of the XML appeared to be garbage to the MBean deployer when it attempted deployment.
  | 
No, it failed because the BeanDeployer expected that the outcome of unmarshalling would be KernelDeployment instance.

"dlmiles" wrote : 
  | Renaming my file in my WAR from /WEB-INF/spring-beans.xml to /WEB-INF/spring-context.xml did the trick.
  | 
"alesj" wrote : 
  | You can either rename the file or change the way BeanDeployer handles this file, e.g. perhaps not using the file if it also contains 'spring' in its name.
  | 
;-)

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

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