cvc-complex-type.3.2.2

[mjafari]

I work with sts 2.6.1, spring 3.0.5 and Spring-integration 2.0.0.
I see cvc-complex-type.3.2.2 error in IDE syntaxt checking frequently.

for example in:

<integration:service-activator input-channel="ch"
                                   expression="@eventCacheAspect.invalidateCache(payload)"/>

error is related to expression attribute.

and in:

    <jms:message-driven-channel-adapter channel="ch2"
                                        destination-name="dest"
                                        pub-sub-domain="true"
                                        error-channel="errorChannel"/>

error is assigned to error-channel attribute.

CAUTION: jms and integration namespaces are defined and corresponding maven dependencies are defined so required jar files exist in classpath.

[Martin Lippert]

I added a JIRA issue to track these things:
https://issuetracker.springsource.com/browse/STS-1772

Cheers,
-Martin

[Martin Lippert]

Hi!

Can you post the header of your config file? I just wanna make sure that I have the same setup when debugging this one. Right now, I am not able to reproduce these erros.
Thanks!!!

Cheers,
-Martin

[mjafari]

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:context="http://www.springframework.org/schema/context"
       xmlns:tx="http://www.springframework.org/schema/tx"
       xmlns:aop="http://www.springframework.org/schema/aop"
       xmlns:integration="http://www.springframework.org/schema/integration"
       xmlns:jms="http://www.springframework.org/schema/integration/jms"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
                           http://www.springframework.org/schema/beans/spring-beans.xsd
                           http://www.springframework.org/schema/context
                           http://www.springframework.org/schema/context/spring-context.xsd
                           http://www.springframework.org/schema/tx
                           http://www.springframework.org/schema/tx/spring-tx.xsd
                           http://www.springframework.org/schema/aop
                           http://www.springframework.org/schema/aop/spring-aop-2.0.xsd http://www.springframework.org/schema/integration http://www.springframework.org/schema/integration/spring-integration.xsd http://www.springframework.org/schema/integration/jms http://www.springframework.org/schema/integration/jms/spring-integration-jms.xsd">

You are welcome.

[mjafari]

I believe that STS-1772 is an important bug because it annoys user in his day to day usage of STS.

I have surprised that after 60 day and a major release of STS this issue hasn't been resolved.
Additionally I couldn't sign up to springsource.com issue manager (to write this message as STS-1772 comment).
Is its membership is private?

[mjafari]

I can guess the problem.
In my experiences these bugs occur only when I use .xsd without version (e.g. spring-integration-jms.xsd instead of spring-integration-jms-2.0.xsd).
In spring jar files META-INF folder exists a file with name spring.schemas that maps schema urls to their locations in jar file.
In this file (e.g. spring-integration-jms-2.0.1.RELEASE.jar) you see:

http\://www.springframework.org/schema/integration/jms/spring-integration-jms-1.0.xsd=org/springframework/integration/jms/config/spring-integration-jms-1.0.xsd
http\://www.springframework.org/schema/integration/jms/spring-integration-jms-2.0.xsd=org/springframework/integration/jms/config/spring-integration-jms-2.0.xsd
http\://www.springframework.org/schema/integration/jms/spring-integration-jms.xsd=org/springframework/integration/jms/config/spring-integration-jms-2.0.xsd

that means that using both spring-integration-jms-2.0.xsd and spring-integration-jms.xsd should be ends using same file.
Probably STS ignores this file or parses and uses it in a incorrect manner.

[Martin Lippert]

I believe that STS-1772 is an important bug because it annoys user in his day to day usage of STS.
I have surprised that after 60 day and a major release of STS this issue hasn't been resolved.

I think this is an important issue, but we already improved this quite a bit with the latest release. Nevertheless there are still some issues (as pointed out here) that we will adress.

Additionally I couldn't sign up to springsource.com issue manager (to write this message as STS-1772 comment).
Is its membership is private?

Its not private, but you need to sign-up for an account here:
https://issuetracker.springsource.co...p!default.jspa

After that you should be able to login and create and comment issues.
It would especially be great to get a zipped sample STS project that illustrates the problems. Please feel free to create such a project and attach that to STS-1722. That would be much appreciated.

Thanks!
Martin

[Martin Lippert]

I can guess the problem.
In my experiences these bugs occur only when I use .xsd without version (e.g. spring-integration-jms.xsd instead of spring-integration-jms-2.0.xsd).
In spring jar files META-INF folder exists a file with name spring.schemas that maps schema urls to their locations in jar file.
In this file (e.g. spring-integration-jms-2.0.1.RELEASE.jar) you see:

http\://www.springframework.org/schema/integration/jms/spring-integration-jms-1.0.xsd=org/springframework/integration/jms/config/spring-integration-jms-1.0.xsd
http\://www.springframework.org/schema/integration/jms/spring-integration-jms-2.0.xsd=org/springframework/integration/jms/config/spring-integration-jms-2.0.xsd
http\://www.springframework.org/schema/integration/jms/spring-integration-jms.xsd=org/springframework/integration/jms/config/spring-integration-jms-2.0.xsd

that means that using both spring-integration-jms-2.0.xsd and spring-integration-jms.xsd should be ends using same file.
Probably STS ignores this file or parses and uses it in a incorrect manner.

This is an interesting observation since this should work in STS. Please setup a sample project and attach it to the bug so that we can track this down. That would help a lot.

Thanks!
Martin

[Martin Lippert]

In many cases the reason for this problem is that the project doesn't have the Spring Nature enabled. Only Spring projects get the classpath-based namespace resolution and should therefore be able to lookup the correct namespace. So in most cases the errors go away after enabling the Spring Nature for that project via the context Spring menu.

HTH,
Martin