Tim,

I made some extra investigation to this issue and find it out that:
If you uninstall a previous release of XAware you should
remove the Xware-Home directory manually to be able to run the SF
bizComponents with the latest changes. You may leave your
previous workspace as it is. This brings no problem but do not forget
to remove the XAware-Home directory else you will not be able to run SF
BizComp with the latest version.

Regards,
Murat

Murat,

Thanks for the info, I'll need to look into the code for updating the Salesforce plugin and see if this is a problem there. The uninstaller does not remove the files because it is configured to not remove files that it did not install - thus preserving any files that a user has added on their own. Perhaps that should be changed as well. Regardless thanks for the follow up.

-Tim

Dennis, I can't seem to replicate this problem with my test cases. Could you try something for me? Remove the xa:on_validation_error="xa-doc::/tns:notificationsResponse/ValidationError" attribute from your BizDoc. Redeploy and try again and see if it still errors out.

In my test cases, I can't seem to get validation to even kick in while running through the SOAP servlets. This appears to be a bug we'll need to address.

Hi Kirstan,

I tried that and it does not error out anymore after that.
However the response sent back to SF is not accepted, probably
because the BizDocument does not use the correct namespace prefix
in the elements.

If I put back the xa:on_validation_error and look at the error
and it looks like the BizDocument does not accept the SF outbound
message because it does not recognize the elements in the message.

How does XAware perform the lookup for the xsd (from the wsdl) for
the incoming message. Do I need to register the sf namespace
and provide a hint on its location (only xsd is allowed here)?
If this was about explicit XSD the file would have been
specified in the BizDoc right?

Thanks!

Kind regards,

Dennis

Thanks for looking at this some more, Dennis. I think its important to prove that we can get this working with the 5.3 release. You mention Salesforce may not like the prefix. You should be able to control this when you create the BizDoc (edit the namespace entry and select the prefix that SF likes). Could you try this?

Schema validation does rely on the server being able to find the XSD. It should find this based on the xsi:schemaLocation attribute on the root of the BizDoc. So, whatever that points to needs to be accessible in the server environment.

Thanks,

-Kirstan