Page History

...

• 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

EAR location scenarios

When using implementation.jee archive="xyz" what does xyz mean?

1 - EAR is external resource

Not defined in Spec.

General pattern for accessing external EAR fles.

<component name="xyz">
<implementation.jee archive="file://c:/temp/my.ear"/>
</component>

Or, when EAR is available in the JEE container

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

2 - EAR is artifact in same contribution

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>

3 - EAR is another contribution

Not defined in Spec.

Not clear how the reference would be formed

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

4 - EAR is artifact in another contribution

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>

5 - EAR is a self contained contribution

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

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

High level functions to be supported

...