Surely you can just register it like that, but also put the name of the
Wicket application (getName()) in the attribute key?
Of course, that requires you to pass in the name of the Wicket app to
your Seam stuff somehow, but if you want to support running multiple
apps in a single context then you'll need to disambiguate them somehow
anyway, so that doesn't seem unreasonable.
Hey Al. I already fixed it by rolling back. Applications were already
put in a static map, and the keys of that map are exposed now as well.
That way, you can at least detect whether there is *some* Wicket app
running, and extensions projects like wicket-seam can attach to the
application if there is only one, or complain it needs more
configurtion if there are multiple.
Eelco
