You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ji...@apache.org on 2004/04/06 17:33:43 UTC

[jira] Created: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Tue, 6 Apr 2004 8:33 AM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


[jira] Commented: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Tue, 6 Apr 2004 9:38 AM
       Body:
Can you please submit a patch that treats 'application/octetstream' the same as 'application/octet-stream' to correct this problem?
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1289?page=comments#action_27978

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Tue, 6 Apr 2004 9:38 AM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


[jira] Commented: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Tue, 6 Apr 2004 3:43 PM
       Body:
Lisa,

Looks like the simple patch is not enough :( Getting test failures. Can you try running "ant clean
all-tests" from ws-axis/java directory? you will see the problem(s).

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

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Tue, 6 Apr 2004 3:43 PM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


[jira] Commented: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Lisa Preston
    Created: Thu, 8 Apr 2004 7:20 AM
       Body:

Looks like your changes work fine!  Thanks!
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1289?page=comments#action_28036

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Thu, 8 Apr 2004 7:20 AM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


[jira] Closed: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
Message:

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Thu, 8 Apr 2004 5:57 AM

Lisa,

do you have a WSDL that i can test with? i have some changes in my sandbox that will help.

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Thu, 8 Apr 2004 5:57 AM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


[jira] Commented: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Tue, 6 Apr 2004 6:33 PM
       Body:
    [java]      [echo] Compiling test.wsdl.attachments
    [java] [wsdl2java] WSDL2Java C:\APACHE\ws-axis\java/test/wsdl/attachments/mime.wsdl
    [java]   [foreach] - soap:body in Binding test.wsdl.attachments.B1 / Operation outputPlainText has an empty namespace
    [java]   [foreach] - soap:body in Binding test.wsdl.attachments.B1 / Operation outputMimeMultipart has an empty namespace
    [java]   [foreach] - soap:body in Binding test.wsdl.attachments.B1 / Operation outputPlainText has an empty namespace
    [java]   [foreach] - soap:body in Binding test.wsdl.attachments.B1 / Operation outputMimeMultipart has an empty namespace
    [java]      [copy] Copying 2 files to C:\APACHE\ws-axis\java\build\work\test\wsdl\attachments
    [java]     [javac] Compiling 7 source files to C:\APACHE\ws-axis\java\build\classes
    [java]   [foreach] C:\APACHE\ws-axis\java\build\work\test\wsdl\attachments\AttachmentTestCase.java:199: echoAttachment(javax.activation.DataHandler) in test.wsdl.attachments.
    [java]   [foreach]         output = binding.echoAttachment(input);
    [java]   [foreach]                         ^
    [java]   [foreach] C:\APACHE\ws-axis\java\build\work\test\wsdl\attachments\B1Impl.java:14: test.wsdl.attachments.B1Impl is not abstract and does not override abstract method
    [java]   [foreach] public class B1Impl implements test.wsdl.attachments.Pt1 {
    [java]   [foreach]        ^
    [java]   [foreach] C:\APACHE\ws-axis\java\build\work\test\wsdl\attachments\B1Stub.java:470: incompatible types
    [java]   [foreach] found   : org.apache.axis.attachments.OctetStream
    [java]   [foreach] required: javax.activation.DataHandler
    [java]   [foreach]                 return (org.apache.axis.attachments.OctetStream) _resp;
    [java]   [foreach]                        ^
    [java]   [foreach] C:\APACHE\ws-axis\java\build\work\test\wsdl\attachments\B1Stub.java:472: incompatible types
    [java]   [foreach] found   : org.apache.axis.attachments.OctetStream
    [java]   [foreach] required: javax.activation.DataHandler
    [java]   [foreach]                 return (org.apache.axis.attachments.OctetStream) org.apache.axis.utils.JavaUtils.convert(_resp, byte[].class);
    [java]   [foreach]                        ^
    [java]   [foreach] 4 errors
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1289?page=comments#action_27990

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Tue, 6 Apr 2004 6:33 PM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


[jira] Commented: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Thu, 8 Apr 2004 6:12 AM
       Body:
You can try the latest cvs. it has the fixes from me. 
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1289?page=comments#action_28028

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Thu, 8 Apr 2004 6:12 AM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


Re: [jira] Updated: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by Davanum Srinivas <di...@yahoo.com>.
Lisa,

Looks like the simple patch is not enough :( Getting test failures. Can you try running "ant clean
all-tests" from ws-axis/java directory? you will see the problem(s).

thanks,
dims

--- jira@apache.org wrote:
> The following issue has been updated:
> 
>     Updater: Lisa Preston (mailto:lisa.preston@jhuapl.edu)
>        Date: Tue, 6 Apr 2004 2:31 PM
>     Comment:
> Re-submit of patch (one change missing in last file)
>     Changes:
>              Attachment changed to diff.txt
>     ---------------------------------------------------------------------
> For a full history of the issue, see:
> 
>   http://issues.apache.org/jira/browse/AXIS-1289?page=history
> 
> ---------------------------------------------------------------------
> View the issue:
>   http://issues.apache.org/jira/browse/AXIS-1289
> 
> Here is an overview of the issue:
> ---------------------------------------------------------------------
>         Key: AXIS-1289
>     Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
>        Type: Bug
> 
>      Status: Unassigned
>    Priority: Major
> 
>     Project: Axis
>  Components: 
>              WSDL processing
>    Versions:
>              current (nightly)
> 
>    Assignee: 
>    Reporter: Lisa Preston
> 
>     Created: Tue, 6 Apr 2004 8:33 AM
>     Updated: Tue, 6 Apr 2004 2:31 PM
> Environment: Java 1.4.1_03
> Axis 1.2
> 
> Description:
> In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream'
> (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a
> result, the representation selected by WSDL2Java for the resultant source code is DataHandler
> (generic) instead of OctetStream when the proper content type is used.
> 
> All references to 'application/octetstream' should either be corrected, or should be a backwards
> compatibility option with 'application/octet-stream' as the preferred string. It would probably
> be a good idea to disallow further use of 'application/octetstream' by removing it completely.
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 


=====
Davanum Srinivas - http://webservices.apache.org/~dims/

[jira] Updated: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Lisa Preston (mailto:lisa.preston@jhuapl.edu)
       Date: Tue, 6 Apr 2004 2:31 PM
    Comment:
Re-submit of patch (one change missing in last file)
    Changes:
             Attachment changed to diff.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1289?page=history

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Tue, 6 Apr 2004 2:31 PM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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


[jira] Updated: (AXIS-1289) Processing of 'octet-stream' content type for MIME SOAP attachments

Posted by ji...@apache.org.
The following issue has been updated:

    Updater: Lisa Preston (mailto:lisa.preston@jhuapl.edu)
       Date: Tue, 6 Apr 2004 2:27 PM
    Comment:
Patch for using 'application/octet-stream':

* New MIME Content Type constants in Constants.java
* Replacement of hardcoded content type strings in files affected by 'octet-stream'

    Changes:
             Attachment changed to diff.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1289?page=history

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1289
    Summary: Processing of 'octet-stream' content type for MIME SOAP attachments
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Lisa Preston

    Created: Tue, 6 Apr 2004 8:33 AM
    Updated: Tue, 6 Apr 2004 2:27 PM
Environment: Java 1.4.1_03
Axis 1.2

Description:
In Axis 1.2, there seems to be an inconsistency in the use of 'application/octetstream' (incorrect) and 'application/octet-stream' for handling MIME content as defined by a WSDL.  As a result, the representation selected by WSDL2Java for the resultant source code is DataHandler (generic) instead of OctetStream when the proper content type is used.

All references to 'application/octetstream' should either be corrected, or should be a backwards compatibility option with 'application/octet-stream' as the preferred string. It would probably be a good idea to disallow further use of 'application/octetstream' by removing it completely.



---------------------------------------------------------------------
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