Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-1264

Inconsistent default deployer suffixes result in IncompleteDeploymentExceptions

    Details

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  starksm64 Scott Stark
                  Reporter:
                  starksm64 Scott Stark
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 1 hour
                    1h
                    Remaining:
                    Remaining Estimate - 1 hour
                    1h
                    Logged:
                    Time Spent - Not Specified
                    Not Specified