Excellent! Just what I was looking for. Thanks.
Raymond Feng wrote:
There is a validation framework that reports issue through the Monitor.
See the org.apache.tuscany.sca.assembly.builder.impl.BaseBuilderImpl in
assembly module. For example,
protected void warning(Monitor monitor, String message, Object model,
String... messageParameters) {
if (monitor != null) {
Problem problem =
monitor.createProblem(this.getClass().getName(),
"assembly-validation-messages", Severity.WARNING, model, message,
(Object[])messageParameters);
monitor.problem(problem);
}
}
Thanks,
Raymond
--------------------------------------------------
From: "Dan Becker" <[email protected]>
Sent: Tuesday, January 13, 2009 2:11 PM
To: <[email protected]>
Subject: Re: WSDL Binding validation scenario
Raymond Feng wrote:
binding.ws allows the configuration of @wsdlElement to point to the
above models in the WSDL using QNames. I think the JIRA complains
that if the QName cannot be resolved a model defintion in the WSDL,
we should have meaningful messages to report that. For example, if we
have:
<binding.ws wsdlElement="http://ns1#wsdl.port(service1/port1)"/>
If there is no WSDL defines a port "port1" under a service "service1"
with "http://ns1"; namespace, we should report the problem instead of
NPE.
Agreed. Do any of the components or their test cases demonstrate
validation of a wsdlElement? I see various method calls for reading or
writing a composite to/from XML, do you recall any methods for
validating? (I guess my question is, does the existing code have a
validation framework, and perhaps this wsdlElement validation is
missing from the framework, or does a validation framework currently
not exist?)
--
Thanks, Dan Becker
--
Thanks, Dan Becker
