Fever With Rash On Legs

jax08: Advanced GlassFish

So, that is, hopefully, exciting and the first few minutes, I can still definitely on the CD-Rom or check. In any case, I just switched the talk and let me know times for GlassFish.

An interesting link is

VisualVM
a monitoring tool currently second in Beta
GlassFish supports Single Sign On (SSO) for all Web applications or with
OpenSSO is also a cross-server or cross-domain SSO. Interestingly, even OpenSSO heterogeneous environments covering by adapter deployed in the respective environments. Now there's a few examples of how to use OpenSSO with different setups. Now here's the example for use in WebServices. Since SSO is a recurring theme, yes.
way from the SSO issue towards a new hype: Scripting. You can tell already, Daniel Adelmann has so certain reservations, "one has to admit" and "Quick, Dirty and Good Enough architectures" - honestly, what appears here as "Enterprise Architecture" trades is just not pragmatic. Not in dynamic languages, and not in Java.
After all, Sun has realized this and relies on JRuby. Jython has also been added. Now you just need official support for Groovy. And Daniel Adelmann is a statement that is supported in Groovy Netbeans and GlassFish. Personally, I am so convinced that dynamic languages - I distinguish here for me so of "scripting languages" - also bring significant benefits to the Enterprise.

that it makes sense to combine AppServer and "scripting languages" also represents Daniel Adelmann, whether for security reasons, for reasons of operational infrastructure and the know-how.

nice is the support for PHP on the

Quercus servlet. I like that. Also for JRuby, there are bundle that directly Install the GlassFish 2 does. From GlassFish 3 is a mini version (goes back almost to the Keynote), which then were, "only" provides the Ruby server.
What happens with Groovy and Grails? Interestingly, this is done in Germany and is currently working in
.
Next: Rich Client Application: Load balancing and failover for IIOP (s). You can just generate the client with the ear and the Glassfish bundle then automatically JNLP file. Seems to be everything but not so easy. That's all for reading the slides. And hah - Firewall / Load Balancing scenarios's' ne solution.
Comet is a solution to a push from Server trigger to the client. You have to take a closer look. In any case, supports GlassFish Comet and you just have the http-listener the property "cometSupport" to "true" set. In the server log should then what are like "Enabling Grizzly ARP Comet support". The basis for Comet in GlassFish, the NIO, which allows a non-blocking handling. In the service easy to implement the CometHandler CometHandler and attach the request. The code went on two slides and the mechanism is quite interesting.

My conclusion to this session: Yes, She with OpenSSO do not really necessarily to do with GlassFish, but the talk was very interesting, has handled a broad topic and was highly recommended. Well, Comet the topic we had so sometimes even without knowing that there is Comet.

Shannon Whirryforum Pack

jax08: Presenter First for RCP applications using Spring OSGi

Wow, three buzzwords in the title at a time when I take this test then read more ... So wait and see whether the Buzzword Bingo or interesting. In this time slot, the competition is great, I have omitted Glassfish, language trends and Pragmatic Architecture.

course, we want simple, agile, and our Eclipse RCP develop testable UI code. Let's go. Brief Introduction to the example test cases for the example. Too bad, because Heiko Seeberger makes even the first test, but then he makes (in his films) again the "mistake" not to be guided by the tests. He it's something that makes it "so it makes it not" example and the example completely chopped off in a composite. Well, no wonder that this can not test. Next. Next point.

I think I'm wrong here - and I prefer to look at the presentation on CD-Rom. Let's see, I'll just go further in the next lecture, where it might not be read so easily.

Hair Colour Chart Wella Koleston

Grails - the grail of web development

man, oh man! Twice already I wanted to listen to this talk in Hamburg already - in the XP User Group and at HAW. Both times has not worked out, so it must go here at last. I come from the corner of web development and the issue is not quite let go of me also determined, although at the moment I rather service-oriented and Eclipse RCP-heavy'm out. Maybe there's also new ideas for an RCP Grail, for convention over configuration where it has not yet taken it. Moreover, in my opinion, this "weakest" Session Round (in this case I had to choose only four talks) and we have divided us and we miss something colleagues technically there is nothing relevant. Hopefully.

Hey, cool. At last, time's has paid off, that my notebook so 'has weak battery NEN: Because I wanted a place with secure socket was there before and now has at least neither stand nor sit on the floor. Grails is an issue that burns.

