Dan,
Thank you for your reply.
> IBindingFactory factory = BindingDirectory.getFactory(clazz);
> String[][] abstractMappings = factory.getAbstractMappings();
> String stype = abstractMappings[0][0]; <--- This Line
This time, I have not described abstract mapping.
Although I also read that code, when normal mapping is adopted,
is going into this method itself irregular?
First of all, is it related although the XML schema is not generated this
time?
Although the judgment of JibxDataBinding (91) was made to skip compulsorily
in the viewpoint
(using debug tool), it is that unmarshal after marshal goes error (finally,
SOAP FAULT).
the code is:
for (ServiceInfo serviceInfo : service.getServiceInfos()) {
SchemaCollection schemaCollection =
serviceInfo.getXmlSchemaCollection();
if (schemaCollection.getXmlSchemas().length > 1) { <--- This
Line
// Schemas are already populated.
continue;
}
Collection<DOMSource> schemas = getSchemas();
if (schemas != null) {
for (DOMSource source : schemas) {
addSchemaDocument(serviceInfo, schemaCollection,
(Document)source.getNode(), source
.getSystemId());
}
}
JibxSchemaInitializer schemaInit = new
JibxSchemaInitializer(serviceInfo, schemaCollection,
this);
schemaInit.walk();
}
--
View this message in context:
http://cxf.547215.n5.nabble.com/Trouble-using-jibx-databinding-in-CXF-2-5-1-using-Mule-3-3M2-tp5518176p5520509.html
Sent from the cxf-user mailing list archive at Nabble.com.
