On 9/12/11 5:33 PM, Bill Shannon wrote:
> Jevgeni Kabanov wrote on 09/10/11 11:54 AM:
>> I meant exactly that the Java EE app uses the API to configure its
>> environment in the container. Just as an idea, why not add a
>> "Configurer" that runs before the app is deployed and sets up the
>> environment (including both the standard parts of environment and
>> the container-specific parts) against a standardized Java API with
>> optional container-specific extensions. Most containers already
>> have some internal API representation anyway, so this would not be
>> too hard complicated to implement.
>
> I think it would be a huge challenge to get agreement among all the
> app server vendors on how to do this. There are so many issues, it's
> hard to know where to start...
>
> Do you want the Configurer to be able to select the JVM parameters?
> Sorry, I'm not going to restart the server just for this app.
>
> What happens if the deployment fails after the Configurer has run? Do
> you undo whatever it did? How? What are the limits on what it can
> do?
>
> If the app is being deployed to a cluster, where does the Configurer
> run? On the admin server? On some instance of the cluster? On every
> instance of the cluster? What if the cluster is not created until the
> application is deployed?
Exactly. A declarative model is superior since it allows the container
to worry about these things, and grants it the ability to do them in an
optimal manner.
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat