From b9421dc80af485591a9c50cc8921f912e0def11e Mon Sep 17 00:00:00 2001 From: Ashlee Young Date: Fri, 23 Oct 2015 10:05:40 -0700 Subject: Removing sources to replace with download links instead. Change-Id: Ie28789a725051aec0d1b04dd291b7690a7898668 Signed-off-by: Ashlee Young --- .../manual/Tasks/BorlandEJBTasks.html | 143 --------------------- 1 file changed, 143 deletions(-) delete mode 100644 framework/src/ant/apache-ant-1.9.6/manual/Tasks/BorlandEJBTasks.html (limited to 'framework/src/ant/apache-ant-1.9.6/manual/Tasks/BorlandEJBTasks.html') diff --git a/framework/src/ant/apache-ant-1.9.6/manual/Tasks/BorlandEJBTasks.html b/framework/src/ant/apache-ant-1.9.6/manual/Tasks/BorlandEJBTasks.html deleted file mode 100644 index 126fe5c5..00000000 --- a/framework/src/ant/apache-ant-1.9.6/manual/Tasks/BorlandEJBTasks.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - - -Borland EJB Tasks - - - - -

BorlandDeployTool

-

by Benoit Moussaud (benoit.moussaud@criltelecom.com)

- - -

Description

-

The BorlandDeployTool is a vendor specific nested element for the Ejbjar optional task.

-

BorlandDeploymentTool is dedicated to the Borland Application Server 4.5.x and Borland - Enterprise Server 5.x. It generates and compiles the stubs and skeletons for all ejb described into the - Deployment Descriptor, builds the jar file including the support files and - verify whether the produced jar is valid or not.

- -

Benoit Moussaud maintains a separate FAQ for this task at -his homepage.

- -

Borland element

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
AttributeDescriptionRequired
destdirThe base directory into which the generated borland - ready jar files are depositedyes
debugIf true, turn on the debug mode for each borland - tools (java2iiop, iastool ...) default = falseno
verifyIf true, turn on the verification at the end - of the jar production (default = false)no
verifyargsextra parameter for verify commandno
suffixString value appended to the basename of the - deployment descriptor to create the filename of the Borland EJB jar file.No, defaults to '-ejb.jar'.
basdtdDeprecated. Defines the location of the - DTD which covers the Borland specific deployment descriptors. - This should not be necessary if you have borland in your classpath. If you - do not, you should use a nested - <dtd> element, described - in the ejbjar task documentation.no
ejbdtdDeprecated. Defines the location of the - ejb-jar DTD in the class hierarchy. This should not be necessary - if you have borland in your classpath. If you do not, you should use a - nested <dtd> element, - described in the ejbjar task - documentation. no
generateclient If true, turn on the generation of the corresponding - ejbjar (default = false)no
versionset the Borland Application Version. -
    -
  • 4 means B.A.S (Borland Application Server) 4.x, target will add ejb-inprise.xml file
    • -
  • 5 means B.E.S (Borland Application Server) 5.x, target will add ejb-borland.xml file
    • -
- 		No, defaults to 4
java2iiopParams If filled, the params are added to the java2iiop command (ex: -no_warn_missing_define)no
- -

Examples

-

The following build.xml snippet is an example of how to use Borland element - into the ejbjar task

-
    <ejbjar srcdir="${build.classes}" basejarname="vsmp" descriptordir="${rsc.dir}/hrmanager">
-        <borland destdir="lib" verify="on" generateclient="on" version="5">
-          <classpath refid="classpath"/>
-        </borland>
-        <include name="**\ejb-jar.xml"/>
-        <support dir="${build.classes}">
-          <include name="demo\*.class"/>
-          <include name="demo\helper\*.class"/>
-         </support>
-     </ejbjar>
-
The borland element will generate into the lib dir an ejb jar file using the deployment descriptor placed into the ${rsc.dir}/hrmanager directory.
-The verify phase is turned on and the generate client phase as well.
-
- -

 

- - - - -- cgit 1.2.3-korg