[sguilhen]

One of the details I have to address has to do with schema validation. Is there any way to express a <xsd:choice> using the annotations? I'm asking because security policies should either have an authentication or an <authentication-jaspi> element, but never both simultaneously. How do I express this kind of restriction?

[alesj]

One of the details I have to address has to do with schema validation. Is there any way to express a <xsd:choice> using the annotations? I'm asking because security policies should either have an authentication or an <authentication-jaspi> element, but never both simultaneously. How do I express this kind of restriction?

I see a bunch of xsd:choice usage here:
- http://anonsvn.jboss.org/repos/jbossas/projects/microcontainer/trunk/kernel/src/resources/main/schema/bean-deployer_2_0.xsd
but I don't think we do any special treatment / annotations in the code.

You can do this programmatically, as we do it in certain places:
- http://anonsvn.jboss.org/repos/jbossas/projects/microcontainer/trunk/kernel/src/main/org/jboss/beans/metadata/plugins/AbstractBeanMetaData.java
see initialVisit method.

You can put this just before you create your security bean metadata.

[alesj]

Probably this post explains it best, why there is no special annotations. ;-)
- http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144891#4144891

[sguilhen]

Hey Ales, thanks again for the pointers. Adrian's post makes sense as validation is separate from XML mapping.

I'll do the validation programmatically like you suggested ;)

[anil.saldhana]

Stefan,
remember to change in the following:

AS/testsuite/src/resources/test-configs

as well as cts config

[anil.saldhana]

AS/testsuite/src/resources/test-configs/jacc has been fixed with security-policies-service.xml to se.....-beans.xml

cts should be updated.....