Axis2
  1. Axis2
  2. AXIS2-941

MMS transport support for Apache Axis2

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: transports
    • Labels:
      None

      Description

      Developed MMS transport for Axis2.

      This is part of my project for Google Summer of Code 2006 , first part was to build a MMS transport for Apache Mirae and after I finished that , I made the MMS transport functionality for Apache Axis2. More information about my project can be seen here , http://wiki.apache.org/general/AnjanaFernando/GSoC2006Work#axis2mms .

      Patch coming up ..

      1. axis2mms.patch
        130 kB
        Anjana Fernando

        Activity

        Anjana Fernando created issue -
        Hide
        Anjana Fernando added a comment -

        Please find the description of this patch here , http://wiki.apache.org/general/AnjanaFernando/GSoC2006Work#axis2mms.

        Show
        Anjana Fernando added a comment - Please find the description of this patch here , http://wiki.apache.org/general/AnjanaFernando/GSoC2006Work#axis2mms .
        Anjana Fernando made changes -
        Field Original Value New Value
        Attachment axis2mms.patch [ 12337753 ]
        Hide
        Deepal Jayasinghe added a comment -

        Hi All;
        Shall we apply this path?
        Then we have one more transport.

        Show
        Deepal Jayasinghe added a comment - Hi All; Shall we apply this path? Then we have one more transport.
        Hide
        Thilina Gunarathne added a comment -

        Anjana,
        Wow.. Interesting... Is this compatible with MM7 specification..
        We recently added MM7 attachments serialzation ability in to Axis2...
        Curious to know whether you support sending attachments in this implementation... If not we would be able to make it work using our recent addition...
        It would be great if you can provide a high level overview of how this works..

        Thanks,
        Thilina

        Show
        Thilina Gunarathne added a comment - Anjana, Wow.. Interesting... Is this compatible with MM7 specification.. We recently added MM7 attachments serialzation ability in to Axis2... Curious to know whether you support sending attachments in this implementation... If not we would be able to make it work using our recent addition... It would be great if you can provide a high level overview of how this works.. Thanks, Thilina
        Hide
        Anjana Fernando added a comment -

        Hello everyone,

        No it doesn't support the MM7 specification, it only supports encoding/decoding using the MM1 standard.

        For the transport to be actually functional, the user should provide classes that implements the " MessageInput ", " MessageOutput " and " MessageNotifier " interfaces.

        The " MessageInput " should get the MMS message that's coming in Axis 2's way and pass it on, and there after the rest will decode the message and pass it to the Axis2 Engine. The " MessageOutput " will get a encoded MMS message that's coming from the Axis2 Engine and it's job is it send the MMS message data to the destination. Then the " MessageNotifier " class should get the MMS notification message with a specific " Application ID ", and get the url that points to the actual MMS message, this url will be passed to the " MessageInput ". These implementations are left to the user because , first , I couldn't use any 3'rd party WAP libraries because they are not Apache licensed code, and also by doing this, the user is free to use the method they like to use to send/receive messages either through a GSM modem or by using a WAP gateway through the internet.

        Hope the information helped.

        Regards,
        Anjana.

        Show
        Anjana Fernando added a comment - Hello everyone, No it doesn't support the MM7 specification, it only supports encoding/decoding using the MM1 standard. For the transport to be actually functional, the user should provide classes that implements the " MessageInput ", " MessageOutput " and " MessageNotifier " interfaces. The " MessageInput " should get the MMS message that's coming in Axis 2's way and pass it on, and there after the rest will decode the message and pass it to the Axis2 Engine. The " MessageOutput " will get a encoded MMS message that's coming from the Axis2 Engine and it's job is it send the MMS message data to the destination. Then the " MessageNotifier " class should get the MMS notification message with a specific " Application ID ", and get the url that points to the actual MMS message, this url will be passed to the " MessageInput ". These implementations are left to the user because , first , I couldn't use any 3'rd party WAP libraries because they are not Apache licensed code, and also by doing this, the user is free to use the method they like to use to send/receive messages either through a GSM modem or by using a WAP gateway through the internet. Hope the information helped. Regards, Anjana.
        Davanum Srinivas made changes -
        Assignee Deepal Jayasinghe [ deepal ]
        Hide
        Davanum Srinivas added a comment -

        Thilina,

        Is this code already checked in?

        thanks,
        dims

        Show
        Davanum Srinivas added a comment - Thilina, Is this code already checked in? thanks, dims
        Davanum Srinivas made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Won't Fix [ 2 ]
        Hide
        Davanum Srinivas added a comment -

        Anjana, Thanks. looks like no one is picking this up.

        – dims

        Show
        Davanum Srinivas added a comment - Anjana, Thanks. looks like no one is picking this up. – dims
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        582d 22h 29m 1 Davanum Srinivas 03/Mar/08 17:45

          People

          • Assignee:
            Deepal Jayasinghe
            Reporter:
            Anjana Fernando
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development