See also: IRC log
<trackbot> Date: 02 September 2008
<scribe> scribe: markphillips
<trackbot> ACTION-22 raise possible use cases clarification for jndi URI additional parameters mapping to JMS headers closed
<trackbot> ACTION-25 Look at wording that might allow vendor to use TextMessage and not break specifications closed
<eric> Email from Derek about jndi parameters http://lists.w3.org/Archives/Public/public-soap-jms/2008Aug/0039.html
Derek: The email outlines the
problem of identifying JNDI properties which need to be set by
the consumer if they are specified in the URI.
... These properties would need to be passed in a Hashtable when the InitialContext is created
... Suggest a namespace prefix for JNDI properties
<scribe> ACTION: Derek to Write up a proposal to differentiate JNDI connection properties in the URI and WSDL [recorded in http://www.w3.org/2008/09/02-soap-jms-minutes.html#action01]
<trackbot> Created ACTION-29 - Write up a proposal to differentiate JNDI connection properties in the URI and WSDL [on Derek Rokicki - due 2008-09-09].
<eric> JMS URI scheme at http://www.ietf.org/internet-drafts/draft-merrick-jms-uri-03.txt
<eric> Phils email about TextMessage: http://lists.w3.org/Archives/Public/public-soap-jms/2008Aug/0040.html
Phil: Proposes adding a new "messageType" property to allow the default (BytesMessage) to be overridden
Derek: Any special fault handling?
alewis: What about mismatches in
... SOAP message contains XML encoding which could conflict with the TextMessage's Java string
Eric: The alternative is that we
allow TextMessage as a vendor extension
... We could say that a receiving node SHOULD be capable of accepting a TextMessage and responding with a TextMessage when possible
Phil: Customers who have asked for this would like to do auditing in production - this wouldn't be a feature just switched on for development or diagnostics
<scribe> ACTION: Eric to Write up the options we have discussed so that we can identify and discuss the scenarios [recorded in http://www.w3.org/2008/09/02-soap-jms-minutes.html#action02]
<trackbot> Created ACTION-30 - Write up the options we have discussed so that we can identify and discuss the scenarios [on Eric Johnson - due 2008-09-09].
ACTION-30=Write up the TextMessage options we have discussed so that we can identify and discuss the scenarios
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: markphillips Inferring ScribeNick: markphillips WARNING: No "Present: ... " found! Possibly Present: Bhakti Derek IBM Peter_Easton Phil TIBCO Yves alewis drokicki eric joined markphillips peaston soap-jms trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Agenda: http://lists.w3.org/Archives/Public/public-soap-jms/2008Sep/0000.html Found Date: 02 Sep 2008 Guessing minutes URL: http://www.w3.org/2008/09/02-soap-jms-minutes.html People with action items: derek eric[End of scribe.perl diagnostic output]