Re: [ebxmlms-develop] JMSMessageListener contrib?

[Ronald v. K. <rv...@ab...>]

Mayne, Peter wrote:

> Sounds good, but I would strongly advise using Tapestry instead of Struts.
>  


:-) I currently have no time to start learning tapestry, nor do I have 
any other projects where I need this (we have other projets with struts 
however). Let me start out by using struts and try to find points where 
we could split some of the main servlet. Then, when I got a small 
working example, maybe tapestry could come in after that

(funny, they struts and tapestry are both apache projects)

Ronald

> PJDM
> --
> Peter Mayne
> Technology Consultant
> Spherion Technology Solutions
> Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
> T: 61 2 62689727  F: 61 2 62689777
>
>     -----Original Message-----
>     *From:* Ronald van Kuijk [mailto:rv...@ab...]
>     *Sent:* Monday, 12 January 2004 8:49 PM
>     *To:* 'ebx...@li...'
>     *Subject:* RE: [ebxmlms-develop] JMSMessageListener contrib?
>
>     Thanks Peter, saves me a lot of time comming to the same conclusion.
>      
>     In addition to this, I'm looking into creating a web based
>     monitoring/management functionality for Hermes based on struts and
>     even a web base test-client. Currently the management things are
>     realy tightly integrated with the messaging servlet. Splitting
>     management functionality into another url (/msh-console?) and even
>     splitting of the management functionality completely would
>     probably make it easier to have some general serverside message
>     processing.
>      
>     Anyone interested in this? I volunteer to refactor this part, but
>     since it is also related closely with the persistency layer, maybe
>     I should wait until that as landed fully.
>      
>     Ronald
>
>The information contained in this email and any attachments to it:
>
>(a) may be confidential and if you are not the intended recipient, any interference with, 
>use, disclosure or copying of this material is unauthorised and prohibited; and
>
>(b) may contain personal information of the recipient and/or the sender as defined 
>under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to 
>collect, hold and use such information and any personal information contained in a 
>response to this email, for any reasonable purpose in the ordinary course of 
>Spherion's 
>business, including forwarding this email internally or disclosing it to a third party. All 
>personal information collected by Spherion will be handled in accordance with 
>Spherion's Privacy Policy. If you have received this email in error, please notify the 
>sender and delete it.
>
>(c) you agree not to employ or arrange employment for any candidate(s) supplied in 
>this email and any attachments without first entering into a contractual agreement with 
>Spherion. You further agree not to divulge any information contained in this document 
>to any person(s) or entities without the express permission of Spherion.
>
>
>  
>