I signed up for the session, "Spring: From the chosen framework for ecosystem". This Eberhard Wolff has won before Rod Johnson and his Q & A session to keynote and a few other interesting sessions. Hope it is as interesting as I hope the straight. Of course, precisely in this session the question of whether Spring will not become too large with all the groping and thus in the case, now in the Java EE already infected.
Wow, first time throws Wolff viiiiele bubbles on the wall: the whole jumping sub-projects. One of the bubbles is Spring Batch. Spring Batch is the support of batch jobs in Java, and batch jobs that are important in many projects. Typical problems of batch (I guess support for it is the same) are restart after a fault, parallelization and optimization of database operations. [...] (Note: Here Eberhard Wolff speaks some detail about Spring Batch) And again, and more, and more batch details. Yes, I know what a batch and how one would build something like that. The details of Spring Batch can I look at me now that I know that it exists. I'm just to leaf through my records and look for alternatives. This is not the talk of the title, but something else. The whole I feel personally much too deep in Spring Batch, a much shallower survey would have definitely served here. More diverse. What else is there to bubbles.
Finally you go to the next bubble: Spring integration. This solves typical EAI problems, so messages, routing, splitting, transformation, etc. The framework is based on a Pipes and Filters pattern and is event-driven. This means that the framework takes care of the message-listening, and then controls the service calls. For example, assume The Spring Framework integration, the thread handling. Great, now even on the correct level. Now just do not slip too much into detail. We are now at the code, it might be too detailed. Yeah, it is too detailed. Well, I'm interested, I do not Raschle, but it's really too detailed. I tack with the now not, but simply refer to the appropriate slides. I just hope that I get the CD-ROM with the slides afterwards. If the thing by mail or have to get it? What I would like to point here: Spring Integration has a classic Java API, but it is also very good and easy to work with annotations.
Spring Web Services is the next Bubble, the Eberhard Wolff imagines. Interoperability is the goal of Web Services and Contract First is the means to an end. If one has ever WebServices, then you can do more than just request-response and one would possibly also can directly access the XML.
first contract is set, otherwise how can you ensure interoperability. A WSDL makes writing by hand is no fun. Conversely, the way you generate the WSDL from Java is also less than ideal - it's last contract, which do not correspond to Java classes, the WSDL / XSD ways to tie necessary, consult the individual web service stack. Even already experienced - Web services are not per se first time really inter-operable between different stacks and languages. Now we come back to the point that the WSDL is not really en bloc should be written by hand, but should be generated together from various artifacts.
Spring uses an XML schema that defines the data description and methods. The complexity of the SOAP stack (endpoints, ports, and so on and so on) you can then make elsewhere.
For the mapping of objects to XML and vice versa can take the existing techniques - JAXB 1 and 2, Castor, XMLBeans, JiBX, XStream or whatever. Or they map not, but goes straight down to the XML structure, for example using JDOM or SAX. The third alternative is to annotations and XPath. The looks interesting.
In 1.5 ("what we shippen now"), there are also new JMS and email transport.
More Bubbles are not even briefly, as it sometimes still own Talks to do so.
Spring Enterprise bundled together different things: For example, the Advanced Pack for Oracle, Oracle RAC certain misfeature of "irons out". It is part of the SpringSource Tool Suite and to the SpringSource Application Management Suite.
Ok, we have seen that Spring is also a whole zoo of frameworks now, but these individual frameworks are much loose coupled together than is the case for JEE.
0 comments:
Post a Comment