Disclaimer: These archives are mirrored from smsforum.net in 2007 before the forum got closed. Please only part of the forum is available here.
For any clarifications regarding these archives you can contact us at http://www.telecomspace.com/contact.

      TELECOMSPACE HOME PAGE         TELECOM DISCUSSION FORUM          CONTACT

+  SMS Forum Online Discussion
|-+  Protocols
| |-+  MMAP-Related (Moderator: SMS Forum Support)
| | |-+  Having SAX with SMAP
« previous next »
Pages: [1] Go Down Print
Author Topic: Having SAX with SMAP  (Read 1621 times)
Nick
Newbie
*
Offline Offline

Posts: 2



« on: November 18, 2002, 23:51:16 UTC »

Now that I've got your attention... Smiley

Has anyone here on this forum had any experience parsing and validating SMAP messages using Xerces-J and SAX? I'm beginning to feel like I'm the first person to ever do any of this stuff before. If anyone has been down this path before, would they perhaps like to share some of their experiences...

Specifically I'm trying to validate the sample SMAP message that comes with the xsd files (pushEx1.xml). Has anyone had any luck validating this file? XMLSpy doesn't seem to complain about it, but Xerces gives my a whole bunch of errors

[Error] common.xsd:4:31: sch-props-correct.2: a schema cannot contain two global components with the same name; this one contains two occurrences of 'http://www.smsforum.net/smap,Operation'.

[Error] pushEx1.xml:4:17: cvc-complex-type.2.4.a: Invalid content starting with element 'SubmitRequest'. The content must match '(("http://www.smsforum.net/smap":ApplicationContext),(("http://www.smsforum.net/smap":Request)|("http://www.smsforum.net/smap":Response)))'.

I'm hoping its something stupid that I've done.

Get hold of me offline if you wish
[email protected]
« Last Edit: November 18, 2002, 23:53:07 UTC by Nick » Logged
stephen_gryphon
Jr. Member
**
Offline Offline

Posts: 7



WWW
« Reply #1 on: March 07, 2003, 06:03:57 UTC »

We don't use Java, however we have had problems parsing the Schema's.

We use Microsoft .NET, and had trouble getting the multiple references in the XSD files to parse correctly in the xsd.exe tool (a tool which automatically generates source code for strongly typed handling of the schema).

The solution we ended up having to implement was to cut and paste the parts of the schema we wanted into a single schema document (i.e. manually build the "profile"), and then use that.

Hope this helps.
Logged
Nick
Newbie
*
Offline Offline

Posts: 2



« Reply #2 on: March 07, 2003, 06:09:32 UTC »

I never found a answer to that problem. But in order to cope with 80 transactions a second requirement, I don't think parsing with schema validation switched on would have ever been a suitable solution.

So now we don't validate against the schema. Just as long as the SMAP is well-formed and the pertinant fields are there we don't really care what they send us. All we look for is payload, sender, recipient/s, any QOS stuff and the rest is just fluff anyway.

Out of interest, what kind of development are you using SMAP for?
Logged
stephen_gryphon
Jr. Member
**
Offline Offline

Posts: 7



WWW
« Reply #3 on: March 10, 2003, 06:02:24 UTC »

We use .NET to generate a set of custom classes which give us strongly typed access to the underlying XML data. The schema is used to automatically generate the classes using a tool.

We do not use the schema at run-time, and I agree that it would be a performance drain to try and do so!

We are using SMAP aka MMAP in a .NET ESME service. The SMAP XML format is used for internal handling of messages, using Microsoft MSMQ (e.g. client software dumps messages in SMAP format into MSMQ).

The service then monitors the queue and passes the message on to the appropriate SMSC -- essentially it is an SMAP-SMPP.

(For more details, and a free trial download, check our corporate web site, http://www.startcorp.com/.)

The download includes the .NET library for handling SMAP data, with API doco.

We haven't yet updated to MMAP, but it doesn't look like too much work (change the Operation wrapper to a SOAP wrapper -- I would prefer SOAP anyway).
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length