don't waste your time while looking for public jndi that belong to your sessinbean while calling it locally in weblogic environment. weblogic don't support jndi with local beans even if you type mappped name in that class like package tr.gov.ibb.core.model.session; import java.util.List; import javax.ejb.Remove; import javax.ejb.Stateful; import javax.ejb.TransactionAttribute; import javax.ejb.TransactionAttributeType; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import javax.persistence.PersistenceContextType; import javax.persistence.Query; import tr.gov.ibb.core.model.entity.Musteri; @Stateful(name = "TestBean", mappedName = "ejb/TestBean") @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) public class TestBean implements TestRemote,TestLocal { @PersistenceContext(unitName = "CoreContextWithoutEUS", type = PersistenceContextType.EXTENDED) private EntityManager em; public List getMusteriList...
This journey is all about
* Edge stack like Scala,Spark,Kafka etc
* Cloud(Kubernetes,Docker,CloudFoundry etc)
* Historically it was about mainly on JEE, SOA, BPEL/BPM but now mainly on Microservices