You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lin Sun (JIRA)" <ji...@apache.org> on 2007/03/20 17:34:32 UTC
[jira] Created: (GERONIMO-2999) when issing .wsdl request, the
content-type isn't set
when issing .wsdl request, the content-type isn't set
-----------------------------------------------------
Key: GERONIMO-2999
URL: https://issues.apache.org/jira/browse/GERONIMO-2999
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Tomcat
Affects Versions: 2.0
Reporter: Lin Sun
Fix For: 2.0
When running the calculator sample, we found out the response of the URL request http://localhost:8081/jaxws-calculator-1.0/CalculatorService.wsdl didn't have the proper content-type set which caused an exception from Axis2. The content-type should be set to "Content-Type: text/xml".
This is with tomcat and there should be some default mime mapping for jetty as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2999) when issuing .wsdl request, the
content-type isn't set
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun updated GERONIMO-2999:
------------------------------
Summary: when issuing .wsdl request, the content-type isn't set (was: when issing .wsdl request, the content-type isn't set)
> when issuing .wsdl request, the content-type isn't set
> ------------------------------------------------------
>
> Key: GERONIMO-2999
> URL: https://issues.apache.org/jira/browse/GERONIMO-2999
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.0
> Reporter: Lin Sun
> Fix For: 2.0
>
>
> When running the calculator sample, we found out the response of the URL request http://localhost:8081/jaxws-calculator-1.0/CalculatorService.wsdl didn't have the proper content-type set which caused an exception from Axis2. The content-type should be set to "Content-Type: text/xml".
> This is with tomcat and there should be some default mime mapping for jetty as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2999) when issuing .wsdl request, the
content-type isn't set
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482436 ]
Davanum Srinivas commented on GERONIMO-2999:
--------------------------------------------
Fixed for tomcat only in svn revision 520467
-- dims
> when issuing .wsdl request, the content-type isn't set
> ------------------------------------------------------
>
> Key: GERONIMO-2999
> URL: https://issues.apache.org/jira/browse/GERONIMO-2999
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.0
> Reporter: Lin Sun
> Fix For: 2.0
>
>
> When running the calculator sample, we found out the response of the URL request http://localhost:8081/jaxws-calculator-1.0/CalculatorService.wsdl didn't have the proper content-type set which caused an exception from Axis2. The content-type should be set to "Content-Type: text/xml".
> This is with tomcat and there should be some default mime mapping for jetty as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2999) when issuing .wsdl request, the
content-type isn't set
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482648 ]
David Jencks commented on GERONIMO-2999:
----------------------------------------
this should be fixed for jetty with rev 520756 (and 520754) but I don't know how to test.
> when issuing .wsdl request, the content-type isn't set
> ------------------------------------------------------
>
> Key: GERONIMO-2999
> URL: https://issues.apache.org/jira/browse/GERONIMO-2999
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.0
> Reporter: Lin Sun
> Fix For: 2.0
>
>
> When running the calculator sample, we found out the response of the URL request http://localhost:8081/jaxws-calculator-1.0/CalculatorService.wsdl didn't have the proper content-type set which caused an exception from Axis2. The content-type should be set to "Content-Type: text/xml".
> This is with tomcat and there should be some default mime mapping for jetty as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2999) when issuing .wsdl request, the
content-type isn't set
Posted by "Lin Sun (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun closed GERONIMO-2999.
-----------------------------
Resolution: Fixed
closing the issue. verified on tomcat.
> when issuing .wsdl request, the content-type isn't set
> ------------------------------------------------------
>
> Key: GERONIMO-2999
> URL: https://issues.apache.org/jira/browse/GERONIMO-2999
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.0-M5
> Reporter: Lin Sun
> Fix For: 2.0-M5
>
>
> When running the calculator sample, we found out the response of the URL request http://localhost:8081/jaxws-calculator-1.0/CalculatorService.wsdl didn't have the proper content-type set which caused an exception from Axis2. The content-type should be set to "Content-Type: text/xml".
> This is with tomcat and there should be some default mime mapping for jetty as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.