The "[jboss.naming.context.java.jdbc.kepweb]" part means that there is no java:jdbc/kepweb JNDI entry and the persistence unit refers to it. Do you have one defined with that name in your server profile?
I'm not sure about the Weld one
Did you verify that your deployment scanner is configured and your jdbc drivers were deployed correctly?
You could also try to deploy the drivers manually or as a module. I'd then create a datasource and test the connection to the database.
Hello, thanks for the answer.
Do i have to set the profile in the configuration file located in the next directory?
Since im new on this jboss/wildfly stuff i'ven following some tutorials...
Thanks the jdbc4 was deployed properly. As for now im trying to investigate where to put the profile for java:jdbc/kepweb JNDI Since James wrote that it is one of the problems.,
The configuration should be done in the appropriate file witin the configuration directory (eg standalone.xml)
But it might be more convenient to use jboss-cli or the web administration console for these purposes.
Check your standalone.xml in the <wildfly_home_dir>/standalone/configuration directory. Open the standalone.xml and make your way down to profile tag and then inside it look for datasource subsystem tag. Between opening and ending tags paste the following and fill in information for your datasource. Install the JDBC driver as core module instead of just deploying it.
<xa-datasource jndi-name="java:jboss/MysqlXADS" pool-name="MysqlXADS">
<driver name="mysql" module="com.mysql">