[jboss-as7-dev] Parallel initialization of more web applications in EAR

David M. Lloyd david.lloyd at redhat.com
Mon Jan 30 17:27:32 EST 2012


I think it is safe to say that it is our general policy to adhere to 
spec behavior.  If an application is incorrect by spec, but happens to 
work with one app server, there can be no reasonable expectation for it 
to always work.  This is because without a clear and specific additional 
specification which explains the deviating behavior, there is no way we 
can make any guarantees about compatibility.

I don't foresee us, now or in the future, bending over backwards to 
guarantee permanent compatibility of non-spec-compliant apps (whether 
the spec is the Java EE spec or any additional guarantees or 
specifications we have implemented).

In other words... without this switch there is no guarantee specified or 
implied about initialization order.  Our policy will generally be 
"whichever order is the fastest possible while respecting dependencies, 
disregarding all other factors".

On 01/30/2012 04:16 PM, Marek Novotny wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Well, I would like a confirmation that this behavior is by design and if
> application requires specific order you have to do it by configuration
> in application.xml. So for every such old application you need to do a
> migration.
>
> I haven't found any JBoss AS 7 documentation about it so it was my
> question that I got it correctly ;-)
>
> Dne 30.1.2012 23:10, Stuart Douglas napsal(a):
>> I'm not really sure what you are asking here, as far as I have see you have answered your own question, just use<initialize-in-order>true</initialize-in-order>  to get non-parallel startup.
>>
>> Stuart
>>
>>
>>
>> On 31/01/2012, at 8:59 AM, Marek Novotny wrote:
>>
>> Hi AS developers,
>>
>> I am exploring the behavior of parallel initialization of web
>> application in EAR. More concretely more than one web application in EAR.
>> I know that spec doesn't define the initialization order of EAR
>> submodules, but the parallel initialization of web application is new in
>> AS7 and this breaks the backward compatibility for existing enterprise
>> applications with multiple wars inside. New Java Enterprise  application
>> 6 configuration setting<initialize-in-order>true</initialize-in-order>
>> set up in application.xml can enable proper initialization flow, but
>> without it is not possible to deploy.
>>
>> Could somebody shed light on parallel web applicaiton init? Original
>> forum post https://community.jboss.org/message/635123
>>
>> And details could be seen also at
>> https://issues.jboss.org/browse/JBSEAM-4856?focusedCommentId=12662448&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12662448
>>
>> Cheers,
>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
> - --
> Marek Novotny
> - --
> JBoss Seam and WFK Productization Lead
>
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno
>
> Email: mnovotny at redhat.com
> Office phone: +420 532 294 287, ext. 82-62 087
> mobile: +420 608 509 230
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk8nFtgACgkQU4HO8G8hNxVlygCdEVkM8U8/yZa2//+CnQBfihbs
> Ww0AoL20NWPah/e6XOMT1g9Juw5slOpB
> =jivl
> -----END PGP SIGNATURE-----
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


-- 
- DML


More information about the jboss-as7-dev mailing list