On Jan 10, 2007, at 4:25 AM, Jim Marino wrote:
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.
OK. I see this a really being a spec issue: it says there is a CurrentCompositeContext but does not define how such context is selected.
This is a bad hack so I'd be happy if we could come up with something better.
OK. I think this would also impact the standalone runtime - currently we just use the root jar supplied and execute it's main() method but I can see that that might not always be what we need to do. Perhaps we could add a manifest entry to that jar saying what the current context should be (e.g. through it's URI).
-- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
