[jira] Created: (CXF-2891) Invalid WSDL when using (XSD) and ASM present in the classpath
Invalid WSDL when using (XSD) and ASM present in the
classpath
--
Key: CXF-2891
URL: https://issues.apache.org/jira/browse/CXF-2891
Project: CXF
Issue Type: Bug
Affects Versions: 2.2.9, 2.2.8, 2.2.7, 2.2.6
Reporter: Thomas Queste
CXF produces an invalid wsdl when a (XSD) is specified.
The error messages is : GRAVE: Schema element [...] references undefined type
[...]
The generated wsdl can not be read by SoapUI.
*BUT*, there is no error messages and *the WSDL is fully working* if :
* I remove the configuration element
* _OR_, the ASM library is completely excluded from the classpath
I think there is an incompatibility between the use of an XSD
(jaxws:schemaLocation) and the ASM library.
A sample webapp is attached and it makes easier to reproduce the problem (see
below for details).
h4. Versions
Tested with :
- CXF : 2.2.6 to 2.2.9
- ASM 2.2.3, 3.0, 3.1
CXF depends on ASM 2.2.3 but this dependency is optional.
ASM 3.1 is provided by JBoss so it will be available anyway in the classpath.
So I was not able to deploy the sample webapp on JBoss 5.
With ASM 1.5.3, there is no error.
h4. Full log messages
{code}
12 juil. 2010 15:25:42
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
GRAVE: Schema
element{http://creditcard.example.com/}getCreditCardStatusResponse references
undefined type
{http://creditcard.example.com/}getCreditCardStatusResponse for service
{http://creditcard.example.com/}
12 juil. 2010 15:25:42
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
GRAVE: Schema element {http://creditcard.example.com/}getCreditCardStatus
references undefined type
{http://creditcard.example.com/}getCreditCardStatus for service
{http://creditcard.example.com/}CreditCardWebServiceImplService.
{code}
h4. Full Jax-ws declaration
{code:xml}
schemas/creditCard.xsd
{code}
h4. The sample project
Attached is a very simple webapp which can be run with : mvn jetty:run
This is a maven project which contains a simple XSD.
The XSD is used to generate the sample java beans used in the webService java
code.
The XSD is also declared in the jaxws:endpoint in the spring applicationContext
file.
The error is shown in the console when the endpoint is created, when CXF is
started.
The pom.xml is fully documented and prepared to enable/disable the ASM
dependency.
The generated WSDL are also provided (with/without schemaLocation combined
with/without ASM).
Thanks for your help and the time you will take to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2891) Invalid WSDL when using (XSD) with ASM in the classpath
[
https://issues.apache.org/jira/browse/CXF-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Queste updated CXF-2891:
---
Comment: was deleted
(was: Sample project)
> Invalid WSDL when using (XSD) with ASM in the
> classpath
> ---
>
> Key: CXF-2891
> URL: https://issues.apache.org/jira/browse/CXF-2891
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.6, 2.2.7, 2.2.8, 2.2.9
>Reporter: Thomas Queste
> Attachments: creditcard-sample-project.zip
>
>
> CXF produces an invalid wsdl when both a (XSD) is
> specified and the ASM library is in the classpath.
> The error messages is : GRAVE: Schema element [...] references undefined type
> [...]
> The generated wsdl can not be read by SoapUI.
> *BUT*, there is no error messages and *the WSDL is fully working* if :
> * I remove the configuration element
> * _OR_, the ASM library is completely excluded from the classpath
> I think there is an incompatibility between the use of an XSD
> (jaxws:schemaLocation) and the ASM library.
> A sample webapp is attached and it makes easier to reproduce the problem (see
> below for details).
> h4. Versions
> Tested with :
> - CXF : 2.2.6 to 2.2.9
> - ASM 2.2.3, 3.0, 3.1
> CXF depends on ASM 2.2.3 but this dependency is optional.
> ASM 3.1 is provided by JBoss so it will be available anyway in the classpath.
> So I was not able to deploy the sample webapp on JBoss 5.
> With ASM 1.5.3, there is no error.
> h4. Full log messages
> {code}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema
> element{http://creditcard.example.com/}getCreditCardStatusResponse references
> undefined type
> {http://creditcard.example.com/}getCreditCardStatusResponse for service
> {http://creditcard.example.com/}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema element {http://creditcard.example.com/}getCreditCardStatus
> references undefined type
> {http://creditcard.example.com/}getCreditCardStatus for service
> {http://creditcard.example.com/}CreditCardWebServiceImplService.
> {code}
> h4. Full Jax-ws declaration
> {code:xml}
> id="creditCardWebService"
> implementor="com.example.creditcard.CreditCardWebServiceImpl"
> address="/creditCard">
>
> schemas/creditCard.xsd
>
>
> {code}
> h4. The sample project
> Attached is a very simple webapp which can be run with : mvn jetty:run
> This is a maven project which contains a simple XSD.
> The XSD is used to generate the sample java beans used in the webService java
> code.
> The XSD is also declared in the jaxws:endpoint in the spring
> applicationContext file.
> The error is shown in the console when the endpoint is created, when CXF is
> started.
> The pom.xml is fully documented and prepared to enable/disable the ASM
> dependency.
> The generated WSDL are also provided (with/without schemaLocation combined
> with/without ASM).
> Thanks for your help and the time you will take to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2891) Invalid WSDL when using (XSD) and ASM present in the classpath
[
https://issues.apache.org/jira/browse/CXF-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Queste updated CXF-2891:
---
Attachment: creditcard-sample-project.zip
Sample project
> Invalid WSDL when using (XSD) and ASM present in the
> classpath
> --
>
> Key: CXF-2891
> URL: https://issues.apache.org/jira/browse/CXF-2891
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.6, 2.2.7, 2.2.8, 2.2.9
>Reporter: Thomas Queste
> Attachments: creditcard-sample-project.zip
>
>
> CXF produces an invalid wsdl when a (XSD) is specified.
> The error messages is : GRAVE: Schema element [...] references undefined type
> [...]
> The generated wsdl can not be read by SoapUI.
> *BUT*, there is no error messages and *the WSDL is fully working* if :
> * I remove the configuration element
> * _OR_, the ASM library is completely excluded from the classpath
> I think there is an incompatibility between the use of an XSD
> (jaxws:schemaLocation) and the ASM library.
> A sample webapp is attached and it makes easier to reproduce the problem (see
> below for details).
> h4. Versions
> Tested with :
> - CXF : 2.2.6 to 2.2.9
> - ASM 2.2.3, 3.0, 3.1
> CXF depends on ASM 2.2.3 but this dependency is optional.
> ASM 3.1 is provided by JBoss so it will be available anyway in the classpath.
> So I was not able to deploy the sample webapp on JBoss 5.
> With ASM 1.5.3, there is no error.
> h4. Full log messages
> {code}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema
> element{http://creditcard.example.com/}getCreditCardStatusResponse references
> undefined type
> {http://creditcard.example.com/}getCreditCardStatusResponse for service
> {http://creditcard.example.com/}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema element {http://creditcard.example.com/}getCreditCardStatus
> references undefined type
> {http://creditcard.example.com/}getCreditCardStatus for service
> {http://creditcard.example.com/}CreditCardWebServiceImplService.
> {code}
> h4. Full Jax-ws declaration
> {code:xml}
> id="creditCardWebService"
> implementor="com.example.creditcard.CreditCardWebServiceImpl"
> address="/creditCard">
>
> schemas/creditCard.xsd
>
>
> {code}
> h4. The sample project
> Attached is a very simple webapp which can be run with : mvn jetty:run
> This is a maven project which contains a simple XSD.
> The XSD is used to generate the sample java beans used in the webService java
> code.
> The XSD is also declared in the jaxws:endpoint in the spring
> applicationContext file.
> The error is shown in the console when the endpoint is created, when CXF is
> started.
> The pom.xml is fully documented and prepared to enable/disable the ASM
> dependency.
> The generated WSDL are also provided (with/without schemaLocation combined
> with/without ASM).
> Thanks for your help and the time you will take to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2891) Invalid WSDL when using (XSD) with ASM in the classpath
[
https://issues.apache.org/jira/browse/CXF-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Queste updated CXF-2891:
---
Summary: Invalid WSDL when using (XSD) with ASM in
the classpath (was: Invalid WSDL when using (XSD) and
ASM present in the classpath)
> Invalid WSDL when using (XSD) with ASM in the
> classpath
> ---
>
> Key: CXF-2891
> URL: https://issues.apache.org/jira/browse/CXF-2891
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.6, 2.2.7, 2.2.8, 2.2.9
>Reporter: Thomas Queste
> Attachments: creditcard-sample-project.zip
>
>
> CXF produces an invalid wsdl when a (XSD) is specified.
> The error messages is : GRAVE: Schema element [...] references undefined type
> [...]
> The generated wsdl can not be read by SoapUI.
> *BUT*, there is no error messages and *the WSDL is fully working* if :
> * I remove the configuration element
> * _OR_, the ASM library is completely excluded from the classpath
> I think there is an incompatibility between the use of an XSD
> (jaxws:schemaLocation) and the ASM library.
> A sample webapp is attached and it makes easier to reproduce the problem (see
> below for details).
> h4. Versions
> Tested with :
> - CXF : 2.2.6 to 2.2.9
> - ASM 2.2.3, 3.0, 3.1
> CXF depends on ASM 2.2.3 but this dependency is optional.
> ASM 3.1 is provided by JBoss so it will be available anyway in the classpath.
> So I was not able to deploy the sample webapp on JBoss 5.
> With ASM 1.5.3, there is no error.
> h4. Full log messages
> {code}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema
> element{http://creditcard.example.com/}getCreditCardStatusResponse references
> undefined type
> {http://creditcard.example.com/}getCreditCardStatusResponse for service
> {http://creditcard.example.com/}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema element {http://creditcard.example.com/}getCreditCardStatus
> references undefined type
> {http://creditcard.example.com/}getCreditCardStatus for service
> {http://creditcard.example.com/}CreditCardWebServiceImplService.
> {code}
> h4. Full Jax-ws declaration
> {code:xml}
> id="creditCardWebService"
> implementor="com.example.creditcard.CreditCardWebServiceImpl"
> address="/creditCard">
>
> schemas/creditCard.xsd
>
>
> {code}
> h4. The sample project
> Attached is a very simple webapp which can be run with : mvn jetty:run
> This is a maven project which contains a simple XSD.
> The XSD is used to generate the sample java beans used in the webService java
> code.
> The XSD is also declared in the jaxws:endpoint in the spring
> applicationContext file.
> The error is shown in the console when the endpoint is created, when CXF is
> started.
> The pom.xml is fully documented and prepared to enable/disable the ASM
> dependency.
> The generated WSDL are also provided (with/without schemaLocation combined
> with/without ASM).
> Thanks for your help and the time you will take to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2891) Invalid WSDL when using (XSD) with ASM in the classpath
[
https://issues.apache.org/jira/browse/CXF-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Queste updated CXF-2891:
---
Description:
CXF produces an invalid wsdl when both a (XSD) is
specified and the ASM library is in the classpath.
The error messages is : GRAVE: Schema element [...] references undefined type
[...]
The generated wsdl can not be read by SoapUI.
*BUT*, there is no error messages and *the WSDL is fully working* if :
* I remove the configuration element
* _OR_, the ASM library is completely excluded from the classpath
I think there is an incompatibility between the use of an XSD
(jaxws:schemaLocation) and the ASM library.
A sample webapp is attached and it makes easier to reproduce the problem (see
below for details).
h4. Versions
Tested with :
- CXF : 2.2.6 to 2.2.9
- ASM 2.2.3, 3.0, 3.1
CXF depends on ASM 2.2.3 but this dependency is optional.
ASM 3.1 is provided by JBoss so it will be available anyway in the classpath.
So I was not able to deploy the sample webapp on JBoss 5.
With ASM 1.5.3, there is no error.
h4. Full log messages
{code}
12 juil. 2010 15:25:42
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
GRAVE: Schema
element{http://creditcard.example.com/}getCreditCardStatusResponse references
undefined type
{http://creditcard.example.com/}getCreditCardStatusResponse for service
{http://creditcard.example.com/}
12 juil. 2010 15:25:42
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
GRAVE: Schema element {http://creditcard.example.com/}getCreditCardStatus
references undefined type
{http://creditcard.example.com/}getCreditCardStatus for service
{http://creditcard.example.com/}CreditCardWebServiceImplService.
{code}
h4. Full Jax-ws declaration
{code:xml}
schemas/creditCard.xsd
{code}
h4. The sample project
Attached is a very simple webapp which can be run with : mvn jetty:run
This is a maven project which contains a simple XSD.
The XSD is used to generate the sample java beans used in the webService java
code.
The XSD is also declared in the jaxws:endpoint in the spring applicationContext
file.
The error is shown in the console when the endpoint is created, when CXF is
started.
The pom.xml is fully documented and prepared to enable/disable the ASM
dependency.
The generated WSDL are also provided (with/without schemaLocation combined
with/without ASM).
Thanks for your help and the time you will take to fix this.
was:
CXF produces an invalid wsdl when a (XSD) is specified.
The error messages is : GRAVE: Schema element [...] references undefined type
[...]
The generated wsdl can not be read by SoapUI.
*BUT*, there is no error messages and *the WSDL is fully working* if :
* I remove the configuration element
* _OR_, the ASM library is completely excluded from the classpath
I think there is an incompatibility between the use of an XSD
(jaxws:schemaLocation) and the ASM library.
A sample webapp is attached and it makes easier to reproduce the problem (see
below for details).
h4. Versions
Tested with :
- CXF : 2.2.6 to 2.2.9
- ASM 2.2.3, 3.0, 3.1
CXF depends on ASM 2.2.3 but this dependency is optional.
ASM 3.1 is provided by JBoss so it will be available anyway in the classpath.
So I was not able to deploy the sample webapp on JBoss 5.
With ASM 1.5.3, there is no error.
h4. Full log messages
{code}
12 juil. 2010 15:25:42
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
GRAVE: Schema
element{http://creditcard.example.com/}getCreditCardStatusResponse references
undefined type
{http://creditcard.example.com/}getCreditCardStatusResponse for service
{http://creditcard.example.com/}
12 juil. 2010 15:25:42
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
GRAVE: Schema element {http://creditcard.example.com/}getCreditCardStatus
references undefined type
{http://creditcard.example.com/}getCreditCardStatus for service
{http://creditcard.example.com/}CreditCardWebServiceImplService.
{code}
h4. Full Jax-ws declaration
{code:xml}
schemas/creditCard.xsd
{code}
h4. The sample project
Attached is a very simple webapp which can be run with : mvn jetty:run
This is a maven project which contains a simple XSD.
The XSD is used to generate the sample java beans used in the webService java
code.
The XSD is also declared in the jaxws:endpoint in the spring applicationContext
file.
The error is shown in the console when the endpoint is created, when CXF is
started.
The pom.xml is fully documented and prepared to enable/disable the ASM
dependency.
The generated WSDL are also provided (with/without schemaLocation combined
with/without ASM).
Thanks for your help and the time you will take to fix this.
> Invalid WSDL when using (XSD) with ASM in the
> classpath
> ---
>
> Key: CXF-
[jira] Created: (CXF-2892) AttachmentSerializer outputs "xop+xml" as body content type even XOP is not enabled
AttachmentSerializer outputs "xop+xml" as body content type even XOP is not enabled --- Key: CXF-2892 URL: https://issues.apache.org/jira/browse/CXF-2892 Project: CXF Issue Type: Bug Components: Core Reporter: William Tam Priority: Minor Fix For: 2.3, 2.2.10 Please check the attached patch. It looks like the content-type should be "text/xml" for the body (http://www.w3.org/TR/SOAP-attachments#SOAPMultipart) if XOP is not enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2892) AttachmentSerializer outputs "xop+xml" as body content type even XOP is not enabled
[ https://issues.apache.org/jira/browse/CXF-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam updated CXF-2892: - Attachment: CXF-2892.patch > AttachmentSerializer outputs "xop+xml" as body content type even XOP is not > enabled > --- > > Key: CXF-2892 > URL: https://issues.apache.org/jira/browse/CXF-2892 > Project: CXF > Issue Type: Bug > Components: Core >Reporter: William Tam >Priority: Minor > Fix For: 2.3, 2.2.10 > > Attachments: CXF-2892.patch > > > Please check the attached patch. It looks like the content-type should be > "text/xml" for the body (http://www.w3.org/TR/SOAP-attachments#SOAPMultipart) > if XOP is not enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2891) Invalid WSDL when using (XSD) with ASM in the classpath
[
https://issues.apache.org/jira/browse/CXF-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888030#action_12888030
]
Glen Mazza commented on CXF-2891:
-
The email thread on this issue is here;
http://cxf.547215.n5.nabble.com/Invalid-WSDL-with-a-Jax-ws-schemaLocation-XSD-specified-td1046395.html
> Invalid WSDL when using (XSD) with ASM in the
> classpath
> ---
>
> Key: CXF-2891
> URL: https://issues.apache.org/jira/browse/CXF-2891
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.6, 2.2.7, 2.2.8, 2.2.9
>Reporter: Thomas Queste
> Attachments: creditcard-sample-project.zip
>
>
> CXF produces an invalid wsdl when both a (XSD) is
> specified and the ASM library is in the classpath.
> The error messages is : GRAVE: Schema element [...] references undefined type
> [...]
> The generated wsdl can not be read by SoapUI.
> *BUT*, there is no error messages and *the WSDL is fully working* if :
> * I remove the configuration element
> * _OR_, the ASM library is completely excluded from the classpath
> I think there is an incompatibility between the use of an XSD
> (jaxws:schemaLocation) and the ASM library.
> A sample webapp is attached and it makes easier to reproduce the problem (see
> below for details).
> h4. Versions
> Tested with :
> - CXF : 2.2.6 to 2.2.9
> - ASM 2.2.3, 3.0, 3.1
> CXF depends on ASM 2.2.3 but this dependency is optional.
> ASM 3.1 is provided by JBoss so it will be available anyway in the classpath.
> So I was not able to deploy the sample webapp on JBoss 5.
> With ASM 1.5.3, there is no error.
> h4. Full log messages
> {code}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema
> element{http://creditcard.example.com/}getCreditCardStatusResponse references
> undefined type
> {http://creditcard.example.com/}getCreditCardStatusResponse for service
> {http://creditcard.example.com/}
> 12 juil. 2010 15:25:42
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean
> GRAVE: Schema element {http://creditcard.example.com/}getCreditCardStatus
> references undefined type
> {http://creditcard.example.com/}getCreditCardStatus for service
> {http://creditcard.example.com/}CreditCardWebServiceImplService.
> {code}
> h4. Full Jax-ws declaration
> {code:xml}
> id="creditCardWebService"
> implementor="com.example.creditcard.CreditCardWebServiceImpl"
> address="/creditCard">
>
> schemas/creditCard.xsd
>
>
> {code}
> h4. The sample project
> Attached is a very simple webapp which can be run with : mvn jetty:run
> This is a maven project which contains a simple XSD.
> The XSD is used to generate the sample java beans used in the webService java
> code.
> The XSD is also declared in the jaxws:endpoint in the spring
> applicationContext file.
> The error is shown in the console when the endpoint is created, when CXF is
> started.
> The pom.xml is fully documented and prepared to enable/disable the ASM
> dependency.
> The generated WSDL are also provided (with/without schemaLocation combined
> with/without ASM).
> Thanks for your help and the time you will take to fix this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2892) AttachmentSerializer outputs "xop+xml" as body content type even XOP is not enabled
[ https://issues.apache.org/jira/browse/CXF-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888169#action_12888169 ] Willem Jiang commented on CXF-2892: --- Applied patch into cxf trunk and cxf-2.2.x branch with thanks to William. > AttachmentSerializer outputs "xop+xml" as body content type even XOP is not > enabled > --- > > Key: CXF-2892 > URL: https://issues.apache.org/jira/browse/CXF-2892 > Project: CXF > Issue Type: Bug > Components: Core >Reporter: William Tam >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.3, 2.2.10 > > Attachments: CXF-2892.patch > > > Please check the attached patch. It looks like the content-type should be > "text/xml" for the body (http://www.w3.org/TR/SOAP-attachments#SOAPMultipart) > if XOP is not enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2892) AttachmentSerializer outputs "xop+xml" as body content type even XOP is not enabled
[ https://issues.apache.org/jira/browse/CXF-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CXF-2892: - Assignee: Willem Jiang > AttachmentSerializer outputs "xop+xml" as body content type even XOP is not > enabled > --- > > Key: CXF-2892 > URL: https://issues.apache.org/jira/browse/CXF-2892 > Project: CXF > Issue Type: Bug > Components: Core >Reporter: William Tam >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.3, 2.2.10 > > Attachments: CXF-2892.patch > > > Please check the attached patch. It looks like the content-type should be > "text/xml" for the body (http://www.w3.org/TR/SOAP-attachments#SOAPMultipart) > if XOP is not enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
