[jira] [Resolved] (CXF-7704) False positive warning log: "Unable to recognize the addressing policy"
[ https://issues.apache.org/jira/browse/CXF-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reguel Wermelinger resolved CXF-7704. - Resolution: Fixed Fix Version/s: 3.2.5 > False positive warning log: "Unable to recognize the addressing policy" > --- > > Key: CXF-7704 > URL: https://issues.apache.org/jira/browse/CXF-7704 > Project: CXF > Issue Type: Improvement >Affects Versions: 3.2.4 >Reporter: Reguel Wermelinger >Priority: Minor > Fix For: 3.2.5 > > Attachments: greet-policy-wsaddressing.wsdl > > > CXF Client Calls to a service with a WS-Addressing policy fails with "Unable > to recognize the addressing policy". Even tough the policy works and the > required interceptors are correctly instantiated. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CXF-7705) Use Java EL api and impl bundle from Servicemix for cxf-bean-validation feature
[ https://issues.apache.org/jira/browse/CXF-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-7705. --- Resolution: Fixed Fix Version/s: 3.2.5 3.1.16 > Use Java EL api and impl bundle from Servicemix for cxf-bean-validation > feature > --- > > Key: CXF-7705 > URL: https://issues.apache.org/jira/browse/CXF-7705 > Project: CXF > Issue Type: Bug > Components: OSGi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.1.16, 3.2.5 > > > Ensure the SPI mechanism can work inside OSGi container -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CXF-7706) wsdl2java client jar generation generates a WSDL with empty schema location
Peter Stöckli created CXF-7706:
--
Summary: wsdl2java client jar generation generates a WSDL with
empty schema location
Key: CXF-7706
URL: https://issues.apache.org/jira/browse/CXF-7706
Project: CXF
Issue Type: Bug
Affects Versions: 3.2.4
Reporter: Peter Stöckli
Attachments: fileDownload.wsdl
When generating a client Jar with wsdl2java it can happen that the resulting
WSDL in the clientjar contains an import with an empty schema location:
{color:#80}http://www.w3.org/2005/05/xmlmime"{color}
{color:#ff}schemaLocation{color}{color:#00}={color}{color:#ff}""{color}{color:#80}/>{color}
This leads to following exception at runtime:
{code:java}
javax.wsdl.WSDLException: WSDLException (at
/wsdl:definitions/wsdl:types/xs:schema): faultCode=PARSER_ERROR: Problem
parsing
'jar:file://fileDownload.jar!/org/example/filedownload/client/'.:
org.xml.sax.SAXParseException: Premature end of file.{code}
If we edit the WSDL in the clientjar and remove the attribute
{{schemaLocation}} on the import tag the runtime the WSDLException does not
occur anymore.
How to reproduce:
# Download the attached WSDL (fileDownload.wsdl) created specifically for this
issue.
# Execute wsdl2java -d out -clientjar fileDownload.jar fileDownload.wsdl
# Open the fileDownload.wsdl in the root of the generated fileDownload.jar
# Now you should see the line: {{http://www.w3.org/2005/05/xmlmime"; schemaLocation=""/>}} (Note the
empty schema location)
Idea to fix:
Maybe don't write the {{schemaLocation}} attribute when it's empty string or
null?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7706) wsdl2java client jar generation generates a WSDL with empty schema location
[
https://issues.apache.org/jira/browse/CXF-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Stöckli updated CXF-7706:
---
Description:
When generating a client Jar with wsdl2java it can happen that the resulting
WSDL in the clientjar contains an import with an empty schema location:
{color:#80}http://www.w3.org/2005/05/xmlmime"{color}
{color:#ff}schemaLocation{color}{color:#00}={color}{color:#ff}""{color}{color:#80}/>{color}
This leads to following exception at runtime:
{code:java}
javax.wsdl.WSDLException: WSDLException (at
/wsdl:definitions/wsdl:types/xs:schema): faultCode=PARSER_ERROR: Problem
parsing
'jar:file://fileDownload.jar!/org/example/filedownload/client/'.:
org.xml.sax.SAXParseException: Premature end of file.{code}
If we edit the WSDL in the clientjar and remove the attribute
{{schemaLocation}} on the import tag the runtime the WSDLException does not
occur anymore.
How to reproduce:
# Download the attached WSDL (fileDownload.wsdl) created specifically for this
issue.
# Execute {{wsdl2java -d out -clientjar fileDownload.jar fileDownload.wsdl}}
# Open the fileDownload.wsdl in the root of the generated fileDownload.jar
# Now you should see the line: {{http://www.w3.org/2005/05/xmlmime"; schemaLocation=""/>}} (Note the
empty schema location)
Idea to fix:
Maybe don't write the {{schemaLocation}} attribute when it's empty string or
null?
was:
When generating a client Jar with wsdl2java it can happen that the resulting
WSDL in the clientjar contains an import with an empty schema location:
{color:#80}http://www.w3.org/2005/05/xmlmime"{color}
{color:#ff}schemaLocation{color}{color:#00}={color}{color:#ff}""{color}{color:#80}/>{color}
This leads to following exception at runtime:
{code:java}
javax.wsdl.WSDLException: WSDLException (at
/wsdl:definitions/wsdl:types/xs:schema): faultCode=PARSER_ERROR: Problem
parsing
'jar:file://fileDownload.jar!/org/example/filedownload/client/'.:
org.xml.sax.SAXParseException: Premature end of file.{code}
If we edit the WSDL in the clientjar and remove the attribute
{{schemaLocation}} on the import tag the runtime the WSDLException does not
occur anymore.
How to reproduce:
# Download the attached WSDL (fileDownload.wsdl) created specifically for this
issue.
# Execute wsdl2java -d out -clientjar fileDownload.jar fileDownload.wsdl
# Open the fileDownload.wsdl in the root of the generated fileDownload.jar
# Now you should see the line: {{http://www.w3.org/2005/05/xmlmime"; schemaLocation=""/>}} (Note the
empty schema location)
Idea to fix:
Maybe don't write the {{schemaLocation}} attribute when it's empty string or
null?
> wsdl2java client jar generation generates a WSDL with empty schema location
> ---
>
> Key: CXF-7706
> URL: https://issues.apache.org/jira/browse/CXF-7706
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Peter Stöckli
>Priority: Major
> Labels: wsdl2java
> Attachments: fileDownload.wsdl
>
>
> When generating a client Jar with wsdl2java it can happen that the resulting
> WSDL in the clientjar contains an import with an empty schema location:
> {color:#80} {color:#ff}namespace{color}{color:#00}={color}{color:#ff}"http://www.w3.org/2005/05/xmlmime"{color}
>
> {color:#ff}schemaLocation{color}{color:#00}={color}{color:#ff}""{color}{color:#80}/>{color}
> This leads to following exception at runtime:
>
> {code:java}
> javax.wsdl.WSDLException: WSDLException (at
> /wsdl:definitions/wsdl:types/xs:schema): faultCode=PARSER_ERROR: Problem
> parsing
> 'jar:file://fileDownload.jar!/org/example/filedownload/client/'.:
> org.xml.sax.SAXParseException: Premature end of file.{code}
>
> If we edit the WSDL in the clientjar and remove the attribute
> {{schemaLocation}} on the import tag the runtime the WSDLException does not
> occur anymore.
>
> How to reproduce:
> # Download the attached WSDL (fileDownload.wsdl) created specifically for
> this issue.
> # Execute {{wsdl2java -d out -clientjar fileDownload.jar fileDownload.wsdl}}
> # Open the fileDownload.wsdl in the root of the generated fileDownload.jar
> # Now you should see the line: {{ namespace="http://www.w3.org/2005/05/xmlmime"; schemaLocation=""/>}} (Note the
> empty schema location)
>
> Idea to fix:
> Maybe don't write the {{schemaLocation}} attribute when it's empty string or
> null?
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7706) wsdl2java client jar generation generates a WSDL with empty schema location
[
https://issues.apache.org/jira/browse/CXF-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Stöckli updated CXF-7706:
---
Description:
When generating a client Jar with wsdl2java it can happen that the resulting
WSDL in the clientjar contains an import with an empty schema location:
{color:#80}http://www.w3.org/2005/05/xmlmime"{color}
{color:#ff}schemaLocation{color}{color:#00}={color}{color:#ff}""{color}{color:#80}/>{color}
This leads to following exception at runtime:
{code:java}
javax.wsdl.WSDLException: WSDLException (at
/wsdl:definitions/wsdl:types/xs:schema): faultCode=PARSER_ERROR: Problem
parsing
'jar:file://fileDownload.jar!/org/example/filedownload/client/'.:
org.xml.sax.SAXParseException: Premature end of file.{code}
If we edit the WSDL in the clientjar and remove the attribute
{{schemaLocation}} on the import tag the runtime the WSDLException does not
occur anymore.
How to reproduce:
# Download the attached WSDL (fileDownload.wsdl) created specifically for this
issue.
# Execute {{wsdl2java -d out -clientjar fileDownload.jar fileDownload.wsdl}}
# Open the fileDownload.wsdl in the root of the generated fileDownload.jar
# Now you should see the line: {{http://www.w3.org/2005/05/xmlmime"; schemaLocation=""/>}} (Note the
empty schema location)
Idea on how to fix:
Maybe don't write the {{schemaLocation}} attribute when it's empty string or
null?
was:
When generating a client Jar with wsdl2java it can happen that the resulting
WSDL in the clientjar contains an import with an empty schema location:
{color:#80}http://www.w3.org/2005/05/xmlmime"{color}
{color:#ff}schemaLocation{color}{color:#00}={color}{color:#ff}""{color}{color:#80}/>{color}
This leads to following exception at runtime:
{code:java}
javax.wsdl.WSDLException: WSDLException (at
/wsdl:definitions/wsdl:types/xs:schema): faultCode=PARSER_ERROR: Problem
parsing
'jar:file://fileDownload.jar!/org/example/filedownload/client/'.:
org.xml.sax.SAXParseException: Premature end of file.{code}
If we edit the WSDL in the clientjar and remove the attribute
{{schemaLocation}} on the import tag the runtime the WSDLException does not
occur anymore.
How to reproduce:
# Download the attached WSDL (fileDownload.wsdl) created specifically for this
issue.
# Execute {{wsdl2java -d out -clientjar fileDownload.jar fileDownload.wsdl}}
# Open the fileDownload.wsdl in the root of the generated fileDownload.jar
# Now you should see the line: {{http://www.w3.org/2005/05/xmlmime"; schemaLocation=""/>}} (Note the
empty schema location)
Idea to fix:
Maybe don't write the {{schemaLocation}} attribute when it's empty string or
null?
> wsdl2java client jar generation generates a WSDL with empty schema location
> ---
>
> Key: CXF-7706
> URL: https://issues.apache.org/jira/browse/CXF-7706
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.2.4
>Reporter: Peter Stöckli
>Priority: Major
> Labels: wsdl2java
> Attachments: fileDownload.wsdl
>
>
> When generating a client Jar with wsdl2java it can happen that the resulting
> WSDL in the clientjar contains an import with an empty schema location:
> {color:#80} {color:#ff}namespace{color}{color:#00}={color}{color:#ff}"http://www.w3.org/2005/05/xmlmime"{color}
>
> {color:#ff}schemaLocation{color}{color:#00}={color}{color:#ff}""{color}{color:#80}/>{color}
> This leads to following exception at runtime:
>
> {code:java}
> javax.wsdl.WSDLException: WSDLException (at
> /wsdl:definitions/wsdl:types/xs:schema): faultCode=PARSER_ERROR: Problem
> parsing
> 'jar:file://fileDownload.jar!/org/example/filedownload/client/'.:
> org.xml.sax.SAXParseException: Premature end of file.{code}
>
> If we edit the WSDL in the clientjar and remove the attribute
> {{schemaLocation}} on the import tag the runtime the WSDLException does not
> occur anymore.
>
> How to reproduce:
> # Download the attached WSDL (fileDownload.wsdl) created specifically for
> this issue.
> # Execute {{wsdl2java -d out -clientjar fileDownload.jar fileDownload.wsdl}}
> # Open the fileDownload.wsdl in the root of the generated fileDownload.jar
> # Now you should see the line: {{ namespace="http://www.w3.org/2005/05/xmlmime"; schemaLocation=""/>}} (Note the
> empty schema location)
>
> Idea on how to fix:
> Maybe don't write the {{schemaLocation}} attribute when it's empty string or
> null?
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CXF-7707) JAXB doesn't (un)marshall property with @XmlElementRef
Radovan Netuka created CXF-7707: --- Summary: JAXB doesn't (un)marshall property with @XmlElementRef Key: CXF-7707 URL: https://issues.apache.org/jira/browse/CXF-7707 Project: CXF Issue Type: Bug Components: JAXB Databinding Reporter: Radovan Netuka When marshalling/unmarshalling JAX-WS response, the JAXB implementation ignores @XmlElementRef annotation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CXF-7707) JAXB doesn't (un)marshall property with @XmlElementRef
[ https://issues.apache.org/jira/browse/CXF-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435667#comment-16435667 ] ASF GitHub Bot commented on CXF-7707: - rnetuka opened a new pull request #404: [CXF-7707] JAXB doesn't (un)marshall property with @XmlElementRef URL: https://github.com/apache/cxf/pull/404 JIRA: https://issues.apache.org/jira/browse/CXF-7707 See downstream for more info: https://issues.jboss.org/browse/JBWS-4097 https://github.com/jboss/cxf/pull/18 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > JAXB doesn't (un)marshall property with @XmlElementRef > -- > > Key: CXF-7707 > URL: https://issues.apache.org/jira/browse/CXF-7707 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding >Reporter: Radovan Netuka >Priority: Major > > When marshalling/unmarshalling JAX-WS response, the JAXB implementation > ignores @XmlElementRef annotation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CXF-7707) JAXB doesn't (un)marshall property with @XmlElementRef
[ https://issues.apache.org/jira/browse/CXF-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst reassigned CXF-7707: --- Assignee: Dennis Kieselhorst > JAXB doesn't (un)marshall property with @XmlElementRef > -- > > Key: CXF-7707 > URL: https://issues.apache.org/jira/browse/CXF-7707 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding >Reporter: Radovan Netuka >Assignee: Dennis Kieselhorst >Priority: Major > > When marshalling/unmarshalling JAX-WS response, the JAXB implementation > ignores @XmlElementRef annotation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CXF-7707) JAXB doesn't (un)marshall property with @XmlElementRef
[ https://issues.apache.org/jira/browse/CXF-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436187#comment-16436187 ] Dennis Kieselhorst commented on CXF-7707: - Thanks for the PR, I've merged it. Could you please add a unittest for it? > JAXB doesn't (un)marshall property with @XmlElementRef > -- > > Key: CXF-7707 > URL: https://issues.apache.org/jira/browse/CXF-7707 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding >Reporter: Radovan Netuka >Assignee: Dennis Kieselhorst >Priority: Major > Fix For: 3.2.5 > > > When marshalling/unmarshalling JAX-WS response, the JAXB implementation > ignores @XmlElementRef annotation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CXF-7707) JAXB doesn't (un)marshall property with @XmlElementRef
[
https://issues.apache.org/jira/browse/CXF-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436186#comment-16436186
]
ASF GitHub Bot commented on CXF-7707:
-
deki closed pull request #404: [CXF-7707] JAXB doesn't (un)marshall property
with @XmlElementRef
URL: https://github.com/apache/cxf/pull/404
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBDataBinding.java
b/rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBDataBinding.java
index 6f224b11ad6..bfa4d3cd020 100644
--- a/rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBDataBinding.java
+++ b/rt/databinding/jaxb/src/main/java/org/apache/cxf/jaxb/JAXBDataBinding.java
@@ -47,6 +47,7 @@
import javax.xml.bind.Unmarshaller;
import javax.xml.bind.ValidationEventHandler;
import javax.xml.bind.annotation.XmlElement;
+import javax.xml.bind.annotation.XmlElementRef;
import javax.xml.bind.annotation.adapters.XmlAdapter;
import javax.xml.bind.annotation.adapters.XmlJavaTypeAdapter;
import javax.xml.namespace.QName;
@@ -798,6 +799,12 @@ private static Field getElField(String partName, final
Class wrapperType) {
&& partName.equals(el.name())) {
return field;
}
+
+XmlElementRef xmlElementRefAnnotation =
field.getAnnotation(XmlElementRef.class);
+if (xmlElementRefAnnotation != null &&
partName.equals(xmlElementRefAnnotation.name())) {
+return field;
+}
+
if (field.getName().equals(fieldName)) {
return field;
}
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> JAXB doesn't (un)marshall property with @XmlElementRef
> --
>
> Key: CXF-7707
> URL: https://issues.apache.org/jira/browse/CXF-7707
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
>Reporter: Radovan Netuka
>Assignee: Dennis Kieselhorst
>Priority: Major
> Fix For: 3.2.5
>
>
> When marshalling/unmarshalling JAX-WS response, the JAXB implementation
> ignores @XmlElementRef annotation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CXF-7707) JAXB doesn't (un)marshall property with @XmlElementRef
[ https://issues.apache.org/jira/browse/CXF-7707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated CXF-7707: Fix Version/s: 3.2.5 > JAXB doesn't (un)marshall property with @XmlElementRef > -- > > Key: CXF-7707 > URL: https://issues.apache.org/jira/browse/CXF-7707 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding >Reporter: Radovan Netuka >Assignee: Dennis Kieselhorst >Priority: Major > Fix For: 3.2.5 > > > When marshalling/unmarshalling JAX-WS response, the JAXB implementation > ignores @XmlElementRef annotation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
