when a session bean(2.1) is to be deployed , i had given in jboss-ejb3.xml
<?xml version="1.1" encoding="UTF-8"?>
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
version="3.1"
impl-version="2.1">
<enterprise-beans>
<session>
<ejb-name>SESSSAMP</ejb-name>
<ejb-class>com.jee.ejbs.SessBean</ejb-class>
</session>
</enterprise-beans>
</jboss:ejb-jar>
it is showing following validation errors
The errors below were detected when validating the file "jboss-ejb3-2_0.xsd" via the file "jboss-ejb3.xml". In most cases these errors can be detected by validating "jboss-ejb3-2_0.xsd" directly. However it is possible that errors will only occur when jboss-ejb3-2_0.xsd is validated in the context of jboss-ejb3.xml.
src-resolve:can not resolve the name javaee:jboss-ejb-beanType to a(n) 'type definition' component -line 34
src-resolve:can not resolve the name javaee:jboss-ejb-jarType to a(n) 'type definition' component -line 36
src-resolve:can not resolve the name javaee:jboss-enterprise-beansType to a(n) 'type definition' component -line 38
this is a plain simple configuration,even without this file ,it is running,but for MDBs,ejb inter-communications,how this file is to be written
There is unfortunately a known bug in eclipse that causes some of the JEE schemas to get invalid error markers.
I assume that is where you are seeing the errors?
if it is during runtime deployment on wildfly I suggest you ask in the wildfly forums.