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 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.
0 comments:
Post a Comment