Required annotation check

[Christian Dupuis]

Iterator,

thanks for opening the JIRA issue. I'll make sure that the validation rule will honar every instance of type RequiredAnnotationBeanPostProcessor because if this works with Spring it should work with Spring IDE as well.

Yes because of the internal packages.

Since the validation API is considered as open extension point of Spring IDE that could be used by clients to implement custom validation logic, I think you are right that the usage of internal classes is a little unsatisfying (please note that one can implement a validation rule with only the use of non-internal classes).

Would moving the BeansValidationContext (hmm why not adding a public IBeansValidationContext interface?), AbstractBeanValidationRule and AbstractNonInfrastructureBeanValidationRule into the package org.springframework.ide.eclipse.beans.core.model.v alidation solve your problem? I think we could go ahead and consider these classes 'public API'.

Christian

[iterator]

Christian,

thank you for your fast response.

please note that one can implement a validation rule with only the use of non-internal classes.

I tried this, but got lost in unknown terrain. I am new to the whole eclipse plugin stuff and also new to the Spring IDE extension points. I couldn't find detailed information about the exension points. I found the blog entry http://springide.org/blog/2007/04/05...om-namespaces/
where the linked example is not upto date to the extension points. I read the sources of the existing namespace extensions and found my way but it was not easy. Now I am happy to have also hyperlink and content assist functionality. But with the validation I got into trouble because I do not understand the way it works. Is there any further documentation?

Would moving the BeansValidationContext (hmm why not adding a public IBeansValidationContext interface?), AbstractBeanValidationRule and AbstractNonInfrastructureBeanValidationRule into the package org.springframework.ide.eclipse.beans.core.model.v alidation solve your problem? I think we could go ahead and consider these classes 'public API'.

It would be helpful. But like stated before I do not yet understand the validation API and so I am not sure if I could already do what I want.

[Christian Dupuis]

I created IDE-735 to remind me to move the classes into an public package. Futhermore I will introduce a IBeansValidationContext interface.

I'll try blog about the validation API and some other improvements no later than the Spring IDE 2.0.2 release. We have made some progress in the content assist and hyperlinking area as well.

Christian

[iterator]

Hi Christian,

that sounds good. I am looking forward to read about the validation API. Thank you.

Dirk