I was actually thinking about utilizing exceptions from java application code, but the event word just stuck in my mind for some reason.
1) I just wanted to make sure I wasn't reinventing the deep plate by implementing my own conversion from exception events to WEF. 2) The runtime handling would be somewhat application specific, so I'll map the events to the WEF on a case by case basis. Thanks for the answer. /Lenni -----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: 09 February 2007 16:08 To: [email protected] Subject: Re: wsn-producer runtime events Hi Lenni, I need some clarifications before I can answer: 1. What do you mean by 'Java event'? Exceptions? Or some other event/listener API? If it's the latter, what is the basic API for the event data? 2. We have no code for the automatic converstion of events (exception or otherwise) to WEF, because it would be very hard to guess the semantics and fill in all the WEF fields properly. Right now WEF creation has to be done like so: http://ws.apache.org/muse/docs/2.1.0/manual/how-to/publish-any-notificat ion.html Can you describe how much 'handling' you're looking for out of the runtime? Dan <[EMAIL PROTECTED]> wrote on 02/09/2007 06:48:43 AM: > Hi all > > I was wondering if there was a default implementation for handling any > runtime events produced by application logic, or if it would look a bit > simplified as follows: > > 1) The application logic fires off a Java event > 2) A WSDM WsResource with a Java event listener handles the event > 3) The WSDM WsResource creates a WEF and pushes it to a WSN producer > > /Lenni > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
