RE: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't allow custom wireFormats in JMS response element

2009-10-10 Thread Konradi, Philipp
Great, thanks for the replies! I've been aware of the possibility to define 
custom wire formats, but seems like not of all its features :-)

 -Original Message-
 From: ant.el...@gmail.com [mailto:ant.el...@gmail.com] On Behalf Of ant
 elder
 Sent: Friday, October 09, 2009 10:31 AM
 To: dev@tuscany.apache.org
 Subject: Re: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't
 allow custom wireFormats in JMS response element
 
 On Fri, Oct 9, 2009 at 9:23 AM, Simon Laws simonsl...@googlemail.com
 wrote:
 
 
  In 1.x we did add the feature, that Ant is referring to, that allows
  you to specify wire formats for request and response independently.
  So, for example,  you could have an incoming bytes messages and a
  response formatted as xml. Ant, is the feature still enabled in 2.x?
 
 
 Should be, the 2.x code is pretty much the same as the 1.x just with a
 few package renames and module simplifications so you just need the
 binding-jms-runtime module and not the policy or jms host ones. Its
 close to done now, the only things not working yet in 2.x are
 callbacks and jms support in the definitions.xml file.
 
...ant


Re: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't allow custom wireFormats in JMS response element

2009-10-09 Thread ant elder
Yes thats possible, the wireFormat is designed to be extensible so you
can create new ones as required. We don't have this structured in
Tuscany to make it totaly obvious what you need to do but you can see
the code of the existing Tuscany ones at:
https://svn.apache.org/repos/asf/tuscany/java/sca/modules/binding-jms-runtime/src/main/java/org/apache/tuscany/sca/binding/jms/wireformat

   ...ant

On Thu, Oct 8, 2009 at 10:01 AM, Konradi, Philipp
philipp.konr...@siemens.com wrote:
 I wasn't aware of this possibility, does it mean one can configure different 
 data formats for request and response messages?

 Best,
 Philipp

 -Original Message-
 From: ant elder (JIRA) [mailto:d...@tuscany.apache.org]
 Sent: Wednesday, October 07, 2009 3:16 PM
 To: dev@tuscany.apache.org
 Subject: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't
 allow custom wireFormats in JMS response element

 JMS Binding schema doens't allow custom wireFormats in JMS response
 element
 ---
 

                  Key: TUSCANY-3297
                  URL: https://issues.apache.org/jira/browse/TUSCANY-
 3297
              Project: Tuscany
           Issue Type: Bug
           Components: OASIS Compliance - OASIS
             Reporter: ant elder
              Fix For: Java-SCA-2.0


 The 1.1 CD04 version of the JMS Binding schema doens't appear to allow
 custom wireFormats in JMS response element so the following binding
 fails schema validation:

    binding.jms
       destination jndiName=HelloWorldService1/
       response
          tuscany:wireFormat.jmsObject /
       /response
    /binding.jms

 I've raised the issue with the JMS binding spec and will add a work
 around to the Tuscany JMS binding xsd for now


 --
 This message is automatically generated by JIRA.
 -
 You can reply to this email to add a comment to the issue online.




Re: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't allow custom wireFormats in JMS response element

2009-10-09 Thread Simon Laws
Hi

There is more general info on the wire formats for JMS in the 1.x
documentation for the JMS binding [1] (we haven't made docs for 2.x
yet). Toward the bottom there are some notes about how the feature is
implemented.

In 1.x we did add the feature, that Ant is referring to, that allows
you to specify wire formats for request and response independently.
So, for example,  you could have an incoming bytes messages and a
response formatted as xml. Ant, is the feature still enabled in 2.x?

The wire formats are also pluggable, so in theory you can write your
own if the formats that are provided out of the box are not
sufficient. As you can see from the docs pages they are basically
interceptors that get a chance to process the message as it flows
between the binding and the service implementation.

Regards

Simon

[1] http://tuscany.apache.org/sca-java-bindingjms.html


Re: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't allow custom wireFormats in JMS response element

2009-10-09 Thread ant elder
On Fri, Oct 9, 2009 at 9:23 AM, Simon Laws simonsl...@googlemail.com wrote:


 In 1.x we did add the feature, that Ant is referring to, that allows
 you to specify wire formats for request and response independently.
 So, for example,  you could have an incoming bytes messages and a
 response formatted as xml. Ant, is the feature still enabled in 2.x?


Should be, the 2.x code is pretty much the same as the 1.x just with a
few package renames and module simplifications so you just need the
binding-jms-runtime module and not the policy or jms host ones. Its
close to done now, the only things not working yet in 2.x are
callbacks and jms support in the definitions.xml file.

   ...ant


RE: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't allow custom wireFormats in JMS response element

2009-10-08 Thread Konradi, Philipp
I wasn't aware of this possibility, does it mean one can configure different 
data formats for request and response messages?

Best, 
Philipp

 -Original Message-
 From: ant elder (JIRA) [mailto:d...@tuscany.apache.org]
 Sent: Wednesday, October 07, 2009 3:16 PM
 To: dev@tuscany.apache.org
 Subject: [jira] Created: (TUSCANY-3297) JMS Binding schema doens't
 allow custom wireFormats in JMS response element
 
 JMS Binding schema doens't allow custom wireFormats in JMS response
 element
 ---
 
 
  Key: TUSCANY-3297
  URL: https://issues.apache.org/jira/browse/TUSCANY-
 3297
  Project: Tuscany
   Issue Type: Bug
   Components: OASIS Compliance - OASIS
 Reporter: ant elder
  Fix For: Java-SCA-2.0
 
 
 The 1.1 CD04 version of the JMS Binding schema doens't appear to allow
 custom wireFormats in JMS response element so the following binding
 fails schema validation:
 
binding.jms
   destination jndiName=HelloWorldService1/
   response
  tuscany:wireFormat.jmsObject /
   /response
/binding.jms
 
 I've raised the issue with the JMS binding spec and will add a work
 around to the Tuscany JMS binding xsd for now
 
 
 --
 This message is automatically generated by JIRA.
 -
 You can reply to this email to add a comment to the issue online.