problems with multiple pluggable schema's

[bill.burke]

I have the following XML:

<aop xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:jboss:aop-deployer aop-deployer_1_1.xsd"
 xmlns="urn:jboss:aop-deployer">

 <interceptor name="SimpleInterceptor">
 <bean xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd"
 xmlns="urn:jboss:bean-deployer" class="org.jboss.test.kernel.SimpleInterceptor">
 <constructor>
 <parameter>Hello</parameter>
 </constructor>
 <property name="second">World</property>
 </bean>
 </interceptor>
</aop>

How can I get at the child bean element in the interceptor's ElementHandler? I want to generically obtain this information. AM I making sense?

Thanks

[aloubyansky]

No way. Currently, SAX events are sent to handlers immediately. So, when interceptor's ElementHandler.startElement is invoked there is no info about bean element available (has not been parsed yet).
We could implement something like look-ahead but before doing that I would like to have convincing arguments.
Why would want to do that?

[starksm64]

Getting access to the bean element does not make sense as presumably the aop:interceptor element has an arbitrary content model given that you are showing an xml fragment from seperate a namespace. The contract between the aop layer and its interceptor plugins has to be either through an interface contract, or a reflection contract like the JavaBean one.

Why would you need specific knowledge of the interceptor configuration? This is essentially equivalent to knowing what constructor was used to create an instance of some interface.

[adrian.brock]

I already added this issue to JIRA, but this will be done after MC 1.0.0/JBossAS 4.0.3
http://jira.jboss.com/jira/browse/JBMICROCONT-42

The basics are to separate

<bean>

and

<deployment>

into different schemas
such that aop can reuse the

<bean>

via the ANY/annotation based parsing.
http://jira.jboss.com/jira/browse/JBMICROCONT-32