Hello,
I would prefer to keep my schema types in a separate XSD file rather
than define them inside the WSDL file. So, I use an xsd:import to
accomplish this.
This appears to work well in CXF with one exception:
When I view the wsdl at
http://localhost:8080/myapp/services/MyService?wsdl the
Hello Again,
If I go to the root mapping of my CXF servlet (in my case,
http://localhost:8080/myapp/services/), it lists my deployed services.
The links however, are broken. Instead of:
http://localhost:8080/myapp/services/MyService?wsdl
it is:
Hi,
Hello,
I would prefer to keep my schema types in a separate XSD file rather
than define them inside the WSDL file. So, I use an xsd:import to
accomplish this.
This appears to work well in CXF with one exception:
When I view the wsdl at
http://localhost:8080/myapp/services/MyService?wsdl
Just FYI: this is a known restriction at this point. However, I'm
going to be working on fixing it this week. It is a big hold up for
some of the work I need done.
Dan
On Monday 16 April 2007 08:50, Christopher Moesel wrote:
Hello,
I would prefer to keep my schema types in a separate
Dan
That did the trick. I pointed the Eclipse update manager at the url as a new
remote site and the install proceeded as normal.
Dan and James thanks for your help.
Thanks
Tom
Dan Connelly-3 wrote:
The CXF plugin can be loaded into Eclipse using the Celtix remote site
in Eclipse
Hi
IMHO the easiest strategy would be to support
http://localhost:8080/myapp/services/MyService/wsdl queries,
with ?wsdl the only way to serve relative imports is to overwrite importing entities to use absolute URLs. '/wsdl' allows for the
composability on the client side while giving the
Hi Tom,
The CXF plugin update site has not been setup yet. That is the reason you got
error when try to use the update mechanism provided by Eclipse.
To play with CXF plugin, you also need to install Eclipse STP plugins. Which
will depend on some other eclipse packages such as EMF, GEF, WTP as
Okay,
Maybe I wrote to soon (If you get exit code 0 everything's okay, right?).
The install did apparently work. No reference to Tuscany but, of course, no
Tuscany. I guess were of to the Tuscany group.
Thanks
Tom
Tom Purcell wrote:
Dan
That did the trick. I pointed the Eclipse
Yes, it looks like the CXF code has a static value for content-type as
well, that will lower-case it for you.
AbstractHTTPDestination.java defines PROTOCOL_HEADERS_CONTENT_TYPE like
so:
public static final String PROTOCOL_HEADERS_CONTENT_TYPE =
Message.CONTENT_TYPE.toLowerCase();
So, if you
I believe there is some related documentation on Eclipse STP site, I
will update user guide to point to that doc.
Cheers,
Bo
Dan Diephouse wrote:
Hiya,
Any chance someone could write up some instructions on how to use the SOA
Tools project with CXF in the docs? I've received a few questions
10 matches
Mail list logo
