[jboss-dev] WarAnnotationMetaDataDeployer and AOP failures
Ales Justin
ales.justin at gmail.com
Mon Feb 1 16:23:48 EST 2010
I guess you meant this one?
<bean name="EARContentsDeployer" class="org.jboss.deployment.EARContentsDeployer">
<constructor>
<parameter><inject bean="AppParsingDeployer" property="relativeOrder"/></parameter>
</constructor>
<!-- Does the deployment have to end in .ear to process it -->
<property name="requiresEarSuffix">true</property>
</bean>
Deployers in ear-deployer-jboss-beans need revisiting,
to be more input/output based.
On Feb 1, 2010, at 10:01 PM, Jason T. Greene wrote:
> Ales Justin wrote:
>>> On 01/27/2010 04:50 PM, Ales Justin wrote:
>>>> Looking at the code, I don't see a reason why it cannot be at POST_PARSE.
>>>>
>>>> Another thing we can notice from this issue is that deployers ordering
>>>> has changed -- it seems we (already) no longer use relative order for
>>>> ordering.
>>>>
>>> This is not true.
>>
>> You don't know that. ;-)
>> As DependenciesTopologicalDeployerSorter is actually currently not used,
>> and I have no other explanation on why that Web deployer kicked in
>> before AOP deployer -- their relative order was an explicit order hack:
>> AOP = Web + 1.
>
> In case it's relevant, the EAR deployer uses relative order in the case
> of strict (descriptor) ordering.
>
> --
> Jason T. Greene
> JBoss, a division of Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
More information about the jboss-development
mailing list