The presentation style - at least the start - is great already. Personally, I stand on these kind of talks. On the basis of "practical examples" illustrate the two web frameworks: It is more of a breakdown Show in pictures from all sorts of areas, with transmission to the web framework. The films then are more classic, but well, it will indeed be not only cool but also informative.

Spring, Hibernate and SiteMesh are the basics of Grails, Groovy is just the icing on this basis. And as the icing is thin, the application will not be thick, to be called by the slow but relatively low performance. In addition to these basic Grails plug in other libraries for Ajax, batch, safety and testing. Actually there are old acquaintances from the world of web development.

Now comes a crash course Groovy, I give not more times. For Java developers, the start was so suuper-light, but as always, of course, it takes a while until you reach really think of the language. I ride around on it again - who can LISP, ... well, we can also Stefan Roock What this points again: Groovy and Java work seamlessly, you can access Java classes in Groovy classes, and vice versa.

now to Grails: First of persistence: Domain Objects are mapped automatically. I have to do so no Hibernate configuration, no JPA annotations or anything else, it starts immediately. Although one admit, then it does not stop here, annotations, or making it something, but on the convention that domain is in a package and that uses the fields or hasMany belongsTo who will each receive a map. Constraints are such as defined by a closure that contains a DSL. Exciting concept. Stefan Roock also points out that it is easier to do when it only accepts times and does not try to understand it first time and making it then. Certainly true, the concept is easy to use. As the figure happened to the database constraints have to know not really. But it shows nicely the Groovy think.

The dynamic finder is really interesting because He beautifully illustrates the dynamics of language: Adresse.findAllByPostleitzahlAndGueltigBis (21 502, null). A MOP (Metaobject Protocol) has real benefits! Between the question of the IDE support is of course interesting: IDEA has the best support, Eclipse and Netbeans pull to there.

groovy server pages and related SiteMesh rely completely on taglibs. This can of course do so also in Java itself, but Grails brings it all to stop.

We model and view, the controllers connect this controller to identify this in a separate package and the suffix Controller. Interestingly, the individual actions are not implemented as methods, but as closures, stored in fields.

Now it is already in the preserves: AJAX is installed (Prototype / Script.acoluo.us, Yahoo UI as a plugin, Dojo as a plugin). Taglibs can build yourself: Again by convention taglib purely throw in their own folder and you have a taglib taglib done. Stefan Roock points out that one uses the simplicity in Grails taglibs own projects more frequently than in Java projects. I think once.

testing is directly involved in Grails. It generates skeletons for domain classes and controllers, integrated running tests in the provided scripts, etc. Yet this is rather slow because the VM, the framework and the Web server from time to time is again up-down and resuming. Stefan Roock

now come on to RESTful services with Grails, very interesting, but which we might almost too deep. The audience sweat some of them already.

But, it's almost done. Now do it (after the inevitable commercial) for a live demo. So, Console, TextMate, and off you go. Bernd Schiffer builds first time a new Grails application. Or he can build a new application, from the corresponding Grails script.
The domain class is again generated by script. First time that's not exciting, but plug-ins for Grails can engage here and so, for example, to the domain class and a test class generated.

Now you can start the application (which runs internally Jetty high). Still nothing much happens - the application starts up, but it is only the Grails default page view. So - Server continues to run - makes Bernd Schiffer is a corresponding controller. Which one can already see on the home page. Still missing a View, but the folders are already created. So hastily created a gsp page.

far to see everything without a server restart.

In class BootStrap there's an init (and destroy) method, there still comes out a bit init code (create domain object), start server and stop (otherwise the bootstrap init method does not run). And already you can see what.

Now you go about adding more links, more code in the controller, etc. So we carry. The questions go in the noise, about data sources, the underlying database to choose refactorings are not supported really well, there are several possibilities, (Java) to integrate legacy code. With DB Migrate you can perform the migration of database schemas.

Still my conclusion: The talk was a good introduction with a nice blend of theoretical insight and a practical part. Groovy is definitely worth a look. When now is the book?

2010 Honda Odyssey Front License Plate

side note connected

Just read on the JAX-site that it is "best opportunities for networking and exchange of experience!" There. Is'm just purely run shortly after his speech in Stefan Zoerner. Let's see what my colleague told after over Zörner Talk.

English Nane For Car Interiors

Spring: From the framework for ecosystem

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.

Very Tight Chested With A Cough

Future of Java

