cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ext2 (JIRA)" <>
Subject [jira] [Commented] (CXF-3505) CXF attachment doesn't compatible with SUN's ACTIVATION library
Date Tue, 10 May 2011 05:03:03 GMT


ext2 commented on CXF-3505:

the problem is somewhat releate the javax.acivation.DataHandler's implement; check the difference
of two activation library:

Geronimo's :
    public DataHandler(DataSource ds) {
        this.ds = ds;
        this.flavor = new ActivationDataFlavor(ds.getContentType(), null);
	// getContentType() of CXF's LazyDataSource will en-force it to be loaded; then:  attachments(not
last one) will cached, and the last attachment still keep delegate to network stream;

    public DataHandler(DataSource ds) {
	// save a reference to the incoming DS
	dataSource = ds;
	oldFactory = factory; // keep track of the factory
	//doesn't call any method of LazyDataSource, so it cannot enforce the CXF's LazyDataSource
to Load; so the attachments are not cached; Then 2 problem will occurs: 1) cannot release
http-connection 2)if user-application doesn't consume the inputstream, just close it. A temporary
file will be left on disk and keep open;

> CXF attachment doesn't compatible with SUN's  ACTIVATION library
> ----------------------------------------------------------------
>                 Key: CXF-3505
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>            Reporter: ext2
>         Attachments:
> if using sun's javax.activation api (version 1.1) instead of geronimo's activation api.
CXF's attachments . the http connection cannot be released corrrectly;

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message