Hi Raymond,
I doubt there is a need to mix different data bindings for a same interface.
Can someone name a valid use case, for example, different operations are using
different data bindings? If we can safely assume one interface is always
implemented by one specific data binding, things can
Also to answer Jeremy's question raise before: I believe Celtix
uses WSDL extensions for this i.e. annotations added
to the WSDL or possibly the underlying XMLSchema to indicate the
data binding to use. . This is not true. Celtix1.0 only supports
jaxb,
Hi Jervis,
I thought Celtix
Hi Raymond,
How about defining databidings separately instead of embedded them as
extensions to the interface.wsdl. Right now I take the case of a WSDL to
express what I mean to say. In a WSDL...
- the message are defined
- then we have wsdl:porttype element and its children defined around
Yes, multiple databindings can be supported by different reader and writer.
What I said is that the Celtix 1.0 release only includes the support for JAXB.
More is being added.
Jervis
-Original Message-
From: Jim Marino [mailto:[EMAIL PROTECTED]
Sent: 2006?8?29? 15:03
To:
Ah o.k that clarifies things.
Jim
On Aug 29, 2006, at 9:17 AM, Liu, Jervis wrote:
Yes, multiple databindings can be supported by different reader and
writer. What I said is that the Celtix 1.0 release only includes
the support for JAXB. More is being added.
Jervis
-Original
Hi,
Sometimes it would be difficult to annotate the WSDL to add databinding
extensions because the WSDL could be from external web services. I think
your idea is similar to java annotations. Usually, the metadata in SCDL
should override those from java/wsdl annotations.
Thanks,
Raymond
On Aug 29, 2006, at 1:55 PM, Raymond Feng wrote:
Hi,
I agree with you that only one databinding will be used for the
same interface for most cases.
I have a case that we need at least operation-level databinding.
For SCA reference/service with JCA bindings, we need databindings
to
Hi,
When we use WSDL as an IDL in a java runtime, we probably have assumed some
data mapping rules because WSDL usually uses XML schema to define the data
types. To provide/consume data in java for a WSDL operation, we have to use
an XML info model such as DOM, AXIOM, SDO, and JAXB.
The SCA
Hi,
I don't see much difference to define DataTypes for WSDL portTypes than java
interfaces.
If we look at the WSDL structure, we can define default DataType for a
portType, an operation or a part.
portType
operation
input: message
part
output: message
What I'm trying to see is the minimum needed to get assemblies going with
different data bindings. One difference with using WSDL portTypes is that
you can't use introspection or annotations so all the config needs to be
done in the SCDL. I'm also wondering about the config for the source and
What about when you're using interface.wsdl and things like JavaScript? Take
the following composite example, could you show what the additional SCDL
extension would be needed to get that to work with SDO and E4X?
composite ...
service name=MyHelloWorldWebService ...
interface.wsdl.../
Could you give a bit more detail and a few more complete examples, I'm not
sure I understand all this? It seems a lot of XML, you're not likely to use
different databinding technologies on the same interface are you, and would
a lot of this have defaults so you don't have to specify all this for
12 matches
Mail list logo