In the keynote Rod Johnson tells something about the future of enterprise Java. In his typically American way, he leads from the first time that Java is not sexy: "No one wants to date a Java developer. Ruby is still so much sexier for Web development. Is obviously not so, otherwise Johnson stands not here, but would make Ruby. So much American: We pull out statistics for the first time - indeed indeed.com job trends are the necessary data without major work. So the comparison with Ruby, with dot.net, all in colorful pictures. Conclusion: For Java developers will gedated further, needs to change Java. We'll see what Johnson presented as six plus two predictions.

But first time to the factors make the changes necessary: First of all, there is the "productivity challenge" - that one quickly with Ruby on Rails is in the development of specific web applications than with Java has now been rumgesprochen. The point here is that the Java community to the "low hanging fruit" over jumps. So why are Rakentenphysik, if it be so simple. Si!

The second reason is simply necessary to change the age of Java EE. Java is simply no longer slim, because he has now accumulated a lot of "baggage". Well, I would indeed have "garbage" taken, but the effect is the same: you have to clean up the system again to make spring cleaning. Johnson sees in Java EE 6 precisely the attempt to bring the Java platform on its feet. The two Idees behind Java EE 6, Extensibility and Profiles (also available in JSR-316). The basis for extensibility is the realization that you can not put everything in the platform, but that the platform really, so what should be a platform for other frameworks. After all, knowledge is for the Java EE platform really new. But it sounds good, because I feel that, for example, the AppServer as a result of Java EE, often so that I do not need many of the services offered. Others not, and this is probably the reason why the Tomcat as "App server light" is so popular. Sorry, I digressed.

Johnson is now already in the profile. There will be the first time three of them and they are manifestations of the platform. The simplest variant "Profile A" (I guess that the name will change) is essentially the Tomcat: Servlets, JSPs, JSTL and EL, and things like that. The important thing to change in the outlook: The Extensibility strikes again and eg you have not always enter everything by hand in the web.xml. Instead, it will provide an API for it, so that frameworks can easily build on the Java EE (light) platform.

Profile Profile B is A plus persistence and two-component models (with question mark). Maybe there will be an EJB 3.1 light, which also will always be that. The second is possibly a Web Bean model are (JSR-299). Profile C will be almost exactly what we have now as Java EE. Rod Johnson has now are already on the films that the full Java EE has little relevance.

For the Sun is of course a good strategy: With this strategy, Java, perhaps a few more years down against the top Ruby and defend against Dot.Net. Whether it is really for developers shows a real effect remains to be seen: WebLogic, WebSphere and JBoss are of course their product strategy, think about a piece far independent of Sun. The trends go there even more meaning, more and more to pack in the products - even if only as a marketing fake. But that's another topic. Rod Johnson comes to similar conclusions in his next film. Interestingly, the next statistics is also (see above) - Tomcat is the most widely used platform for enterprise Java. What Sun So here goes as a strategy is simply adapt it to reality. To the reality that we live here in the audience already all.

Now for the long-awaited Predictions:
"Real competition will return to the application server market", yes, Tomcat can then also stick to the Java EE-stamp and thus one has a more market participants. And in addition to many other Tomcat. Thus, there is just a low market entry threshold. Ok, basically I got the point already above already, because the point is, that realize the full Java EE Appserver functionality, use only the least. I feel, moreover, so - in the last project we had a WebLogic, which we have used the servlet engine for Web services and JMS. We could have done with the Tomcat.

Prediction 2: "Tomorrow's application server will be light weight and modular". JBoss now people are screaming "we already have, we already have." Right. And all others are set according to Johnson on OSGi as a technical basis.

Prediction 3: "Tomorrow's application server will not Merely Implement JCP specifications. Strange - but they do not have today. And if so, Push your original items with new standard proposals. But Johnson still leads in a bit: It will not only give JCP standards, but also eg by the OSGi Allience. Much more interesting is the reverse, in which Rod Johnson points out, that the JCP is not always necessary to reinvent the wheel. Who needs commons logging, log4j if it already is. Who needs a new EJB concept if it is Spring. JSR 277, OSGi if it is. Whether to enforce this setting may at last? I'm not a fan of it only (thought) Monopolies and who has a better idea of who should implement it in code. But often it is simply not a better idea, sometimes not even to another. Just only one other organization - the not invented here Phänonomen does not stop at the JCP. This is also the extended prediction: the JCP will run on open source.

