Eclipse unable to validate xsd-2.0 ucl, products

amy

pany.integration.from.services.ProductServicequot;
id=quot;productServiceGatewayquot; default-request-channel=quot;productServiceOperationsquot; /gt;

lt;int:channel id=quot;productServiceOperationsquot; /gt;

lt;fromutbound-gateway id=quot;fromGatewayquot;
request-channel=quot;productServiceOperationsquot;
ucl=quot;spring-rs-poc-1.0.0/products/1002quot;
from-method=quot;GETquot; expected-response-type=quot;com.company.integration.from.domain.Productquot; /gt;
lt;bean id=quot;xstreamMarshallerquot; class=quot;org..oxm.xstream.XStreamMarshallerquot;gt;
lt;property name=quot;annotatedClassquot;
value=quot;com.company.integration.from.domain.Productquot; /gt;
lt;/beangt;

lt;/beansgt;
This is however, working on build and deployment as expected.

Please advise.

The problem is that the version of STS you are using has an older version of the 2.0 schema in its plugin.

Even if you upgrade to STS 2.3.2 (which allows you to set an option to find the schemas on the classpath), STS will still use the old schemas that are in the XML Catalog (see browse/INT-1353).

You can detour this by putting the schemas on your filesystem some place and creating manual XML catalog entries (see the above JIRA for an example).

Or, if you update to STS 2.5.0.M3, you will pick up most (but not all) schema updates.

Edit: Oh, and you can play with the new GUI Spring Integration Editor too!

Hi Gary,

Thanks for the quick update. I will upgrade it to 2.5.0.M3, but I could not see any roadmap or a project timeline when we are expecting a RELEASE version for STS. Integration 2 i guess is expected by October, is the new STS expected around the same time?

With STS 2.5.0.M3, there is an option (Window | Preferences | Spring | Beans Support | Namespaces | Load Namespace Handlers and XSDs from project's classpath). It is also settable at the individual project level.

If you set that, STS will always use the schemas in the jars on your classpath.

The option has been available since 2.3.2 and worked for quot;newquot; schemas that were not already in the catalog (the catalog took precedence for existing schemas); it has since been changed so that a classpath schema will take precedence.

Gary,

I tried the steps and though 2.3.2 doesn seem to recognise the integration XSDs, 2.5.0.CI-R5706-B362 did after doing the modification for Namespace Handling as mentioned in your reply.

However, I guess some issues are yet to be fiixed before release, and I just wanted to inform that I am getting this problems:

1. Internal error while quotrocessing Dirty Regionsquot;
2. During quot; Initialise bean graphquot;

The screen shots are attached for your reference. (attachment3.png)

Thanks,

Tanmoy

Thanks for the feedback.

May I ask you to post your new issues here... forumdisplay.php?f=32 ?

Feel free to refer back to this thread there.

Thanks