[jira] [Commented] (CXF-4836) ServiceImpl getPort does not need to throw Exception if the portName can not be found in portInfos

[ https://issues.apache.org/jira/browse/CXF-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599753#comment-13599753 ] Yan Min Sheng commented on CXF-4836: The JSR 224 spec has the following statement: 4.1

[jira] [Commented] (CXF-4836) ServiceImpl getPort does not need to throw Exception if the portName can not be found in portInfos

[ https://issues.apache.org/jira/browse/CXF-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598559#comment-13598559 ] Yan Min Sheng commented on CXF-4836: Can anybody take a look at it? Thanks.

[jira] [Updated] (CXF-4877) CXF will throw javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Can't find prefix if the SEI has Action annotation

[ https://issues.apache.org/jira/browse/CXF-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4877: --- Component/s: (was: Core) Integration Estimated Complexity: No

[jira] [Updated] (CXF-4877) CXF will throw javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Can't find prefix if the SEI has Action annotation

[ https://issues.apache.org/jira/browse/CXF-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4877: --- Attachment: CXF-4877.patch I created a patch to fix it. Basically I add code to add the prefix plus nam

[jira] [Created] (CXF-4877) CXF will throw javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Can't find prefix if the SEI has Action annotation

Yan Min Sheng created CXF-4877: -- Summary: CXF will throw javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Can't find prefix if the SEI has Action annotation Key: CXF-4877 URL: https://issues.apache.org

[jira] [Closed] (CXF-4869) CXF will throw exception if impl class and interface targetNameSpace is different

[ https://issues.apache.org/jira/browse/CXF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng closed CXF-4869. -- Resolution: Not A Problem I've found and fixed the issue. This is because my customized settings.

[jira] [Commented] (CXF-4869) CXF will throw exception if impl class and interface targetNameSpace is different

[ https://issues.apache.org/jira/browse/CXF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592014#comment-13592014 ] Yan Min Sheng commented on CXF-4869: The spec JSR 224 has the following statements: The

[jira] [Commented] (CXF-4869) CXF will throw exception if impl class and interface targetNameSpace is different

[ https://issues.apache.org/jira/browse/CXF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592013#comment-13592013 ] Yan Min Sheng commented on CXF-4869: If I put the following interface into the CXF which

[jira] [Updated] (CXF-4869) CXF will throw exception if impl class and interface targetNameSpace is different

[ https://issues.apache.org/jira/browse/CXF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4869: --- Component/s: Core > CXF will throw exception if impl class and interface targetNameSpace is > diff

[jira] [Updated] (CXF-4869) CXF will throw exception if impl class and interface targetNameSpace is different

[ https://issues.apache.org/jira/browse/CXF-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4869: --- Summary: CXF will throw exception if impl class and interface targetNameSpace is different (was: CXF w

[jira] [Created] (CXF-4869) CXF will throw exception if impl clall and interface targetNameSpace is different

Yan Min Sheng created CXF-4869: -- Summary: CXF will throw exception if impl clall and interface targetNameSpace is different Key: CXF-4869 URL: https://issues.apache.org/jira/browse/CXF-4869 Project: CXF

[jira] [Commented] (CXF-4836) ServiceImpl getPort does not need to throw Exception if the portName can not be found in portInfos

[ https://issues.apache.org/jira/browse/CXF-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585689#comment-13585689 ] Yan Min Sheng commented on CXF-4836: What I removed is : public T getPort(QName por

[jira] [Updated] (CXF-4836) ServiceImpl getPort does not need to throw Exception if the portName can not be found in portInfos

[ https://issues.apache.org/jira/browse/CXF-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4836: --- Description: We create such client which will set target address info and binding info in RequestConte

[jira] [Updated] (CXF-4836) ServiceImpl getPort does not need to throw Exception if the portName can not be found in portInfos

[ https://issues.apache.org/jira/browse/CXF-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4836: --- Description: We create such client which will set target address info and binding info in RequestConte

[jira] [Created] (CXF-4836) ServiceImpl getPort does not need to throw Exception if the portName can not be found in portInfos

Yan Min Sheng created CXF-4836: -- Summary: ServiceImpl getPort does not need to throw Exception if the portName can not be found in portInfos Key: CXF-4836 URL: https://issues.apache.org/jira/browse/CXF-4836

[jira] [Comment Edited] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560392#comment-13560392 ] Yan Min Sheng edited comment on CXF-4772 at 1/23/13 6:01 AM: - Hi

[jira] [Comment Edited] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559614#comment-13559614 ] Yan Min Sheng edited comment on CXF-4772 at 1/23/13 4:51 AM: - We

[jira] [Commented] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560392#comment-13560392 ] Yan Min Sheng commented on CXF-4772: Hi, Freeman, I get your point. Delegate attachment

[jira] [Comment Edited] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560392#comment-13560392 ] Yan Min Sheng edited comment on CXF-4772 at 1/23/13 4:49 AM: - Hi

[jira] [Commented] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559618#comment-13559618 ] Yan Min Sheng commented on CXF-4772: As the blog states, the DelegatingInputStream/Cache

[jira] [Commented] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559614#comment-13559614 ] Yan Min Sheng commented on CXF-4772: Well, the problem here is after call DataHandler.wr

[jira] [Updated] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4772: --- Attachment: (was: AttachmentDeserializer.java) > AssessmentDataStore do not cache the last atta

[jira] [Updated] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4772: --- Attachment: CXF4772.patch add the patch file > AssessmentDataStore do not cache the la

[jira] [Commented] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559485#comment-13559485 ] Yan Min Sheng commented on CXF-4772: I will create a patch and link it later.

[jira] [Updated] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

[ https://issues.apache.org/jira/browse/CXF-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yan Min Sheng updated CXF-4772: --- Attachment: AttachmentDeserializer.java The suggestion fix is to cache the newly created attachement af

[jira] [Created] (CXF-4772) AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time

Yan Min Sheng created CXF-4772: -- Summary: AssessmentDataStore do not cache the last attachment binary stream, so the DataHandler.writeTo() will fail if it is called for the second time Key: CXF-4772 URL: https://iss