This is so the web app can access the correct composite in a
composite hierarchy. This is used in the legacy case where an
existing Spring app needs to have a bean exposed or an SCA reference
add. For example, if we have a Spring web app we would wrap it as an
implementation type in a composite. The parameter allows the SCA web
app launcher to set the correct composite.
This is a bad hack so I'd be happy if we could come up with something
better.
Jim
On Jan 9, 2007, at 3:29 PM, Jeremy Boynes wrote:
What does this webapp parameter do? Don't we just have one context
deployed in the runtime?
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
