SOAP-JMS Binding Working Group Teleconference -- 14 Oct 2008

<Yves> trackbot, start telcon

<trackbot> Date: 14 October 2008

zakim aaaa is mphilip

<Roland> Topic Actions

Actions

<scribe> scribe: mphillip[

<Roland> http://www.w3.org/2002/ws/soapjms/tracker/actions/open

close Action-38

<trackbot> ACTION-38 - put the just agreed-upon changes related to TextMessage into the spec (Phil's write up & Eric's writeup) closed

close action-39

<trackbot> ACTION-39 Email/phone Oracle/BEA to see if they want to continue to be listed on the URI specification by 2008-10-08 closed

Oracle removed from the editor list on the URI spec

close action-40

<trackbot> ACTION-40 Write up specific proposal for conformance to address the normative concerns. closed

Roland's edits per Action 38 and 40 to be reviewed

Review draft changes per Text Message etc.

<Roland> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8

<Roland> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#binding-message-body

All comfortable with the text messages changes

<eric> Add sentence: a conforming implementation MUST support both TextMessage and BytesMessage. ?

scribe: providing we add a clarification into section 2.4 like eric's comment above

<Roland> change "Use fault subcode unsupportedJMSMessageFormat when the arriving message format is not supported by the application"

<Roland> to"Use fault subcode unsupportedJMSMessageFormat when the arriving message format is not BytesMessage or TextMessage"

<scribe> ACTION: Roland to Clarify the fault to be returned when the arriving message is neither Bytes or Text message [recorded in http://www.w3.org/2008/10/14-soap-jms-minutes.html#action01]

<trackbot> Created ACTION-41 - Clarify the fault to be returned when the arriving message is neither Bytes or Text message [on Roland Merrick - due 2008-10-21].

<Roland> Conformance changes:

<Roland> http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#introduction-conformance

Changes on conformance - section 1.6

Clarified that WSDL support is optional, but that if implemented, the implementation MUST implement all the requirements

Phil: Ask for clarification on the support for the URI

Eric: Simplify by removing the last sentence, and say that the URI MUST be supported (in the first - base protocol - statement)

Phil: Does this just mean JNDI

Eric: No - the URI scheme does not mandate any specific variant

<scribe> ACTION: Roland Clarify the conformance section (1.6) to make it clear that the URI scheme MUST be fully supported in the base protocol (just refer to it once) [recorded in http://www.w3.org/2008/10/14-soap-jms-minutes.html#action02]

<trackbot> Created ACTION-42 - Clarify the conformance section (1.6) to make it clear that the URI scheme MUST be fully supported in the base protocol (just refer to it once) [on Roland Merrick - due 2008-10-21].

URI Spec new draft

<Roland> https://datatracker.ietf.org/drafts/draft-merrick-jms-uri/

Roland: Spec. looks good

Eric: To proceed we need to mail the IETF secretariat list

<scribe> ACTION: Eric to Mail the JMS URI draft to the IETF Secretariat mailing list to move the process to the next stage [recorded in http://www.w3.org/2008/10/14-soap-jms-minutes.html#action03]

<trackbot> Created ACTION-43 - Mail the JMS URI draft to the IETF Secretariat mailing list to move the process to the next stage [on Eric Johnson - due 2008-10-21].

Spec anomalies on targetService

Eric's action to be dated for the end of the month

No XML Schema describes the elements defined in the

<Roland> specification

<scribe> ACTION: Mark to Create a Schema for the WSDL extensions [recorded in http://www.w3.org/2008/10/14-soap-jms-minutes.html#action04]

<trackbot> Sorry, amibiguous username (more than one match) - Mark

<trackbot> Try using a different identifier, such as family name or username (eg. mhapner, mphillip)

<scribe> ACTION: mphillip to Create a Schema for the WSDL extensions [recorded in http://www.w3.org/2008/10/14-soap-jms-minutes.html#action05]

<trackbot> Created ACTION-44 - Create a Schema for the WSDL extensions [on Mark Phillips - due 2008-10-21].

Specifying additional JNDI parameters,

<Derek> http://lists.w3.org/Archives/Public/public-soap-jms/2008Sep/0031.html

Derek: This dates back to action item 22. Some JNDI providers may need additional JNDI parameters
... The link relates to an email from Eric which discusses Derek's proposal
... Proposed URI changes include a suggested prefix to 'namespace' the JNDI properties

Roland: The suggested "jndi-" prefix would be a good thing if it is allowed in the URI - should be in the URI *and* the WSDL unless someone can think of a good reason why not.

No other comments on URI spec.

Derek: In the binding spec. Eric suggested using a new XML schema type for this WSDL extension property

Eric and Phil: Prefer the name "jndiContextParameter" to "jndiProperty"

<Phil> has to run... talk to you all next week

<Derek> http://lists.w3.org/Archives/Public/public-soap-jms/2008Sep/0028.html

Eric: This isn't just a string, this is a name and a value - i.e. a complex type

Derek: e.g. <soapjms:jndiProperty name="com.sun.jndi.someParameter" value="someValue" type="string"/>

Peter: We need to state that this will all be strings

Eric: They will be defined as xsd:string in the schema definition
... These JNDI values are always strings

Mark: Should this be a complex element with children or an elementr with attributes as shown

Roland: Simpler to use attributes e.g. <soapjms:jndiProperty name="com.sun.jndi.someParameter" value="someValue"/>

<scribe> ACTION: Derek to Tidy up the proposal factoring in Eric's changes and splitting the proposal into 2 parts - URI spec and Binding [recorded in http://www.w3.org/2008/10/14-soap-jms-minutes.html#action06]

<trackbot> Created ACTION-45 - Tidy up the proposal factoring in Eric's changes and splitting the proposal into 2 parts - URI spec and Binding [on Derek Rokicki - due 2008-10-21].

<Roland> <soapjms:jndiProperty name="com.sun.jndi.someParameter">someValue</soapjms:jndiProperty>

mark: Should be jndiContextParameter

Roland: May have difficulty chairing the call next week
... Two main items outstanding - JNDI properties and arbitrary headers.... We should discuss by email this week

Peter: Happy to drop issue on abitrary JMS headers

<peaston> I'm happy dropping arbitrary JMS headers

Roland: Hope to get spec into last call by the end of the month

- DRAFT -

SOAP-JMS Binding Working Group Teleconference

14 Oct 2008

Attendees

Contents