After the magical dust of JavaOne has settled the reality is reappearing and we can start thinking about the results. Especially Sun's announcement (beside buying my current employer) of open-sourcing their application server was a hot topic here even though I did not quite trust all the fuss around it. Now over the long weekend I had time to figure out what happened and the result, quite frankly, is disillusioned and I get the feeling that this was just the last phase of this application's life cycle.
 |
Search |
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Blogs by topic J2EE and user schaefa
J2EE
A choice in how J2EE application servers handle a depleted MDB pool for JCA inbound connections leaves the Resource Adapter developer in limbo creating vendor neutral applications. In a specification were pieces have to work together like a lock and key the specification must be especially clear otherwise one party has to pay a high price.
Except you are thinking J2EE is the Holy Grail of application servers one could think about what comes after J2EE. I came up with a proposal of a more generic application server that could work like a J2EE based server in a particular configuration but could become quit another beast in another configuration.
This is my response to Simon Borwn's log 'File access in EJB'.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
|
