Inconsistent default deployer suffixes result in IncompleteDeploymentExceptions
--------------------------------------------------------------------------------
Key: JBAS-1264
URL: http://jira.jboss.com/jira/browse/JBAS-1264
Project: JBoss Application Server
Type: Bug
Components: MicroContainer bus
Versions: JBossAS-4.0.1 Final, JBossAS-4.0.0 Final
Reporter: Scott M Stark
Assigned to: Scott M Stark
In the change to generalize the deployer suffix management, the acceptance of
deployable content has relaxed a bit as the MainDeployer suffixes are not as
precise as they should be. For example, any descriptor seen to end in ds.xml is
seen as deployable based on the SubDeployerSupport.isDeployable method, even
though the XSLSubDeployer only accepts -ds.xml suffixes. This results in
spurious IncompleteDeploymentExceptions about no deployer for descriptors like
fields.xml.
We should probably not have any default suffix list and simply let it be built
by the registration of the sub deployers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
