[jira] [Commented] (CXF-3505) CXF attachment doesn't compatible with SUN's ACTIVATION library

2011-05-09 Thread ext2 (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031018#comment-13031018 ] ext2 commented on CXF-3505: --- the problem is somewhat releate the javax.acivation.DataHandler's imp

[jira] [Commented] (CXF-3505) CXF attachment doesn't compatible with SUN's ACTIVATION library

2011-05-09 Thread ext2 (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031015#comment-13031015 ] ext2 commented on CXF-3505: --- 1)attachment is a POM project for testing this problem; the test app

[jira] [Updated] (CXF-3505) CXF attachment doesn't compatible with SUN's ACTIVATION library

2011-05-09 Thread ext2 (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ext2 updated CXF-3505: -- Attachment: attachment-clean.zip > CXF attachment doesn't compatible with SUN's ACTIVATION library > ---

[jira] [Created] (CXF-3505) CXF attachment doesn't compatible with SUN's ACTIVATION library

2011-05-09 Thread ext2 (JIRA)
CXF attachment doesn't compatible with SUN's ACTIVATION library Key: CXF-3505 URL: https://issues.apache.org/jira/browse/CXF-3505 Project: CXF Issue Type: Bug Repo

[jira] [Updated] (CXF-3504) for big attachment, a temporary file is left on disk and keep opend, if the application just close the DataSource's inputStream and doesn't consume it;

2011-05-09 Thread ext2 (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ext2 updated CXF-3504: -- Attachment: attachment-clean.zip this is the test case's pom project. > for big attachment, a temporary file is left on

[jira] [Updated] (CXF-3504) for big attachment, a temporary file is left on disk and keep opend, if the application just close the DataSource's inputStream and doesn't consume it;

2011-05-09 Thread ext2 (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ext2 updated CXF-3504: -- Attachment: mtom.wsdl > for big attachment, a temporary file is left on disk and keep opend, if the > application just c

[jira] [Created] (CXF-3504) for big attachment, a temporary file is left on disk and keep opend, if the application just close the DataSource's inputStream and doesn't consume it;

2011-05-09 Thread ext2 (JIRA)
for big attachment, a temporary file is left on disk and keep opend, if the application just close the DataSource's inputStream and doesn't consume it; -

Re: CXF-2.4.0 possible bug in HTTP and Local Transport Configs incompatible

2011-05-09 Thread cogitate
thanks Willem however the problem is still unsolved in cxf-2.4.0 it seems i can't have both local protocol and http protocol within the same spring context file. as the example above shows if i have the following configured and i try to call an endpoint configured with local protocol

[jira] [Commented] (CXF-3472) Cannot override HTTPConduit's handleResponse() method

2011-05-09 Thread Willem Jiang (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030655#comment-13030655 ] Willem Jiang commented on CXF-3472: --- Hi David, I just checked the HttpConduit code in the

Issues with Attachments: week of 2011-05-09

2011-05-09 Thread dkulp
CXF - Monday, May 9, 2011 5 Issues with Attachments (sorted oldest to newest) [CXF-3219] WS-RMs' DestinationSequence does not update the ack range in the RMStore - Created: 2010-12-25 - Updated: 2011-04-29 - Type: Bug - Fix Versions: [] - Reporter: Aki

[jira] [Resolved] (CXF-3502) IllegalArgumentException: wrong number of arguments with Dispatch/Provider service

2011-05-09 Thread jimma (JIRA)
[ https://issues.apache.org/jira/browse/CXF-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jimma resolved CXF-3502. Resolution: Fixed > IllegalArgumentException: wrong number of arguments with Dispatch/Provider > service > -

Re: CXF-2.4.0 possible bug in HTTP and Local Transport Configs incompatible

2011-05-09 Thread Willem.Jiang
Hi, In CXF 2.4.0, we don't use spring to load the extensions by default. If you want to replace the components with a customer configuration, you have to include this line Willem -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-2-4-0-possible-bug-in-HTTP-and-Local-Transp