JBossDeveloper

Another issue is the need to parse multiple documents into one object instance. This shows up in the org.jboss.test.xml.metadata.JBossEjbObjectFactoryUnitTestCase test where both the standardjboss.xml and jboss.xml need to go into the JBoss50MetaData override.

I'm looking into how that can be handled.

"alesj" wrote:

I guess this is related:
- http://jira.jboss.com/jira/browse/JBMICROCONT-184

I can look at this first thing in the morning, and we can discuss it during the MC call?

A bigger problem is lack of support for dom Elements as is needed for the standardjboss.xml proxy-factory-config elements. The content of these depends on the invoker type:

 <proxy-factory-config>
 <client-interceptors>
 <home>
 <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
 <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
 <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
 <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
 <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
 </home>
 <bean>
 <interceptor>org.jboss.proxy.ejb.EntityInterceptor</interceptor>
 <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
 <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
 <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
 <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
 </bean>
 <list-entity>
 <interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</interceptor>
 <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
 <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
 <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
 <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
 </list-entity>
 </client-interceptors>
 </proxy-factory-config>

...

 <proxy-factory-config>
 <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
 <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
 <CreateJBossMQDestination>false</CreateJBossMQDestination>
 <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
 <MinimumSize>1</MinimumSize>
 <MaximumSize>15</MaximumSize>
 <KeepAliveMillis>30000</KeepAliveMillis>
 <MaxMessages>1</MaxMessages>
 <MDBConfig>
 <ReconnectIntervalSec>10</ReconnectIntervalSec>
 <DLQConfig>
 <DestinationQueue>queue/DLQ</DestinationQueue>
 <MaxTimesRedelivered>10</MaxTimesRedelivered>
 <TimeToLive>0</TimeToLive>
 </DLQConfig>
 </MDBConfig>
 </proxy-factory-config>

I raised this http://jira.jboss.com/jira/browse/JBXB-109 issue which has a failing test.

"adrian@jboss.org" wrote:

Why do you need to merge standardjboss.xml?

standardjboss.xml should just be parsed once into a JBossMetaData
and then it should just be a case of delegating.

If you merge standardjboss.xml into the JBossMetaData then you'll loose the
reversability. Let's not make the same mistakes as the old metadata did!

"adrian@jboss.org" wrote:

This is how you define it generically

public class ListElementWildcard
{
 private List<Element> wildcard;

 public List<Element> getWildcard()
 {
 return wildcard;
 }

 @XmlAnyElement(lax=true)
 public void setWildcard(List<Element> wildcard)
 {
 this.wildcard = wildcard;
 }

You can also make it recognise specific types, e.g. we could define
the known JMSContainerInvoker config, etc. by adding @XmlElements
and specific types but then you need to make

List<Object>

if you also want it to have raw Elements as well as real types.

The real problem is that it just isn't implemented
(at least in the version in the JBossXB project)

@XmlType(name="invoker-proxy-bindingType")
public class InvokerProxyBindingMetaData extends NamedMetaDataWithDescriptions
{
...

 /** The proxy factory config */
 // TODO DOM private Element proxyFactoryConfig;

@XmlType(name="invoker-proxy-bindingType")
public class InvokerProxyBindingMetaData extends NamedMetaDataWithDescriptions
{
 /** The proxy factory config */
 private List<Element> proxyFactoryConfig;
...

 public List<Element> getProxyFactoryConfig()
 {
 return proxyFactoryConfig;
 }

 @XmlAnyElement(lax=true)
 public void setProxyFactoryConfig(List<Element> proxyFactoryConfig)
 {
 this.proxyFactoryConfig = proxyFactoryConfig;
 }
}

Caused by: java.lang.ClassCastException: java.util.ArrayList
at org.jboss.javaee.metadata.support.MappedAnnotationMetaData.add(MappedAnnotationMetaData.java:39)
at org.jboss.xb.builder.runtime.CollectionPropertyHandler.handle(CollectionPropertyHandler.java:133)
... 40 more