Hi, I have begun to write this sequencers (http://jira.jboss.org/jira/browse/DNA-78 ). I'm writing here to ask readers of this mailing list to take a look at my first implementation of ESBMessageMetaData and give me some feedback: http://fisheye.jboss.org/browse/DNA/branches/maeste/sequencers/dna-sequen... The purpose of this sequencer I have kept in mind writing it, is to extract infos from an ESBMessage for governance (and in particular monitoring inside governance) goals. What I'd like to have from this sequencer is to extract metadata about messages regarding properties, faults, and route. Querying and/ or statistics can be performed on this metadata and eventually joined with SLAs or others useful measurement. My idea is to implement a JCRMessageStore on ESB side (http://jira.jboss.org/jira/browse/JBESB-1769 ) storing the whole message as array of bytes, leaving to sequencer responsibility of extract and store in JCR (eventually different/ federated JCR) all metadata. This approach leave the JCRMessageStore very thin and eventually permit to have different level of metadata applying different sequencer. Any feedback is very welcome. What else do you like to sequence from an ESB Message? Are there any metadata I extracted in my first impl that you think are not useful? thanks in advance _______________________________________________ dna-dev mailing list dna-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/dna-dev

I'm not sure I understood. I don't see data about throughput attached to message. I don't think you are asking to calculate it from scratch in DNA, probably it wouldn't be the right place, so I'm probably missing something...can you point me where I can find throughput in esb messages? Thanks a lot S. Mark Little wrote on 09/06/08 11:19: > Throughput (that data is attached to the messages too). > > Mark. > > > On 9 Jun 2008, at 08:38, Stefano Maestri wrote: > >> Hi, >> I have begun to write this sequencers (http://jira.jboss.org/jira/browse/DNA-78 >> ). >> I'm writing here to ask readers of this mailing list to take a >> look at my first implementation of ESBMessageMetaData and give me >> some feedback: >> http://fisheye.jboss.org/browse/DNA/branches/maeste/sequencers/dna-sequen... >> >> The purpose of this sequencer I have kept in mind writing it, is >> to extract infos from an ESBMessage for governance (and in >> particular monitoring inside governance) goals. >> What I'd like to have from this sequencer is to extract metadata >> about messages regarding properties, faults, and route. Querying >> and/or statistics can be performed on this metadata and eventually >> joined with SLAs or others useful measurement. >> >> My idea is to implement a JCRMessageStore on ESB side (http://jira.jboss.org/jira/browse/JBESB-1769 >> ) storing the whole message as array of bytes, leaving to >> sequencer responsibility of extract and store in JCR (eventually >> different/federated JCR) all metadata. >> This approach leave the JCRMessageStore very thin and eventually >> permit to have different level of metadata applying different >> sequencer. >> >> Any feedback is very welcome. What else do you like to sequence >> from an ESB Message? Are there any metadata I extracted in my >> first impl that you think are not useful? >> >> thanks in advance >> >> _______________________________________________ >> dna-dev mailing list >> dna-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/dna-dev > > ---- > Mark Little > mlittle(a)redhat.com > > JBoss, a Division of Red Hat > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SI4 1TE, United Kingdom. > Registered in UK and Wales under Company Registration No. 3798903 > Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt > Parsons (USA) and Brendan Lane (Ireland).