Lines 20-25
Link Here
|
20 |
<li>Cyrille Morvan (<a href="mailto:cmorvan@ingenosya.com">cmorvan@ingenosya.com</a>)</li> |
20 |
<li>Cyrille Morvan (<a href="mailto:cmorvan@ingenosya.com">cmorvan@ingenosya.com</a>)</li> |
21 |
<li>Greg Nelson (<a href="mailto:gn@sun.com">gn@sun.com</a>)</li> |
21 |
<li>Greg Nelson (<a href="mailto:gn@sun.com">gn@sun.com</a>)</li> |
22 |
<li>Rob van Oostrum(<a href="mailto:rob@springwellfarms.ca">rob@springwellfarms.ca</a>)</li> |
22 |
<li>Rob van Oostrum(<a href="mailto:rob@springwellfarms.ca">rob@springwellfarms.ca</a>)</li> |
|
|
23 |
<li>Per Olesen (<a href="mailto:polesen@nordija.com">polesen@nordija.com</a>)</li> |
23 |
</ul> |
24 |
</ul> |
24 |
|
25 |
|
25 |
<p>Version @VERSION@<br> |
26 |
<p>Version @VERSION@<br> |
Lines 71-76
Link Here
|
71 |
<tr><td><a href="#ejbjar_jonas">jonas</a></td><td>JOnAS 2.4.x and 2.5</td></tr> |
72 |
<tr><td><a href="#ejbjar_jonas">jonas</a></td><td>JOnAS 2.4.x and 2.5</td></tr> |
72 |
<tr><td><a href="#ejbjar_weblogic">weblogic</a></td><td>Weblogic 5.1 to 7.0</td></tr> |
73 |
<tr><td><a href="#ejbjar_weblogic">weblogic</a></td><td>Weblogic 5.1 to 7.0</td></tr> |
73 |
<tr><td><a href="#ejbjar_websphere">websphere</a></td><td>IBM WebSphere 4.0</td></tr> |
74 |
<tr><td><a href="#ejbjar_websphere">websphere</a></td><td>IBM WebSphere 4.0</td></tr> |
|
|
75 |
<tr><td><a href="#ejbclientjar">ejbclientjar</a></td><td colspan="2">Generate a ejb client jar with client-view classes of ejbs</td></tr> |
74 |
<tr><td><a href="#wlrun">wlrun</a></td><td colspan="2">Weblogic 4.5.1 to 7.0</td></tr> |
76 |
<tr><td><a href="#wlrun">wlrun</a></td><td colspan="2">Weblogic 4.5.1 to 7.0</td></tr> |
75 |
<tr><td><a href="#wlstop">wlstop</a></td><td colspan="2">Weblogic 4.5.1 to 7.0</td></tr> |
77 |
<tr><td><a href="#wlstop">wlstop</a></td><td colspan="2">Weblogic 4.5.1 to 7.0</td></tr> |
76 |
|
78 |
|
Lines 315-320
Link Here
|
315 |
</pre> |
317 |
</pre> |
316 |
|
318 |
|
317 |
<hr> |
319 |
<hr> |
|
|
320 |
<h2><a name="ejbclientjar">ejbclientjar</a></h2> |
321 |
<h3><b>Description:</b></h3> |
322 |
|
323 |
<p>The <code>ejbclientjar</code> task is used to generate ejb client jar files from ejbjar files. |
324 |
With the input of a ejbjar file (which can be generated using <a href="#ejbjar">ejbjar</a>, this |
325 |
task analyses the <code>ejb-jar.xml</code> deployment descriptor for classes in the beans client-view. |
326 |
The client-view classes include remote and local interface, pk-class, home and local home and |
327 |
any classes upon which these classes depend, including super-classes, classes used in parameters |
328 |
and exceptions.</p> |
329 |
|
330 |
<p><em>NOTE:</em>This task depends upon the optional |
331 |
<a href="http://jakarta.apache.org/bcel">Byte Code Engineering Library for determining class dependencies</a>, |
332 |
which must be in our ant lib. Please refer to <a href="../install.html#librarydependencies">for a description |
333 |
of installing bcel with ant</a>. |
334 |
|
335 |
<h3>Parameters:</h3> |
336 |
|
337 |
<table border="1" cellpadding="2" cellspacing="0"> |
338 |
<tr> |
339 |
<td valign="top"><b>Attribute</b></td> |
340 |
<td valign="top"><b>Description</b></td> |
341 |
<td align="center" valign="top"><b>Required</b></td> |
342 |
</tr> |
343 |
<tr> |
344 |
<td valign="top">srcdir</td> |
345 |
<td valign="top"> |
346 |
The directory where the task looks for the ejbjar files to generate ejb client jar |
347 |
files from. The task is a <a href="../CoreTypes/fileset.html">FileSet</a>, so when |
348 |
selecting ejbjar files as input, this is the basedir which is searched. |
349 |
</td> |
350 |
<td valign="top" align="center">Yes</td> |
351 |
</tr> |
352 |
<tr> |
353 |
<td valign="top">destdir</td> |
354 |
<td valign="top"> |
355 |
The directory where output ejb client jar files are written. |
356 |
</td> |
357 |
<td valign="top" align="center">Yes</td> |
358 |
</tr> |
359 |
<tr> |
360 |
<td valign="top">manifestclasspathprefix</td> |
361 |
<td valign="top"> |
362 |
The value of this property is prefixed to any "Class-Path" attribute in the manifest in the |
363 |
output ejb client jar. |
364 |
In the process of determining dependencies, this task resolves where to find the files of the |
365 |
dependent classes (by using the nested "classpath" element). If it finds dependent classes |
366 |
in <code>.jar</code> or <code>.zip</code> files, these files are <em>not</em> added to the |
367 |
resulting ejb client jar. Instead, they are referenced using a Class-Path attribute in the manifest. |
368 |
</td> |
369 |
<td valign="top" align="center">No. Default is "lib".</td> |
370 |
</tr> |
371 |
<tr> |
372 |
<td valign="top">clientjarsuffix</td> |
373 |
<td valign="top"> |
374 |
Determines the naming of output ejb client jar files. If this property is set to "-bar", |
375 |
and a input ejb jar file is named "foo.jar", the output ejb client jar is named "foo-bar.jar". |
376 |
</td> |
377 |
<td valign="top" align="center">No. Default is "-client".</td> |
378 |
</tr> |
379 |
</table> |
380 |
|
381 |
<h3>Nested Elements</h3> |
382 |
|
383 |
<p>In addition to the standard nested elements of a <a href="../CoreTypes/fileset.html">FileSet</a>, |
384 |
this task also supports nested <code><classpath></code> and <code><dtd></code> elements.</p> |
385 |
|
386 |
<h4><code>classpath</code></h4> |
387 |
|
388 |
<p>Is the standard <code>classpath</code> element, which is a <a href="../using.html#path">path-like structure</a>. |
389 |
Use this element to give the classpath, that is used to find all client-view classes.</p> |
390 |
|
391 |
<h4><code>support</code></h4> |
392 |
|
393 |
<p>Makes it possible to include other files, which the automatic dependency analyzer does not find. |
394 |
This could for instance be classes which are loaded on demand with <code>Class.forName</code> |
395 |
or it could be resources. The <code>support</code> element is simply a <a href="../CoreTypes/fileset.html">FileSet</a>, |
396 |
and all files matched by the fileset is included in resulting client jar. More than one support element can be |
397 |
specified.</p> |
398 |
|
399 |
<h4><code>dtd</code></h4> |
400 |
|
401 |
<p>Specifies local dtd-locations used when parsing the <code>ejb-jar.xml</code> file. If this element is not |
402 |
specified, the xml parser will try and validate the dtd using whatever the <code>DOCTYPE</code> of the |
403 |
<code>ejb-jar.xml</code> specifies. Use this element if you would like to resolve dtds locally.</p> |
404 |
|
405 |
<p>Parameters:</p> |
406 |
<table border="1" cellpadding="2" cellspacing="0"> |
407 |
<tr> |
408 |
<td valign="top"><b>Attribute</b></td> |
409 |
<td valign="top"><b>Description</b></td> |
410 |
<td align="center" valign="top"><b>Required</b></td> |
411 |
</tr> |
412 |
<tr> |
413 |
<td valign="top">publicId</td> |
414 |
<td valign="top"> |
415 |
Whatever follows <code>PUBLIC</code> in the <code>DOCTYPE</code> of the <code>ejb-jar.xml</code>. |
416 |
</td> |
417 |
<td valign="top" align="center">Yes</td> |
418 |
</tr> |
419 |
<tr> |
420 |
<td valign="top">location</td> |
421 |
<td valign="top"> |
422 |
Where to find the dtd locally. |
423 |
</td> |
424 |
<td valign="top" align="center">Yes</td> |
425 |
</tr> |
426 |
</table> |
427 |
|
428 |
<h3>Examples</h3> |
429 |
|
430 |
<p>This example builds client-view ejb client jar files for all ".jar" files found in <code>${build.ejbs.dir}</code>. |
431 |
The output files are written to <code>${build.clientejbs.dir}</code>, using a <code>-mysuffix</code> suffix |
432 |
and a <code>mylib</code> prefix to the value of any Class-Path attribute in manifest. |
433 |
Any created output files will include property files found in support fileset with basedir |
434 |
<code>${build.classes.dir}</code>.</p> |
435 |
|
436 |
<p>Assuming the <code>${build.ejbs.dir}</code> directory contains the files <code>foo.jar</code> |
437 |
and <code>bar.jar</code>, the output files in <code>${build.clientejbs.dir}</code> will be named |
438 |
<code>foo-mysuffix.jar</code> and <code>bar-mysuffix.jar</code>. Also, if the client-view of bean |
439 |
<code>foo.jar</code> depends upon classes found in <code>xml-apis.jar</code> |
440 |
in the classpath, the manifest of the <code>foo-mysuffix.jar</code> will contain a <code>Class-Path</code> |
441 |
attribute with the value <code>mylib/xml-apis.jar</code>.</p> |
442 |
|
443 |
<pre> |
444 |
<target name="build-clientejbs" depends="build-ejbs"> |
445 |
<ejbclientjar srcdir="${build.ejbs.dir}" destdir="${build.clientejbs.dir}" clientjarsuffix="-mysuffix" manifestclasspathprefix="mylib"> |
446 |
<classpath> |
447 |
<pathelement location="${build.classes.dir}" /> |
448 |
<pathelement location="${lib.dir}/xml-apis.jar" /> |
449 |
<pathelement location="${lib.dir}/xercesImpl.jar" /> |
450 |
<classpath /> |
451 |
<dtd publicid="-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" location="${dtd.dir}/ejb-jar_2_0.dtd" /> |
452 |
<include name="*.jar" /> |
453 |
<support dir="${build.classes.dir}"> |
454 |
<include name="**/*.properties" /> |
455 |
<support /> |
456 |
</ejbclientjar> |
457 |
</target> |
458 |
</pre> |
459 |
|
460 |
<hr> |
318 |
<h2><a name="wlrun">wlrun</a></h2> |
461 |
<h2><a name="wlrun">wlrun</a></h2> |
319 |
<h3><b>Description:</b></h3> |
462 |
<h3><b>Description:</b></h3> |
320 |
|
463 |
|
Lines 546-551
Link Here
|
546 |
<li><a href="http://www.objectweb.org/jonas/">JOnAS</a> 2.4.x and 2.5 Open Source EJB server</li> |
689 |
<li><a href="http://www.objectweb.org/jonas/">JOnAS</a> 2.4.x and 2.5 Open Source EJB server</li> |
547 |
</ul> |
690 |
</ul> |
548 |
|
691 |
|
|
|
692 |
<p>If you want to generate ejb client jars with client-view classes, |
693 |
you can use the <a href="#ejbclientjar">ejbclientjar</a> task.</p> |
549 |
|
694 |
|
550 |
<p>The task works as a directory scanning task, and performs an action for each |
695 |
<p>The task works as a directory scanning task, and performs an action for each |
551 |
deployment descriptor found. As such the includes and excludes should be set |
696 |
deployment descriptor found. As such the includes and excludes should be set |