[jboss-dev-forums] [Design the new POJO MicroContainer] - Deployer meta data don't specify XML element order

thomas.diesler@jboss.com do-not-reply at jboss.com
Fri Jul 3 04:25:34 EDT 2009


After an upgrade to jbossxb-2.0.1.GA I see


  | Caused by: java.lang.IllegalStateException: Cannot deploy beans from: bundle://10.0:1/META-INF/base-deployers-beans.xml
  | 	at org.jboss.osgi.microcontainer.internal.EmbeddedKernelBootstrap.deploy(EmbeddedKernelBootstrap.java:79)
  | 	at org.jboss.osgi.microcontainer.internal.MicrocontainerServiceImpl$1.addingService(MicrocontainerServiceImpl.java:141)
  | 	at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030)
  | 	at org.osgi.util.tracker.ServiceTracker$Tracked.trackInitialServices(ServiceTracker.java:891)
  | 	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:296)
  | 	at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:235)
  | 	at org.jboss.osgi.microcontainer.internal.MicrocontainerServiceImpl.start(MicrocontainerServiceImpl.java:160)
  | 	at org.jboss.osgi.microcontainer.internal.MicrocontainerServiceActivator.start(MicrocontainerServiceActivator.java:47)
  | 	at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589)
  | 	at org.apache.felix.framework.Felix.startBundle(Felix.java:1461)
  | 	... 26 more
  | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: bundle://10.0:1/META-INF/base-deployers-beans.xml@8,49
  | 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:177)
  | 	at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:147)
  | 	at org.jboss.osgi.microcontainer.internal.EmbeddedXMLDeployer.deploy(EmbeddedXMLDeployer.java:140)
  | 	at org.jboss.osgi.microcontainer.internal.EmbeddedKernelBootstrap.deploy(EmbeddedKernelBootstrap.java:74)
  | 	... 35 more
  | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Property order is not specified for type org.jboss.beans.metadata.plugins.AbstractDependencyValueMetaData bound to a sequence. Property order can be specified using @XmlType.propOrder or @XmlAccessorOrder. List of properties: underlyingValue classShortName
  | 

AFAICT, this is due to a missing xml element order spec in the meta data.

Is this a known (perhaps already fixed) issue?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241651#4241651

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241651



More information about the jboss-dev-forums mailing list