"adrian(a)jboss.org" wrote : Looks like a bug to me.
|
I guess this is what we want:
| protected void processManagedDeployment(DeploymentContext context, ManagedDeployment parent)
| throws DeploymentException
| {
| DeploymentUnit unit = context.getDeploymentUnit();
| Map<String, ManagedObject> MOs = getManagedObjects(context);
| ManagedDeployment md = mgtDeploymentCreator.build(unit, MOs, parent);
| for (DeploymentContext childContext : context.getChildren())
| {
| processManagedDeployment(childContext, md);
| }
| }
|
I'll add some tests for deeper-than-root ManagedObjects.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092078#4092078
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092078
I'm having problems getting the service-ref as an Element. I can get all of the service-ref child elements as Elements, but not the service-ref element itself. Seems like the @JBossXmlModelGroup is not behaving the same as the @XmlType used with the InvokerProxyBindingMetaData that used wildcards.
I'll create an example test later. For now I'll take another approach to creating the org.jboss.wsf.spi.serviceref.ServiceRefMetaData.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092063#4092063
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092063