Thanks Raymond for pointing it out. I made a change to the
ExtensibleURLArtifactProcessor.read to set the monitor artifact name to null
before calling processor.read. This solve my OASIS test running problem on
ASM_12012. I will open a JIRA and attach my fixed code.
One thing I do want to point ou
Maybe we should have the ExtensibleURLArtifactProcessor to set the artifact
name before it delegates the real processor.
Raymond Feng
rf...@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany
ASM_10003 is related to DefinitionsProcessor. In tuscany's error message it
is using Test_ASM_10003.composite, while in my environment for some reason
the composite file may not have been processed, so I get the definition
file's input name (the file uri from a jar) as the artifact name.
ASM_12012
On Fri, Oct 1, 2010 at 2:27 PM, Yang Lei wrote:
> I was running oasis compliance test in another hosting environment, I
> noticed some test result validation differences from what Tuscany defined in
> the error message files. I think these differences may expose an issue
> on how we maintain the a
I was running oasis compliance test in another hosting environment, I
noticed some test result validation differences from what Tuscany defined in
the error message files. I think these differences may expose an issue
on how we maintain the artifact name in the MonitorImpl.
I noticed that not all
