Nice - thanks Dan. Do you know of any plans for CXF to support WSDL 2.0
soon?
So in the CXF design, the client requests a javascript script through a
URL-based
command and then that script is used for the invocation of the remote
(REST) service.
Is the script on the server side generated at runtime based on the
implementation of the
service or is it pre-defined before the service is launched?
Daniel Kulp wrote:
On Thursday 18 March 2010 1:44:08 am Demetris wrote:
Hi all,
where would the server-side javascript code generotion be located in
the baseline?
Should be in:
http://svn.apache.org/repos/asf/cxf/trunk/rt/javascript
and the command line tool that would wrapper it:
http://svn.apache.org/repos/asf/cxf/trunk/tools/wsdlto/frontend/javascript/
I don't seem to be able to locate it. Is there documentation as to who
this generation
works? Is it derived from the service's WSDL file or does the user
navigate how this
generation should work?
It's based on the WSDL I believe. Or, more approriately, our service model
that would hold onto the wsdl information.
One of the responses I got from Benson as while ago read:
"you can create a 'dynamic client' that can talk to moderately
complex services. This requires the entire CXF stack on the client"
Are there any examples I can look at of such a 'dynamic client'. And
to what capacity is it 'dynamic'?
I have http servers that return WSDL 2.0 files (either REST or SOAP
sevices) and I would like to utilize them to generate javascript
clients for those services. From what I gathered so far, CXF and
WSO2 are the only mature projects doing this. If you do know of any
other ones please let me know. It seems to me that CXF can offer
such tools for me to build these clients so I wanted to find a bit
more about them. I have already started going over the online info.
Well, CXF doesn't support WSDL 2.0. Thus, that could be an issue.
Dan
Thanks very much in advace
