Versions Compared

Old Version 18

changes.mady.by.user Simon Laws

Saved on

compared with

New Version 19

changes.mady.by.user Simon Laws

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If an archive is not marked as "contribution explicit deployment" or "contribution implicit deployment" it is assumed to be included within, or otherwise reference by, an SCA contribution. See "Archive Location Scenarios" for ways in which JEE archive can be positioned with respect to SCA contribution.

Deployment Scenarios

  • 1 WAR non-enhanced
  • 2 WAR enhanced
  • 3 WAR enhanced, deployable composite, contribution explicit deployment
  • 4 WAR enhanced, application composite >>>> IS THIS SENSIBLE?
  • 5 WAR enhanced, application composite, contribution exlicit deployment
  • 6 WAR enhanced, application composite, contribution implicit deployment
    *
  • 7 JAR non-enhanced
  • 8 JAR enhanced
  • 9 JAR enhanced, deployable composite, contribution explicit deployment
  • 10 JAR enhanced, application composite >>>> IS THIS SENSIBLE?
  • 11 JAR enhanced, application composite, contribution exlicit deployment
  • 12 JAR enhanced, application composite, contribution implicit deployment
    *
  • 13 EAR non-enhanced
    • WAR non-enhanced
    • JAR non-enhanced
  • 14 EAR implied-enhanced
    • WAR enhanced
    • JAR enhanced
  • 15 EAR implied-enhanced
    • WAR enhanced, application composite
    • JAR enhanced, application composite
      *
  • 16 EAR enhanced
    • WAR non-enhanced
    • JAR non-enhanced
  • 17 EAR enhanced
    • WAR enhanced
    • JAR enhanced
  • 18 EAR enhanced
    • WAR enhanced, application composite
    • JAR enhanced, application composite
      *
  • 19 EAR enhanced, application composite
    • WAR non-enhanced
    • JAR non-enhanced
  • 20 EAR enhanced, application composite
    • WAR enhanced
    • JAR enhanced
  • 21 EAR enhanced, application composite
    • WAR enhanced, application composite (ignores app composite?)
    • JAR enhanced, application composite (ignores app composite?)
      *
  • 22 EAR enhanced, deployable composite, contribution exlicit deployment
    • WAR non-enhanced
    • JAR non-enhanced
  • 23 EAR enhanced, deployable composite, contribution exlicit deployment
    • WAR enhanced
    • JAR enhanced
  • 24 EAR enhanced, deployable composite, contribution exlicit deployment
    • WAR enhanced, application composite
    • JAR enhanced, application composite
      *
  • 25 EAR enhanced, application composite, contribution exlicit deployment
    • WAR non-enhanced
    • JAR non-enhanced
  • 26 EAR enhanced, application composite, contribution exlicit deployment
    • WAR enhanced
    • JAR enhanced
  • 27 EAR enhanced, application composite, contribution exlicit deployment
    • WAR enhanced, application composite
    • JAR enhanced, application composite
      *
  • 28 EAR enhanced, application composite, contribution implicit deployment
    • WAR non-enhanced
    • JAR non-enhanced
  • 29 EAR enhanced, application composite, contribution implicit deployment
    • WAR enhanced
    • JAR enhanced
  • 30 EAR enhanced, application composite, contribution implicit deployment
    • WAR enhanced, application composite
    • JAR enhanced, application composite

...

Artifact location scenarios

When using implementation.jee archive="xyz" what does xyz mean? The artifact location described by these scenarios could equally apply to stand alone war and EJB jar files.

A - EAR is external resource (external)

Not defined in Spec.

General pattern for accessing external EAR fles.

...

<component name="xyz">
<implementation.jee archive="logical ear name"/>
</component>

B - EAR is artifact in same contribution (contribnested)

Spec : The archive attribute specifies a relative path to the Java EE archive that serves as
implementation artifact

<component name="xyz">
<implementation.jee archive="../my.ear"/>
</component>

C - EAR is another contribution (other)

Not defined in Spec.

Not clear how the reference would be formed

<component name="xyz">
<implementation.jee archive="contribution name"/>
</component>

D - EAR is artifact in another contribution (othernested)

Not defined in Spec.

Again not clear how the reference would be formed but it would seem consistent to exploit the contribution export/import mechanism

<component name="xyz">
<implementation.jee archive="contribution name/ear name?"/>
</component>

E - EAR is a self contained contribution (contrib)

Spec : If EAR is a contribution @archive attribute can be left unspecified, and the archive defaults to
be the archive of the contribution itself.

...