[Design the new POJO MicroContainer] - Wildcards and JBossXb Builder
by alesj
Reading through Kabir's AOP work on jaxb-ing his metadata:
"adrian(a)jboss.org" wrote :
| You should let the MC schema define the {urn:jboss:bean-deployer:2.0}bean
| and use it as a "wildcard".
|
I'm jaxb-ing our PolicyMetaData, having this in AbstractBindingMetaData:
| @XmlTransient
| public void setValue(ValueMetaData value)
| {
| this.value = value;
| }
|
| @XmlAnyElement
| public void setValueObject(Object value)
| {
| if (value == null)
| setValue(null);
| else if (value instanceof ValueMetaData)
| setValue((ValueMetaData) value);
| else
| setValue(new AbstractValueMetaData(value));
| }
|
| @XmlValue
| public void setValueString(String value)
| {
| if (value == null)
| setValue(null);
| else
| {
| ValueMetaData valueMetaData = getValue();
| if (valueMetaData instanceof StringValueMetaData)
| {
| ((StringValueMetaData) valueMetaData).setValue(value);
| }
| else
| {
| StringValueMetaData stringValue = new StringValueMetaData(value);
| stringValue.setType(getType());
| setValue(stringValue);
| }
| }
| }
|
and I'm getting this exception:
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:bean-deployer:2.0}value not found as a child of {urn:jboss:policy:1.0}binding
|
I thought the @XmlAnyElement will handle this as a wildcard?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133637#4133637
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133637
17 years, 7 months
[Design of JBoss Build System] - Re: JBossAS CR1 build plan
by wolfc
You're forgetting jboss-as-server and the transitive dependencies.
Which means we pull in almost all the AS components.
I can send the dependency graph around again. :-)
Aspects should be a library component. It has nothing to do with AS. They should be pojo aspects for use in any container environment. Maybe an extension component for MC?
I'm not sure why we depend on the JCA implementation. We invoke the resource adapter through the MC. So the API should be enough (possibly some JCA API extentions).
Iiop is an extension and could be separated out. It still requires an AS lib component though.
Naming should be jnpserver (already fixed by Scott).
I think the deployers and client launcher depend on jboss-as-server. Both should be moved from ejb3 to AS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133627#4133627
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133627
17 years, 7 months