EjbClientJarManifestClassPathpublic class EjbClientJarManifestClassPath extends com.sun.enterprise.tools.verifier.tests.ejb.EjbTest implements com.sun.enterprise.tools.verifier.tests.ejb.EjbCheckThe EJB specification does not specify whether the ejb-jar file should
include the classes that are in the ejb-client JAR by copy or by reference.
If the by-copy approach is used, the producer simply includes all the class
files in the ejb-client JAR file also in the ejb-jar file. If the
by-reference approach is used, the ejb-jar file producer does not duplicate
the content of the ejb-client JAR file in the ejb-jar file, but instead uses
a Manifest Class-Path entry in the ejb-jar file to specify that the ejb-jar
file depends on the ejb-client JAR at runtime. |
Methods Summary |
---|
public Result | check(com.sun.enterprise.deployment.EjbDescriptor descriptor)The EJB specification does not specify whether the ejb-jar file should
include the classes that are in the ejb-client JAR by copy or by reference.
If the by-copy approach is used, the producer simply includes all the class
files in the ejb-client JAR file also in the ejb-jar file. If the
by-reference approach is used, the ejb-jar file producer does not duplicate
the content of the ejb-client JAR file in the ejb-jar file, but instead uses
a Manifest Class-Path entry in the ejb-jar file to specify that the ejb-jar
file depends on the ejb-client JAR at runtime.
Result result = getInitializedResult();
ComponentNameConstructor compName = getVerifierContext().getComponentNameConstructor();
// Stub test class placeholder
// fill in guts/logic - pass/fail accordingly in future
// once DOL returns proper value
result.setStatus(Result.NOT_IMPLEMENTED);
result.addNaDetails(smh.getLocalString
("tests.componentNameConstructor",
"For [ {0} ]",
new Object[] {compName.toString()}));
result.addNaDetails
(smh.getLocalString
(getClass().getName() + ".notImplemented",
"No static testing done - yet."));
return result;
|
|