> +0 to making this a configurable option of axis, something like
> <parameter name="wsdl-mimetype" value="text/plain" />
There are already too many options available with regards to SOAP, WSDL,
etc. I say we pick one and stick with it.
>
> Actually, does WSDL have/need its own mime type like
application/wsdl+xml ?
> That way a proper WSDL viewer could bind to it?
I personally think this would be best, but I have doubts it would ever
happen. I believe the WSDL working group considered this at some point,
not I'm not entirely sure.
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(559) 587-1233 (office)
(700) 544-9035 (t/l)
Programming Web Services With SOAP
O'Reilly & Associates, ISBN 0596000952
Have I not commanded you? Be strong and courageous.
Do not be terrified, do not be discouraged, for the Lord your
God will be with you whereever you go. - Joshua 1:9
"Steve Loughran" <[EMAIL PROTECTED]> wrote on 12/16/2002 11:42:12 AM:
> ----- Original Message -----
> From: "Mike Spreitzer" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, December 16, 2002 09:03
> Subject: Re: Mozilla and automatic ?wsdl generation with Axis 1.0
>
> > I have noticed that Mozilla displays the XML usefully if there is an
HTTP
> > header saying the media type is "text/plain". And IE does OK in that
> > situation, as long as the content begins with an XML declaration (as
is
> > already the case for the WSDL returned by Axis). What do you think of
> > making Axis return an HTTP header claiming the media type to be
> > "text/plain"?
> -1 to a quick and dirty patch,
> we should have a text/xml header because it is text/xml. Same for the
> responses to any soap methods called using GET. Mozilla will get better
over
> time and there is no reason to lie for short term compatibility issues.
> +0 to making this a configurable option of axis, something like
> <parameter name="wsdl-mimetype" value="text/plain" />
>
> Actually, does WSDL have/need its own mime type like
application/wsdl+xml ?
> That way a proper WSDL viewer could bind to it?
> -steve