Prediction 4: The market will address the gap between Tomcat and WebLogic / WebSphere. That's right, because that's true even now, yes. Only that, for each part its own solution knits. You can also use a Tomcat as productive as the WebLogic.

Prediction 5: The gap between application servers and ESBs will be Bridget. Well, that's still a long way. It is for example still a long way there that my platform decides whether it is using now load from a locally deployed service reasons or the same service on another machine. But such features would be for me a real step forward for the SOA thought. And on the SOA thought Rod Johnson is also just clear of the topic is so close and still bears the Buzzword.

Prediction 6: The Black Knight will be defeated. In other words, EJB is dying. Yeah, this is not a prediction, this is an observation. Who does already EJB when it may instead make Spring. Interesting statistics again - in the U.S. you can see the obvious with EJB (still) a little differently. But - the first funny stats - the curves for the development of Java EE and Cobol are alike as peas in a pod. Both legacy techniques.

In Conclusion a Johnson admits that Java EE 6, the relevance Java EE increased, but that Java will no longer determine the future.

At the next session.

Will I Loose Weight Doing Body Jam

JAX opening

Day 1 of the 08th JAX Yesterday, I was already on day 0, the Agile Day before the JAX. Sebastian Meyen-editor at S & S Media, the host of the JAX - it just says there were about 400 people there. Now he tells only something about the current context - what topics are interesting (architecture, agility, technique), in which market environment, we are here all the way: Java EE, EJB 3, an alternative stack, from web 2.0 to Enterprise 2.0 and dynamic languages and scripting.

Sebastian Meyen goes straight in the dynamic languages on a particularly Groovy. I personally find it so very nice, because I think - on the Java platform that is very successful indeed - Groovy for a better choice than, say, JRuby. Good, but that's probably the next religious war. Compound eyes Meyen following stack: Bottom Java EE & Co., about a "dynamic" layer of dynamic languages and rule engines and over yet another layer of domain-specific languages.

for the Eclipse Forum's even a reference to the opening session, in which also the way to Eclipse 4.0 is shown. Maybe I should I go there? I can not break it.

Hey, great question from the stage: Who was last year already JAX? I would guess that just about reporting a fifth. And who was two years already? Surprise: the same people. Let's see if next year I can answer one of the two questions is yes ...


Gäääähn, now the whole "big and important name called. I can read itself is, but everything in the program. Too bad, until now was the opening but made it very nice. Well one, stop this ...

When People Refuse Gifts

agile project management in work contracts

Ok, it took a while to Dirk's son came forward. First he has painstakingly worked on Life of Brian joke ("The Shoe"), the lecture already threatened to be tough. But no sooner had he said the shoe was awkward all restraint from him and he turned on properly. This talk was definitely the highlight. Humorous, but also in substance.

The distillate of the project experience, I say only "bottom-up controlling" or "a wiki is not," was as informative as Dirk son's views on iteration 0, - is sometimes discussed dogmatic - have I ever experienced.

nice that Dirk's son at the end of his lecture, even at the beginning was promised work contracts. But actually that was only the curvature of the paper.

Pokemon Heartgold English U

Product Owner - a challenge

Chamber filled to the entire people, an estimated two to three hundred and the question Product Owner is if someone already or still wants to be not a single logs. Maybe it's all me all the way ... the role "in its purest form" is lived so well really rare.

But still - the talk is a real highlight. Urban Ernst lit his experience as a product owner of a 20-developer project. (In between, I ran out of juice - that is precisely my notebook - so there is no live-blogging.)

By the way, admits Urban Ernst still with some life lies agile development and in particular Scrum: Project teams do not organize themselves simply by itself . Sure, of course - that has so never told anyone. But it is good for a change again when someone points out how much Work is in reality.

A rich learning was the Sprint Goal Presentation and the story decreases, in which the product owner takes an active role. And very important: the process runs round material if the product owner and Scrum master have the same understanding of the process and thus draw in the same direction.

I put something extra: It is essential that all live in the project the same process. Not with the same intensity, clearly. But sooner or later makes the team wear down if there are different conceptions of the process. So again: The very idea of the process. Otherwise this will never be a process.

How To Create Fake Blood Effect On Imovie 09

collaboration in IT projects

Dr. Georg Molter and Torben Knerr now talking about team collaboration in Java projects, present challenges and requirements and then show collaboration tools at three levels: Level 1 as a set of open source tools, Level 2 as a special collaboration tools and Level 3 as in the IDE integrated collaboration platforms .

