ejb

来源： https://stackoverflow.com/questions/63750741/ejb-websocket-handshake-error-response-code-was-not-101-404

来源： https://stackoverflow.com/questions/63750741/ejb-websocket-handshake-error-response-code-was-not-101-404

问题 Does anyone experience the following issue? I'm able to successfully build, deploy and run my javaee6 application in jboss inside eclipse using jboss tools. But when we deployed it on another server running on standalone we got an error. I tried it the same machine where eclipse is and run on jboss as standalone and got the same error. See error below, I've removed some parts. 06:53:46,423 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-1) Transaction cannot

问题 Does anyone experience the following issue? I'm able to successfully build, deploy and run my javaee6 application in jboss inside eclipse using jboss tools. But when we deployed it on another server running on standalone we got an error. I tried it the same machine where eclipse is and run on jboss as standalone and got the same error. See error below, I've removed some parts. 06:53:46,423 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-/127.0.0.1:8080-1) Transaction cannot

问题 I am quite new to JavaEE and tried to get a little Hello World example running (https://ibytecode.com/blog/how-to-create-a-simple-ejb3-project-in-eclipse-jboss-7-1/), but I am stuck with an Exception in thread "main" javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/HelloWorldSessionBean/HelloWorldBean", view is interface com.ibytecode.business.HelloWorld, affinity is None It is probably only some beginner's error, but

问题 I am quite new to JavaEE and tried to get a little Hello World example running (https://ibytecode.com/blog/how-to-create-a-simple-ejb3-project-in-eclipse-jboss-7-1/), but I am stuck with an Exception in thread "main" javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/HelloWorldSessionBean/HelloWorldBean", view is interface com.ibytecode.business.HelloWorld, affinity is None It is probably only some beginner's error, but

问题 I'm designing my database and I reached the situation that an Entity itself requires to access database. I read Why sometimes a reference to an EntityManager inside JPA entities is needed. And I'm curious about the possibility of accessing an EJB in EntityListener. public class MyEntityListener { @PrePersist private void onPrePersist(final Object object) { // find an EJB // and set those required values // which each resides in a specific table. } } Is this possible or (or and) preferred? 回答1

问题 I know Stateless EJBs are stored in a pool and instantiated as needed, my question is, what happens when there are more EJB dependencies, for example with something like this: @Remote @Stateless public class Master_EJB{ @EJB private EJB_A ejb_A; @EJB private EJB_B ejb_B; } With EJB_A and EJB_B also being stateless EJBs. In the worst case, if there are two petitions at exactly the same time, the server will retrieve two instances of Master_EJB from the pool (or create if needed). But if from

问题 We are migrating an Application consisting of several ear files from Weblogic 11 to Weblogic 12. Three of the ear files are running well, when we deploy the 4th it throws a ClassNotFoundException on startup. Two of the three running ears aren’t important in this regard. So, the situation is that A.ear runs fine, B.ear fails to start. B.ears pom.xml refers to a module of A.ear as dependency with provided and ejb-client, and using maven-ear-plugin it refers to the module as ejbClientModule. Due

问题 I am migrating EJB application from websphere 9.0 to Liberty. I am using the application server migration utility to help me with the migration. One of the listed issue is: Ported locally transacted JMS sessions do not work in Liberty I checked the details mentioned in the help, but I could not understand much from the details. 回答1: JMS sessions in general will work in Liberty. However, transacted JMS sessions won't work. Therefore, applications using transacted JMS sessions which are ported