1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162 |
- <?xml version="1.0" encoding="UTF-8"?>
- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
- targetNamespace="urn:security:1.1"
- xmlns="urn:security:1.1"
- xmlns:javaee="http://java.sun.com/xml/ns/javaee"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd">
- <xs:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd"/>
- <xs:element name="security" type="securityType" substitutionGroup="javaee:assembly-descriptor-entry"/>
- <xs:complexType name="securityType">
- <xs:complexContent>
- <xs:extension base="javaee:jboss-assembly-descriptor-bean-entryType">
- <xs:sequence>
- <xs:element name="security-domain" type="xs:string"/>
- <xs:element name="run-as-principal" type="xs:string"/>
- <xs:element name="missing-method-permissions-deny-access" type="xs:boolean">
- <xs:annotation>
- <xs:documentation>
- <![CDATA[
- If a EJB is secured but certain methods haven't been marked with explicit roles or @PermitAll/@DenyAll
- then the EJB container uses this missing-method-permissions-deny-access element to decide whether or not
- access is allowed to such methods.
- Setting this element to true will prevent access to this by any role (i.e.
- the method is as good as being marked as @DenyAll).
- Setting this element to false will allow access to this method by any role (i.e. the method is as
- good as being marked as @PemitAll)
- ]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- </xs:schema>
|