SOA World Magazine
So what do you really look for in an interface engine? There is more to an IE
than just being a pass-through of messages.
Some good features of an interface engine –
1) Store and forward capability
2) Auto-acknowledgement
3) Guaranteed message redelivery
4) Rollback and retry capabilities
5) Reliable messaging, Once only delivery
6) Message Ordering, Error-free, Sequential
7) Disconnected Operation
8) Message Logging
9) Message Security
10) Consistent Routing
11) Message Monitoring
12) Exception/Error Escalation
13) Uptime Quantification
14) Persistent Messaging
15) Timely Delivery
16) Failover
17) Fault Tolerance
18) Load Balancing
19) MTTF (Mean time to Repair), MTBF (Mean time between Failure) management
20) Disk I/O performance monitoring
21) Continuous Availability
22) Transaction-aware distribution
23) Loosely coupled asynchronous messaging framework
24) Dea... (more)
Java Developer's Journal
A cool article at http://www.roseindia.net/javatutorials/insane_strings.shtml
You never know what can happen with Java code .
... (more)
We had this new error from Hiberante –
“java.lang.IncompatibleClassChangeError: class
org.hibernate.cfg.ExtendedMappings has interface org.hibernate.cfg.Mappings
as super class” – This is due to using the older hibernate entity
manager/annotations libraries that were around when we upgraded to the newer
3.5.x version of hibernate. Hibernate includes the entity manager and
annotations as part of the hibernate core library.
... (more)
Java Developer's Magazine
Here’s a Echo3 application in 3 steps -
1) Create HelloWorld.java
public class HelloWorld extends ApplicationInstance {
public Window init() {
Window window = new Window();
ContentPane contentPane = new ContentPane();
window.setContent(contentPane);
Label label = new Label("Hello, world!");
contentPane.add(label);
return window;
}
}
2) Create the HelloWorldServlet
public class HelloWorldServlet extends WebContainerServlet {
@Override
public ApplicationInstance newApplicationInstance() {
return new HelloWorld();
}
}
3) Change web.xml
Hell... (more)
Being an architect is a tough job. The life of an architect is very painful
especially taking many suboptimal decisions in the dark. The book “97
Things Every Software Architect Should Know” can really help avoid such
costly mistakes.
You can get the book at –
http://www.amazon.com/Things-Every-Software-Architect-Should/dp/059652269X/
... (more)