The problems of distributed collaboration are so well known - not only from the software development. The three "significant" by Molter and Knerr can actually evaporate together to "poor communication". This leads for example to different interpretations of the requirements to non-transparent planning and monitoring difficult. Further implications are the available means of communication (phone, chat, file sharing, video conferencing), etc., including performance of those means.

conditions for the success of a spatially distributed collaborative development are a common terminology, processes and tools (eg version control, management of test cases, etc.), a common understanding of the work items and the requirements and the support to take appropriate tools Collaboration . Many "disciplines" are met (with tools) to provide a good collaboration environment.

Molter Knerr and grab some of the tools now, and check just by meeting in the extent to which these disciplines. The reassuring statement first: In the Java world, we are not so bad on the road. I expect time that the tools are at different levels suitable differently. The individual tools I would like to pass now not, this was mainly a slideshow of screenshots.


The talk was unfortunately just that - a slideshow of screenshots with some platitudes about collaboration in general. I hope in the afternoon.

Period With Mucusy Discharge

introduction of agile processes

"How to become agile?" is the question at the entlanghangelt, Jutta Eckstein in their talk. Interesting question, but because the introduction is always a difficult process. By the way: Change is always a difficult Process, why should the change go to an agile approach that is easier. According to the "classical" distinction between bottom-up and top-down (you mean "guerilla tactics" and "command and control", but the terms are bit too warlike) stated Jutta Eckstein, and know that ideally all in the same direction - management , customer, developer ... Well, when that happens in real life yet? In any event, not mine. But that's what it's all Jutta Eckstein. How to perform agile approach nevertheless a success?

following points are therefore important:

In a series of retrospectives we first had to collect the experiences of past projects or the current project. The statement Jutta Eckstein is that as a result of this reflection on one's own actions and the desired action is usually somewhat agile show.

Readiness / create enabling workshops - usually with the decision, less with developers - understanding and lay the foundation for further action. Important questions are "What do we do that?", "What is easy to implement?", "What is really difficult?" and "What is impossible?". Sure, out comes the decision whether to proceed at all agile and can do what you have may still.

If you have the decision, then you can get started. Here, the consultant comes through - sell, sell, sell. At least here you can sell training. But what to do to get started? Training and coaching should simply accompany the first steps here, so just look at the first iterations, etc. At the same time you need a plan, like Jutta Eckstein puts it, "Passionate change agent, ie an individual that is passionate about the introduction of agility. I feel addressed.

Unfortunately, Jutta Eckstein not (directly) to one, how to bring the team to take over the course of the trial to more and more responsibility on their own. She says only that the success of the introduction of three roles depends entscheident: The project lead, the passionate change agent and the technical leader. In order to have

lasting success, you must create a balance between "beginners" on one side and "agile" on the other side. Just go with the recipe for beginners, even if it is against the agility really. Naturally recurring retrospectives are helpful to reflect on their own experiences and to adapt the process to your needs. Really helpful, it is natural if the Passionate rubs off in the course of the project on the other team members.

We are through with this talk. Now when I do a retrospective of times, I just hope that this was only the first iteration in the project "Agile Day", because so far came through for me no-new insights. The real sticking points has Jutta Eckstein - also slowed down by the shortness of the time - be silent. For me, the sticking points in this field, namely the support of the agile process with the developers on the one side (the process of change is usually still extremely dependent on individual persons) and the other involved in a project on the other. In particular, sales, employees and controlling Plaung I see an interesting factors: Vertieb thinks it can sell agile approach worse than a fixed price project. For the Mitarbeitereinsatzplaung it is necessary not only accurate, "estimates" leave - which of course no one recognizes as estimates, but that's another issue - the people actually tend to make not only this (agile) project, but also other projects, and so on and so forth.
The controlling nature are very difficult to deal with agility - how can you measure such as the POC for something that just by definition, is never finished, but is constantly in a process of change.

I hope the day is clear a few of these issues. The title sounds interesting.

Lyrics Of Love Story -taylor Swift

News from JAX 08

So, there is some news in my blog: I am currently in the JAX, specifically the Agile Day. On the Train ride I've heard just the pick of Frank Westphal to the subject, that includes some interesting aspects to the now but relatively "old" about agility is that coincide with my experience horizon: An interesting question is, for example, how to agility in the entire enterprise with how to integrate agile software development, for example with an existing controlling. Agile controlling, does this exist? Let's see what happens on such issues at JAX.