DFS & the packageService ANT task - a feature?

aflowers001

Hi,

We have recently been building a solution based on DFS 6.5 SP1.

Our solution was required to make calls into DFC and it also used custom JARs.

When packaging we used wildcards in the packageService ANT task in our buuild file and we came across an issue

If we used

        <packageService deploymentName="..." destDir="..." generatedArtifactsDir="...">
            <libraries>

                ...
                <pathelement location="ourjars/*.jar"/>

                ....
            </libraries>
            <resources>
            </resources>
        </packageService>

we noticed that in JBoss it all worked fine but in Websphere it failed as it couldn't find out custom classes.

Upon investigation it appears that using <pathelement .../> and wildcards didn't include references to the jar files in the manifest.mf of that war file corresponding to the service that gets embedded in the ear file.

If we use a form such as

        <packageService deploymentName="..." destDir="..." generatedArtifactsDir="...">
            <libraries>
                <path location="ourjars/jar1.jar"/>
                <path location="ourjars/jar2.jar"/>
             </libraries>
        </packageService>

then all is well and the manifest.mf gets updated correctly.

So, if you're having issues with Websphere might be worth checking how you package the service. I might even get around to raising a support call about this, unless one of the DFS team is taking a peek