Scott Kurz wrote:
OK, just wanted to make sure I hadn't missed a discussion on how to do
this with dynamic SDOs.
You know, one issue I noticed when looking at this with static SDOs is
the way that SDO makes it hard for you
to programmatically go from static SDO to XSD. Looking at the SDO
sourc
Hi Scott,
There was a discussion around this with the SDO folks and their view point
was that, having generated the static SDO from an XSD, why would one want to
go and generate the XSD again. Ideally the original XSD should be used.
Its been a while since I've been thro this, but I do remember
On Feb 3, 2008 5:01 PM, Mike Edwards <[EMAIL PROTECTED]> wrote:
> Folks,
> It is important to remember that when an interface is specified EITHER
> as some non-WSDL interface type (eg Java interface) OR where it is
> specified as WSDL, the FINAL WSDL that is necessary for a deployed (web)
> servic
OK, just wanted to make sure I hadn't missed a discussion on how to do
this with dynamic SDOs.
You know, one issue I noticed when looking at this with static SDOs is
the way that SDO makes it hard for you
to programmatically go from static SDO to XSD. Looking at the SDO
source I think it was the
Scott Kurz wrote:
When you wrote:
>
- The generator should use the databinding metadata (including any
knowledge of handwritten XSD representing the business data and
generation capabilities like the SDO XSDGenerator) to generate proper
XSD in the WSDL.
How were you thinking a particular XSD w
Sebastien,
When you wrote:
- The generator should use the databinding metadata (including any
knowledge of handwritten XSD representing the business data and
generation capabilities like the SDO XSDGenerator) to generate proper
XSD in the WSDL.
How were you thinking a particular XSD would be ass
Mike Edwards wrote:
Folks,
ant elder wrote:
On Jan 31, 2008 5:04 PM, Lou Amodeo <[EMAIL PROTECTED]> wrote:
Hi, I have a question about the implementation of the "wsdlless"
deployment
function.
The issues I see are occurring in a couple of places within the
life-cycle.
Namely, deployment, bind
Folks,
ant elder wrote:
On Jan 31, 2008 5:04 PM, Lou Amodeo <[EMAIL PROTECTED]> wrote:
Hi, I have a question about the implementation of the "wsdlless"
deployment
function.
The issues I see are occurring in a couple of places within the
life-cycle.
Namely, deployment, binding start, and servic
Simon Laws wrote:
On Jan 31, 2008 5:04 PM, Lou Amodeo <[EMAIL PROTECTED]> wrote:
Hi, I have a question about the implementation of the "wsdlless"
deployment
function.
The issues I see are occurring in a couple of places within the
life-cycle.
Namely, deployment, binding start, and service defin
On Jan 31, 2008 5:04 PM, Lou Amodeo <[EMAIL PROTECTED]> wrote:
> Hi, I have a question about the implementation of the "wsdlless"
> deployment
> function.
> The issues I see are occurring in a couple of places within the
> life-cycle.
> Namely, deployment, binding start, and service definition. It
On Jan 31, 2008 5:04 PM, Lou Amodeo <[EMAIL PROTECTED]> wrote:
> Hi, I have a question about the implementation of the "wsdlless"
> deployment
> function.
> The issues I see are occurring in a couple of places within the
> life-cycle.
> Namely, deployment, binding start, and service definition. It
Hi, I have a question about the implementation of the "wsdlless" deployment
function.
The issues I see are occurring in a couple of places within the life-cycle.
Namely, deployment, binding start, and service definition. It occurs to me
that if the generation of the wsdl occurred early in the proce
12 matches
Mail list logo
