On Aug 23, 2006, at 4:57 AM, Liu, Jervis wrote:
Thanks, ant. I did see this discussion after I sent out my email.
However, my point was that no matter what kind of locating and
loading mechanism we adopt, it does not appear to be an absolute
requirement that we need to cache loaded wsdls. As once the wsdl is
loaded and parsed, we store all info in the instance of
WebServiceBinding, there is no need to access wsdl anymore for
following processes.
Why don't we start with something simple and then add in
functionality as we need it?
Of course I have to admit, without a cache or registry, it is a bit
hard to implement refreshings....
We do need a system service for example a resolve to lookup and
load wsdls. It can be a chained resolvers, so that if resolver A
can not load a resource successfully then the responsibility passes
to resolver b, then c...This way Tuscany runtime can config a
default resolving logic by registering resolovers in order,
applications can extend this by register their own resolvers.
Yea the resolver has come up too. I think we were going to have a
swappable system service that implemented different resolution
strategies. Do the resolvers need to do more than just handle
resolution?
Cheers,
Jervis
-----Original Message-----
From: ant elder [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 6:18 PM
To: [email protected]
Subject: Re: Celtix binding
There's a long thread going on about this right now:
http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg06781.html
...ant
On 8/23/06, Liu, Jervis <[EMAIL PROTECTED]> wrote:
One thing you can try is same as what is done by axis2's
WebServiceBindingLoader, i.e., using wsdlLocation to parse
wsdl Definition
by yourself. This way wsdl Definition is not cached but it works.
I can not remember if we had a discussion on this before.
Do we still need
a wsdl cache ( e.g. WSDLDefinitionRegistry) somewhere like
we did in M1?
As far as I can see, once WebServiceBinding is created,
components that use
web service binding should be able to access all wsdl
related info from
WebServiceBinding, thus there is no need to access a wsdl
cache any more.
Cheers,
Jervis
-----Original Message-----
From: Liu, Jervis
Sent: Wednesday, August 23, 2006 10:52 AM
To: Jim Marino; [email protected]
Cc: Chris Wall
Subject: RE: Celtix binding
Hi Jim, Celtix binding currently is not working yet. I got
the helloworldwsclient working with the Celtix binding with
some hacks and without using SDO. At the same time, for the
helloworldws-celtix sample, I am able to get the reference
part working, and still struggling on the service part. the
creation of WebServiceBinding is one issue among many, the
main problem is that the wsdl info is not properly cached in
WSDLDefinitionRegistry. As soon as helloworldwsclient and
helloworldws-celtix are both working, your sample should work
as well. I will let you know once I make any further progress
on these two samples.
Thanks,
Jervis
-----Original Message-----
From: Jim Marino [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 22, 2006 4:02 PM
To: [email protected]
Cc: Chris Wall; Liu, Jervis
Subject: Celtix binding
Hi Jervis,
Chris and I have been trying to get the Celtix binding
bootstrapped
into a sample where it wires to Spring. I noticed
WebServiceBindingLoader line 134 originally returned a null
instead
of a WebServiceBinding, which caused another issue related to
composite wiring (I or Ignacio will need to fix). So, to
get around
this, I changed the loader to return a WebServiceBinding that
doesn't
work as I pass mostly nulls in. Ideally, we'd like to get
the Celtix
part fully working. Both of us are willing to help out
if you can
provide some direction.
The same SCDL and WSDL are attached.
Thanks,
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
