[Design of JBoss Portal] - Oportunidade SeedTS
by SeedTS
Consultor Instrutor Jboss
Consultoria especializada em Oracle/Java/SOA/JBoss em franca expansao oferece uma oportunidade para quem esta buscando trabalhar com tecnologia de ponta em um ambiente dinamico e desafiador.
Requisitos:
-Servidor de Aplicacao JBoss ( instalacao, configuracao e administracao),
-JBPM, Jboss Portal, Criacao de Cluster, JBoss seam,
-Experiencia em ambientes de alta disponibilidade e deploy de aplicacoes.
Desejavel:
- JavaEE (EJB, JSP e Servlet),
- Ter experiencia como instrutor,
- Certificacao
Diferencial: -Disponibilidade para viagens,
-Ingles avancado.
Escopo de atividades:
- Instrutoria, Palestras, Suporte e Mentoring.
Oferece-se:
Desafios constantes, grande oportunidade de crescimento profissional, poder de decisao atrelado a alta responsabilidade, plano de carreira e participacao nos lucros.
Os interessados devem enviar cv atualizado para rh(a)seedts.com
Contrato de trabalho por prazo indeterminado.
Local de trabalho: Sao Paulo - SP
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180031#4180031
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180031
15 years, 7 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Message Scheduling
by ataylor
This is how i propose we handle message scheduling.
Firstly the send method in ClientProducer will be overridden with a new parameter (long) to allow the scheduled time of message delivery to be specified. A new packet will be created, say SessionScheduledSendMessage, which will extend SessionSendMessage and have a scheduled time attribute.
In ServerSession when we send the message if the scheduled delivery time is set and it is not involved in a tx we route the message and then update the references with the scheduled delivery time. If the message is persisted we then add a ''SET_SCHEDULED_DELIVERY_TIME' record. This is so on reload we can reschedule the messages. We then add to the queue as a scheduled message and the current queue code will take care of delivering when ready. If the message is part of a tx,we add it to the transaction marked as a scheduled message and on commit the messages will be handled the same way.
One slight problem is how do we deal with this during page since when the message is depaged we won't know it was to be scheduled. Tim suggested adding and removing a property on page/depage, We could do this simply by adding a property to PageMessage and change the page method to have an additional oprtional property, Clebert any thoughts?
Lastly on a JMS layer, it would work as in 1.4, I.e. you set a property on the message and we decide on send how to send it.
comments!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180010#4180010
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180010
15 years, 7 months