[jira] [Commented] (CXF-4570) Attachment Header Content-ID conversion
[
https://issues.apache.org/jira/browse/CXF-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13477654#comment-13477654
]
Jinhua Wang commented on CXF-4570:
--
Snippet code for copying attachment from cxf to jdk simulation.
{code}
import java.util.Iterator;
import javax.xml.soap.AttachmentPart;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.MimeHeader;
import javax.xml.soap.SOAPMessage;
public class JDKAttachmentTest {
private static final String STR_CONTENT_ID = Content-ID;
public static void main(String[] args) throws Exception {
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage soapMessage = messageFactory.createMessage();
AttachmentPart attachmentPart =
soapMessage.createAttachmentPart();
attachmentPart.setContentId(foo);
attachmentPart.addMimeHeader(STR_CONTENT_ID, foo);
soapMessage.addAttachmentPart(attachmentPart);
Iterator? attIterator = soapMessage.getAttachments();
while(attIterator.hasNext()){
AttachmentPart att = (AttachmentPart)attIterator.next();
Iterator? headerIterator = att.getAllMimeHeaders();
while(headerIterator.hasNext()){
MimeHeader header =
(MimeHeader)headerIterator.next();
System.out.println(header.getName() + : +
header.getValue());
}
}
}
}
{code}
output:
{code}
Content-ID:foo
Content-ID:foo
{code}
Attachment Header Content-ID conversion
---
Key: CXF-4570
URL: https://issues.apache.org/jira/browse/CXF-4570
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Reporter: Jinhua Wang
Attachments: AttachmentUtil.java.patch
I have a migrating problem for headers in attachment.
For example, the message sent out contains Content-ID:foo,
Content-ID header value is foo instead of foo at server side.
When creating attachment of the following code:
org.apache.cxf.attachment.AttachmentUtil.createAttachment(InputStream,
InternetHeaders)
There's a id conversion at first. But in the following header processing,
there's no id conversion for Content-ID.
Since Content-ID conversion is needed for id(new AttachmentImpl(id)), I
think it is also useful for headers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4573) WADL to Java generator loses the namespace info for types from imported schemas
[ https://issues.apache.org/jira/browse/CXF-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-4573. --- Resolution: Fixed Fix Version/s: 2.6 2.7.1 2.5.7 WADL to Java generator loses the namespace info for types from imported schemas --- Key: CXF-4573 URL: https://issues.apache.org/jira/browse/CXF-4573 Project: CXF Issue Type: Bug Components: JAX-RS Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Fix For: 2.5.7, 2.7.1, 2.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4570) Attachment Header Content-ID conversion
[ https://issues.apache.org/jira/browse/CXF-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13477752#comment-13477752 ] Aki Yoshida commented on CXF-4570: -- org.apache.cxf.attachment.AttachmentDeserializerTest's testDeserializerSwA uses this create attachment method and this is not getting any issue (only the bracketed id is placed in the headers and when this message is reserialized, you see only the bracketed content id). So, I don't know why you are getting the unbracketed one. So, I am not sure if AttachmentUtil itself really has some issue. Attachment Header Content-ID conversion --- Key: CXF-4570 URL: https://issues.apache.org/jira/browse/CXF-4570 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Reporter: Jinhua Wang Attachments: AttachmentUtil.java.patch I have a migrating problem for headers in attachment. For example, the message sent out contains Content-ID:foo, Content-ID header value is foo instead of foo at server side. When creating attachment of the following code: org.apache.cxf.attachment.AttachmentUtil.createAttachment(InputStream, InternetHeaders) There's a id conversion at first. But in the following header processing, there's no id conversion for Content-ID. Since Content-ID conversion is needed for id(new AttachmentImpl(id)), I think it is also useful for headers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4570) Attachment Header Content-ID conversion
[
https://issues.apache.org/jira/browse/CXF-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13477784#comment-13477784
]
Jinhua Wang commented on CXF-4570:
--
There are two attachment implementation classes, one is from cxf framework and
another if from jdk. Content-ID is stored in *id* field in cxf
implementation. On the contrary Content-ID is stroed in headers in jdk
implementation.
*org.apache.cxf.attachment.AttachmentImpl*(cxf framework)
{code}
private String id;
private MapString, String headers = new HashMapString, String();
{code}
*com.sun.xml.internal.messaging.saaj.soap.AttachmentPartImpl*
{code}
private final MimeHeaders headers;
public void setMimeHeader(String paramString1, String paramString2) {
this.headers.setHeader(paramString1, paramString2);
}
public void addMimeHeader(String paramString1, String paramString2) {
this.headers.addHeader(paramString1, paramString2);
}
{code}
*javax.xml.soap.MimeHeaders*
{code}
private Vector headers;
{code}
When copying content from cxf attachment to jdk attachment, both Content-ID
values are copied to *Vector headers*.
Attachment Header Content-ID conversion
---
Key: CXF-4570
URL: https://issues.apache.org/jira/browse/CXF-4570
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Reporter: Jinhua Wang
Attachments: AttachmentUtil.java.patch
I have a migrating problem for headers in attachment.
For example, the message sent out contains Content-ID:foo,
Content-ID header value is foo instead of foo at server side.
When creating attachment of the following code:
org.apache.cxf.attachment.AttachmentUtil.createAttachment(InputStream,
InternetHeaders)
There's a id conversion at first. But in the following header processing,
there's no id conversion for Content-ID.
Since Content-ID conversion is needed for id(new AttachmentImpl(id)), I
think it is also useful for headers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4570) Attachment Header Content-ID conversion
[ https://issues.apache.org/jira/browse/CXF-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinhua Wang updated CXF-4570: - Attachment: 04.png org.apache.cxf.attachment.AttachmentImpl instance when running test org.apache.cxf.attachment.AttachmentDeserializerTest.testDeserializerSwA() Attachment Header Content-ID conversion --- Key: CXF-4570 URL: https://issues.apache.org/jira/browse/CXF-4570 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Reporter: Jinhua Wang Attachments: 04.png, AttachmentUtil.java.patch I have a migrating problem for headers in attachment. For example, the message sent out contains Content-ID:foo, Content-ID header value is foo instead of foo at server side. When creating attachment of the following code: org.apache.cxf.attachment.AttachmentUtil.createAttachment(InputStream, InternetHeaders) There's a id conversion at first. But in the following header processing, there's no id conversion for Content-ID. Since Content-ID conversion is needed for id(new AttachmentImpl(id)), I think it is also useful for headers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4578) SearchConditionVisitor should be parameterized on the query type
Sergey Beryozkin created CXF-4578:
-
Summary: SearchConditionVisitor should be parameterized on the
query type
Key: CXF-4578
URL: https://issues.apache.org/jira/browse/CXF-4578
Project: CXF
Issue Type: Improvement
Components: JAX-RS
Environment: This was suggested by Jeff Wang.
It should be possible to type:
{code:java}
SearchConditionVisitorBook, TypedQueryBook visitor = new
JPATypedQueryVisitorBook();
searchCondition.visit(visitor);
TypedQueryBook query = visitor.getQuery();
{code}
Reporter: Sergey Beryozkin
Assignee: Sergey Beryozkin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4572) GZIPOutInterceptor not negotiating first without compressing
[ https://issues.apache.org/jira/browse/CXF-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13477921#comment-13477921 ] Glen Mazza commented on CXF-4572: - A simple test case can be made by taking the Double It tutorial[1], replacing two classes with those here[2], and then running mvn clean install tomcat:redeploy to deploy the server and mvn exec:exec from the client subdirectory to activate the SOAP client. Wireshark will show the results. [1] https://github.com/gmazza/blog-samples/tree/master/web_service_tutorial [2] https://github.com/gmazza/blog-samples/tree/master/compressing_soap_messages/cxf-gzip GZIPOutInterceptor not negotiating first without compressing Key: CXF-4572 URL: https://issues.apache.org/jira/browse/CXF-4572 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Affects Versions: 2.7.0 Reporter: Glen Mazza Priority: Minor The GZIPOutInterceptor, like the Fast Infoset out interceptor, is supposed to negotiate first with the server prior to sending a compressed message as stated in the docs (http://cxf.apache.org/docs/annotations.html#Annotations-GZIP). I.e. the first SOAP request, while containing the Accept-Encoding: gzip HTTP header, should still be uncompressed (only subsequent calls compressed) but it is still compressing the message with the first soap request. This results in servers not configured for GZIP to raise can't parse errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4579) Exchange's out message is not set for recovered outbound WS-RM messages
Aki Yoshida created CXF-4579: Summary: Exchange's out message is not set for recovered outbound WS-RM messages Key: CXF-4579 URL: https://issues.apache.org/jira/browse/CXF-4579 Project: CXF Issue Type: Bug Components: WS-* Components Affects Versions: 2.6.3 Reporter: Aki Yoshida Assignee: Aki Yoshida Priority: Minor When recovering outbound WS-RM messages from the storage for retransmission, the associated exchange object's outbound message is not set. This may result in NPE in some scenarios. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4570) Attachment Header Content-ID conversion
[ https://issues.apache.org/jira/browse/CXF-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4570. -- Resolution: Fixed Fix Version/s: 2.7.1 2.6.4 Assignee: Daniel Kulp Cleaned up the SAAJIn/Out stuff a little to only call the setContentID if a getContentID call returns null after setting all the headers. Thus, this should fix the double header issue. Attachment Header Content-ID conversion --- Key: CXF-4570 URL: https://issues.apache.org/jira/browse/CXF-4570 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Reporter: Jinhua Wang Assignee: Daniel Kulp Fix For: 2.6.4, 2.7.1 Attachments: 04.png, AttachmentUtil.java.patch I have a migrating problem for headers in attachment. For example, the message sent out contains Content-ID:foo, Content-ID header value is foo instead of foo at server side. When creating attachment of the following code: org.apache.cxf.attachment.AttachmentUtil.createAttachment(InputStream, InternetHeaders) There's a id conversion at first. But in the following header processing, there's no id conversion for Content-ID. Since Content-ID conversion is needed for id(new AttachmentImpl(id)), I think it is also useful for headers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4575) Could not find any node with XPath expression
[
https://issues.apache.org/jira/browse/CXF-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-4575:
-
Description:
I have wsdl and xsd in files separate when attempt generate java files show the
next error:
[ERROR] Failed to execute goal org.apache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java
(generate-sources) on project svOrder: Execution generate-sources of goal org.a
pache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java failed: Could not find any node wit
h the XPath expression: //wsdl:definitions/wsdl:types/xs:schema[@targetNamespace
='http://www.axcess-financial.com.pe/schema/transaction'] - [Help 1]
this is code chunk code from pom.xml
{code}
execution
idgenerate-sources/id
phasegenerate-sources/phase
configuration
sourceRoot${basedir}/src/main/java/sourceRoot
wsdlOptions
wsdlOption
wsdl${basedir}/src/main/resources/wsdl/WSOrder.wsdl/wsdl
wsdlLocationclasspath:wsdl/WSOrder.wsdl/wsdlLocation
extraargs
extraarg-b/extraarg
extraarg${basedir}/src/main/resources/binding.xml/extraarg
/extraargs
/wsdlOption
/wsdlOptions
/configuration
goals
goalwsdl2java/goal
/goals
/execution
{code}
this is code chunk code from binding.xml
{code}
?xml version=1.0 encoding=UTF-8?
jaxws:bindings wsdlLocation=wsdl/WSOrder.wsdl
xmlns:jaxws=http://java.sun.com/xml/ns/jaxws;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
jaxws:bindings schemaLocation=wsdl/Order.xsd
node=wsdl:definitions/wsdl:types/xs:schema[@targetNamespace='http://www.axcess-financial.com.pe/schema/transaction']
jxb:globalBindings xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
jxb:serializable uid=15102012/
/jxb:globalBindings
/jaxws:bindings
/jaxws:bindings
{code}
was:
I have wsdl and xsd in files separate when attempt generate java files show the
next error:
[ERROR] Failed to execute goal org.apache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java
(generate-sources) on project svOrder: Execution generate-sources of goal org.a
pache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java failed: Could not find any node wit
h the XPath expression: //wsdl:definitions/wsdl:types/xs:schema[@targetNamespace
='http://www.axcess-financial.com.pe/schema/transaction'] - [Help 1]
this is code chunk code from pom.xml
execution
idgenerate-sources/id
phasegenerate-sources/phase
configuration
sourceRoot${basedir}/src/main/java/sourceRoot
wsdlOptions
wsdlOption
wsdl${basedir}/src/main/resources/wsdl/WSOrder.wsdl/wsdl
wsdlLocationclasspath:wsdl/WSOrder.wsdl/wsdlLocation
extraargs
extraarg-b/extraarg
extraarg${basedir}/src/main/resources/binding.xml/extraarg
/extraargs
/wsdlOption
/wsdlOptions
/configuration
goals
goalwsdl2java/goal
/goals
/execution
this is code chunk code from binding.xml
?xml version=1.0 encoding=UTF-8?
jaxws:bindings wsdlLocation=wsdl/WSOrder.wsdl
xmlns:jaxws=http://java.sun.com/xml/ns/jaxws;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
jaxws:bindings schemaLocation=wsdl/Order.xsd
node=wsdl:definitions/wsdl:types/xs:schema[@targetNamespace='http://www.axcess-financial.com.pe/schema/transaction']
jxb:globalBindings xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
jxb:serializable uid=15102012/
/jxb:globalBindings
/jaxws:bindings
/jaxws:bindings
Could not find any node with XPath expression
-
Key: CXF-4575
URL: https://issues.apache.org/jira/browse/CXF-4575
Project: CXF
Issue Type: Bug
Affects Versions: 2.7.0
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
Default locale: es_PE, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Osmar Miraval
[jira] [Updated] (CXF-4575) Could not find any node with XPath expression
[
https://issues.apache.org/jira/browse/CXF-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Osmar Miraval updated CXF-4575:
---
Description:
I have wsdl and xsd in files separate when attempt generate java files show the
next error:
[ERROR] Failed to execute goal org.apache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java
(generate-sources) on project svOrder: Execution generate-sources of goal org.a
pache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java failed: Could not find any node wit
h the XPath expression: //wsdl:definitions/wsdl:types/xs:schema[@targetNamespace
='http://www.axcess-financial.com.pe/schema/transaction'] - [Help 1]
this is code chunk from pom.xml
execution
idgenerate-sources/id
phasegenerate-sources/phase
configuration
sourceRoot${basedir}/src/main/java/sourceRoot
wsdlOptions
wsdlOption
wsdl${basedir}/src/main/resources/wsdl/WSOrder.wsdl/wsdl
wsdlLocationclasspath:wsdl/WSOrder.wsdl/wsdlLocation
extraargs
extraarg-b/extraarg
extraarg${basedir}/src/main/resources/binding.xml/extraarg
/extraargs
/wsdlOption
/wsdlOptions
/configuration
goals
goalwsdl2java/goal
/goals
/execution
{code}
this is code chunk from binding.xml
?xml version=1.0 encoding=UTF-8?
jaxws:bindings wsdlLocation=wsdl/WSOrder.wsdl
xmlns:jaxws=http://java.sun.com/xml/ns/jaxws;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
jaxws:bindings schemaLocation=wsdl/Order.xsd
node=wsdl:definitions/wsdl:types/xs:schema[@targetNamespace='http://www.axcess-financial.com.pe/schema/transaction']
jxb:globalBindings xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
jxb:serializable uid=15102012/
/jxb:globalBindings
/jaxws:bindings
/jaxws:bindings
{code}
was:
I have wsdl and xsd in files separate when attempt generate java files show the
next error:
[ERROR] Failed to execute goal org.apache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java
(generate-sources) on project svOrder: Execution generate-sources of goal org.a
pache.cxf:cxf-codegen-plugin:2.7.0:wsdl2java failed: Could not find any node wit
h the XPath expression: //wsdl:definitions/wsdl:types/xs:schema[@targetNamespace
='http://www.axcess-financial.com.pe/schema/transaction'] - [Help 1]
this is code chunk code from pom.xml
{code}
execution
idgenerate-sources/id
phasegenerate-sources/phase
configuration
sourceRoot${basedir}/src/main/java/sourceRoot
wsdlOptions
wsdlOption
wsdl${basedir}/src/main/resources/wsdl/WSOrder.wsdl/wsdl
wsdlLocationclasspath:wsdl/WSOrder.wsdl/wsdlLocation
extraargs
extraarg-b/extraarg
extraarg${basedir}/src/main/resources/binding.xml/extraarg
/extraargs
/wsdlOption
/wsdlOptions
/configuration
goals
goalwsdl2java/goal
/goals
/execution
{code}
this is code chunk code from binding.xml
{code}
?xml version=1.0 encoding=UTF-8?
jaxws:bindings wsdlLocation=wsdl/WSOrder.wsdl
xmlns:jaxws=http://java.sun.com/xml/ns/jaxws;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
jaxws:bindings schemaLocation=wsdl/Order.xsd
node=wsdl:definitions/wsdl:types/xs:schema[@targetNamespace='http://www.axcess-financial.com.pe/schema/transaction']
jxb:globalBindings xmlns:jxb=http://java.sun.com/xml/ns/jaxb;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
jxb:serializable uid=15102012/
/jxb:globalBindings
/jaxws:bindings
/jaxws:bindings
{code}
Could not find any node with XPath expression
-
Key: CXF-4575
URL: https://issues.apache.org/jira/browse/CXF-4575
Project: CXF
Issue Type: Bug
Affects Versions: 2.7.0
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
Default locale: es_PE, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Osmar Miraval
[jira] [Created] (CXF-4580) InjectionUtils can not handle boolean properties with getters starting from 'is'
Sergey Beryozkin created CXF-4580: - Summary: InjectionUtils can not handle boolean properties with getters starting from 'is' Key: CXF-4580 URL: https://issues.apache.org/jira/browse/CXF-4580 Project: CXF Issue Type: Bug Components: JAX-RS Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4580) InjectionUtils can not handle boolean properties with getters starting from 'is'
[ https://issues.apache.org/jira/browse/CXF-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin resolved CXF-4580. --- Resolution: Fixed Fix Version/s: 2.7.1 2.6.4 2.5.7 InjectionUtils can not handle boolean properties with getters starting from 'is' Key: CXF-4580 URL: https://issues.apache.org/jira/browse/CXF-4580 Project: CXF Issue Type: Bug Components: JAX-RS Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Priority: Minor Fix For: 2.5.7, 2.6.4, 2.7.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4566) StaxTransformFeature outTransformElements does not work when converting namespaces
[ https://issues.apache.org/jira/browse/CXF-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-4566. -- Resolution: Fixed Fix Version/s: 2.7.1 2.6.4 2.5.7 StaxTransformFeature outTransformElements does not work when converting namespaces -- Key: CXF-4566 URL: https://issues.apache.org/jira/browse/CXF-4566 Project: CXF Issue Type: Bug Components: Core Affects Versions: 2.6.3 Reporter: Aki Yoshida Assignee: Aki Yoshida Fix For: 2.5.7, 2.6.4, 2.7.1 When replacing a namespace with another namespace, if some elements belonging to that namespace must retain that namespace, the transformation will result with the undeclared namespace for those elements. http://cxf.547215.n5.nabble.com/StaxTransformFeature-outTransformElements-problem-tc5716579.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4581) cxf-codegen-plugin tries to generate code during configuration build
Josh Beitelspacher created CXF-4581: --- Summary: cxf-codegen-plugin tries to generate code during configuration build Key: CXF-4581 URL: https://issues.apache.org/jira/browse/CXF-4581 Project: CXF Issue Type: Bug Components: Tooling Reporter: Josh Beitelspacher In order to configure the workspace, m2e runs a configuration build prior to any actual builds. During this configuration builds plugins should only setup their additional source and resources directories and should not attempt to read or write any files in the workspace. In many cases it is not a problem that code generation runs too soon, but if any input files to the code generation process are not available then the code generation will fail, the target/generated-sources/cxf directory will not be created, and the generated-sources directory won't be added to Eclipse classpath. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4579) Exchange's out message is not set for recovered outbound WS-RM messages
[ https://issues.apache.org/jira/browse/CXF-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida resolved CXF-4579. -- Resolution: Fixed Fix Version/s: 2.7.1 2.6.4 2.5.7 Exchange's out message is not set for recovered outbound WS-RM messages Key: CXF-4579 URL: https://issues.apache.org/jira/browse/CXF-4579 Project: CXF Issue Type: Bug Components: WS-* Components Affects Versions: 2.6.3 Reporter: Aki Yoshida Assignee: Aki Yoshida Priority: Minor Fix For: 2.5.7, 2.6.4, 2.7.1 When recovering outbound WS-RM messages from the storage for retransmission, the associated exchange object's outbound message is not set. This may result in NPE in some scenarios. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
