> This could be used for XML in general, right? Not only SOAP, I mean.
yeah we can say that. But the code is really old and does not fit any standard
specs.
(no SAX or DOM parsing)
Also it's really buggy.
See the ML for some patch i've posted.
Here is one of my last mails on this (07/02/2007 15:22)
Vincent CHAVANIS a écrit :
> After a long proccess of investigation, i finaly found that this SMSC
> have some serious issues
> - XML specs files are really bad interpreted (fields are read with char
> * and then converted into octstr)
> - Lots of segfaults
> - SMSC driver cannot support multi SMSC (with the same driver, (**server
> not used))
> - XML parsing is really old school.
>
> I'm in favor to remove this file from the current directory, or move it
> into /contrib or /dev
Alejandro Guerrieri a écrit :
Ok, I think I've got it, thanks!
This could be used for XML in general, right? Not only SOAP, I mean.
Regards,
--
Alejandro Guerrieri
[email protected]
On 05/02/2009, at 17:05, Vincent CHAVANIS wrote:
Hi Alejandro,
I spent a lot of time to understand how this works.
this seems to work like this:
- .xml file is (if i remember well) the XML format of your
content you will answer generally successResponse
- .spec are the logical path to grab the infos
from the XML you receive with this structure:
field[space]path.
for SMAP uses, i made these files:
#) cat DLR.xml
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.w3.org/2003/05/soap-envelope
http://www.w3.org/2003/05/soap-envelope";>
<soap:Header>
<MMAP:MMAPHeader soap:mustUnderstand="1"
xmlns:MMAP="http://www.smsforum.net/schemas/mmap/v1.0";
xsi:schemaLocation="http://www.smsforum.net/schemas/mmap/v1.0
http://www.smsforum.net/schemas/mmap/v1.0/mmap.xsd";>
<MMAP:ApplicationContext bodyType="SuccessResponse"/>
</MMAP:MMAPHeader>
</soap:Header>
<soap:Body>
<soap:SuccessResponse
xmlns:smap="http://www.smsforum.net/schemas/smap/v1.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.smsforum.net/schemas/smap/v1.00
http://www.smsforum.net/schemas/smap/v1.0/MessageTransfer.xsd"/>
</soap:Body>
</soap:Envelope>
#) cat DLR.spec
from Envelope/Body/DeliverRequest/DeliveryInfo/Source/Number
receiver Envelope/Body/DeliverRequest/DeliveryInfo/Destination/Number
id Envelope/Body/DeliverRequest/DeliveryInfo/MessageInfo/MessageRef
result
Envelope/Body/DeliverRequest/DeliveryInfo/MessageInfo/NetworkErrorCode
value
msgstate
Envelope/Body/DeliverRequest/DeliveryInfo/MessageInfo/MessageState value
Hope it will help you.
Vincent.
Alejandro Guerrieri a écrit :
Hi,
I've been looking into smsc_soap.c code and found it quite
interesting. I've made a couple of quick fixes to make it build into
the source tree and so far it compiles. The functionality is
different from what the code comments says, but I've figured out most
of it.
However, I don't know how to build the .xml and .spec files required
to make it work.
If someone has an example or know about those files' syntax and wants
to save me the reverse-guessing from the code, it's more than welcome ;)
Regards,
--
Alejandro Guerrieri
[email protected]
--
Telemaque - 06560 SOPHIA-ANTIPOLIS - (FR)
Service Technique/Reseau - NOC
Direction du Developpement xMS+
http://www.telemaque.fr/
[email protected]
Tel : +33 4 92 90 99 84 (fax 9142)
--
Telemaque - 06560 SOPHIA-ANTIPOLIS - (FR)
Service Technique/Reseau - NOC
Direction du Developpement xMS+
http://www.telemaque.fr/
[email protected]
Tel : +33 4 92 90 99 84 (fax 9142)
