We have just published a White Paper that outlines the steps required to build Ruby on Rails Apps on GlassFish using JRuby. This would be the quickest way to start off with developing RoR applications on GlassFish. The paper outlines the steps through Netbeans and the command line.

Download the paper now.

This tutorial explores the Intelligent Event Processor (IEP) service engine, a component in GlassFish ESB 2.1 that provides powerful support for event-driven architecture (EDA). (Login or registration required.)

Ludo parece ganhar a corrida para ser a Primeira a anunciá-la, mas NB6.8 M1 ja está disponível para download. Esta é a primeira construção que fornece suporte JavaEE 6, incluindo um pacote GlassFish v3 (b57). Veja Novos e Notável e Ludo's Post para mais detalhes. Baixe os diferentes pacotes da pagina NB6.8 M1.

Adicionado - Avaliações de:

• Adam Bien - "Netbeans 6.8m1 - The (lightweight) Java EE 6 IDE"
• James Branajam - More About NB 6.8 M1

SNMP (Simple Network Management Protocol) est un standard répandu de gestion du réseau qui intègre un protocole, un schema de base de donnée et des objets de données. Etant donné la popularité de SNMP dans les entreprises, GlassFish Enterprise Manager propose son support sous la forme d'un plugin pour GlassFish Portfolio.

La documentation comporte les "Release Notes", l'installation et guide de démarrage, et la référence. Le logiciel est disponible au travers de Sunsolve. Si son utilisation vous intéresse, envoyez donc une demande d'évaluation par courriel. Dans le futur, nous allons proposer un mécanisme d'évaluation plus simple comme l'offre déjà WebStack Enterprise Manager.

L'équipe de développement du support SNMP propose un ensemble de billets : • Survol des fonctionnalités par Rashewar. • Plusieurs d'exemples par Marc Kossa. • Un billet de Sankar sur la configuration du monitoring SNMP. • Olivier nous parle de MIB: J2EE MIB et navigation de la MIB • Et encore deux autres de Olivier : Master Agent Integration et SNMP et sécurité. • et encore un d'Olivier : Monitoring de multiples domaines.

Nazrul propose un survol complet de GlassFish Enterprise Monitor.

In the scenario that the requester asks for delegation tokens from an STS
acting as various users, the security header for the request message to the STS carries
the credentials of the requester and the STS while the payload has the credentials
of the actual users being acted as. It is a perfect case that secure conversation should be
enabled for the STS to optimize the communications between the requester and STS.

To achieve this with Metro:

1. On the STS side, enable secure conversation with SecureConversationToken in the wsdl:
A sample wsdl is provided here. To use it with the delegate sample,
you just need to rename it from sts-sc.wsdl to sts.wsdl.

2. On the client side, one need to use the same STSIssuedTokenConfiguration instance for the different
calls to the STS as illustrated by the following codes for the server:

     public class FSImpl implements IFinancialService {
         @Resource
         private WebServiceContext context;

         private DefaultSTSIssuedTokenConfiguration config = new DefaultSTSIssuedTokenConfiguration();

         public String getAccountBalance(Department dept){

                 ...
     }

     private void ping(){
         PingService service = new PingService();
         Token actAsToken = getActAsToken();
         config.getOtherOptions().put(STSIssuedTokenConfiguration.ACT_AS, actAsToken);
         STSIssuedTokenFeature feature = new STSIssuedTokenFeature(config);

         IPingService stub = service.getCustomBindingIPingService(new WebServiceFeature[]{feature});
         stub.ping(new Holder("1"), new Holder("sun"), new Holder("Passed!"));
     }

     private Token getActAsToken(){
         return new GenericToken(getSAMLAssertion());
     }

     private Element getSAMLAssertion() {
         try {
                Subject subj = SubjectAccessor.getRequesterSubject(context);
                Set