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.