axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (AXIS-1358) attachments.implementation configuration option broken
Date Tue, 11 May 2004 21:06:56 GMT
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Tue, 11 May 2004 2:05 PM
       Body:
Agreed that this should be fixed. Can you please send in a patch? ("cvs diff -u" against latest
cvs). I'd be happy to review any changes to existing implementation as well that would make
it more flexible the way you want it.

thanks,
dims
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1358?page=comments#action_35498

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1358

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1358
    Summary: attachments.implementation configuration option broken
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             1.1
             1.2 Beta

   Assignee: 
   Reporter: Uli Bubenheimer

    Created: Tue, 11 May 2004 1:20 PM
    Updated: Tue, 11 May 2004 2:05 PM

Description:
attachments.implementation is a global configuration option for specifying the class to implement
attachment support. It is documented in the Axis Reference Guide.

The problem is that setting the option has no effect due to a bug in org.apache.axis.Message.
The setup() method contains a call isAttachmentSupportEnabled(getMessageContext()), but at
this point the message context has not been initialized yet. Consequently, isAttachmentSupportEnabled()
always uses the default attachments implementation class.

The effect is that I cannot replace the (somewhat inflexible) default attachments implementation
with my own.

Because it is a documented option, this problem should be fixed in the 1.2 release.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message