-------------------------------------------------- --------------- JMS: ------------------------------- -------------------------------- ◎ JMS After issuing a message, the server will immediately ring the user request ◎ JMS can put In the local, you can also put it in remote other servers ◎ Multiple recipients, multiple senders ◎ The so-called binding is that your server side must tell the other party to communicate ◎ Targeting the definition of the setup and interface ◎ loose Binding does not need to define the establishment and interface, directly use JMS, through the JMS to link middleware ◎ MOM-Messaging Oriented MiddleWare, ◎ If there is a problem with the network, you can transfer it to complete the time of thinking. ◎ JMS is through production ◎ MOM product IBM MQSerials ◎ Subbinding is a communication through middleware ◎ ReceiveD uses synchronization communication ◎ Using MessageListener is asynchronous communication, only need setmelistener listener (MessageListener Listener) is OK. ◎ You can use durable persistence to save JMS messages ◎ Adding Queue and Topic ◎ lasting Subscriber by modifying c: /jboss-3.2.2/server/default/deploy/jms/jbossmq-deploy/jms/jbossmq-deploy/jms/jbossmq-deploy/jms/jbossmq-destinations-service.xml And storage forwarding will be used together, otherwise, when the case occurs, it will not be sent to the client, but the persistent subscriber will also receive the email, which is the difference between the two ◎ JMS can set priority , Level 9, level 4 is default ◎ JMS can set the message ◎ MDB EJBCREATE is mainly used to access SessionBean, you can add related to find InitialContext ◎ Do not add systemic abnormality for Throwejbexception in MDB onMessage This will lead to poison news, because the system will think that you have a first system-level exception, then the system will roll back to the current operation, so Destination will think that Bean is not accepted, so it will continue, bean Continuous Callback, this will lead to the production of poisonous messages ◎ Use JMS and the use of SessionBean, the former can interact with the EJB container, and better flexibility, no Need to expose any stub and skeleton, while SessionBean's way is a synchronous way, and needs to give the client stub ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ------ -------------------------------------------------- --------- Design Pattern: -------------------------------------- --------------------------- ◎ Singleton Design Pattern: Private Constructorstatic Method to Build A Singleton Object ◎ Factory Design Pattern:
◎ Observer Design Pattern: NotifeViewChange ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------ JDO: ----- -------------------------------------------------- ---------- ◎ If you want to make objects also support Persistence, you must extend javax.jdo.Persistencecapable ◎ Inheritance relationship in the JDO table, you can maintain the relationship in the table, you can maintain the maintenance ◎ JDO There is also its inquiry statement JDOQL ◎ JDO supports various types for Persistenceall Primitives (int, float, byte, etc) All primitive wrappers (java.lang.integer, java.lang.float, java.lang.byte, etc)
Java.lang.string
Java.math.biginteger
Java.math.bigDecimal
java.lang.number
Java.util.locale
Java.util.date
Java.util.hashset
◎ Metadata in JDO ◎ Any Field, which is declared for static, finAl, and transient will not be persistent Persistence ◎ relational operator ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎
-------------------------------------------------- ------------------------------ {◎ There is DurableSubscriber in Topic, which can reach the system crash by storage forwarding, the same client can receive Go to the message, then there is also the same durable in Queue if there is no solving this problem is ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎ ◎
}
