[xsd-users] general enquiry

Tibor Guba Tibor.Guba at igate.com
Fri Nov 29 08:44:22 EST 2013


Hi,

I'm evaluating xsd on behalf of my employer, what we are looking for is an implementation of ebms/as4 light client profile, which is a collection of free standards for b2b messaging. I'm looking into several products to help us implement the transport layer for our application specific messages. For this end I am trying to implement an object model to compose messages, the model is based on public xml schemas such as soap1.1, soap 1.2, and oasis's ebXML messaging, each publicly available standard .xsd-s.
As you may be familiar with these standards, they employ wildcards, which I am having problem with, and in need of help, explanation, as what is supported in xsd.exe. I read through several mails in the archive, along with the available documentation. Tried several suggested solution like the -generate-wildcard switch, and customizing the soap Header for instance. I still find it difficult to produce the required xml format messages.
Ideally I am looking for a solution where I can add my ebms:Messaging object hierarchy to soap:Header using the any() member or adding a custom messaging() member to my soap Header class without extensive use of xerces-c API, and then serialise the whole message for sending via HTTP. Is this even possible/supported? I am building my message from scratch so no parsed dom is available, even if I'd use keep_dom option.

Thanks,
Tibor

Tibor Guba
Technical Specialist

[iGATE Logo for Email signature]
..........................................................................................................................................................
Office Tel: +353 16722 800  | Guba.Tibor at igate.com<mailto:Guba.Tibor at igate.com> | www.igate.com<http://www.igate.com/>



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Information contained and transmitted by this e-mail is confidential and proprietary to iGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailadmin at igate.com <mailto:mailadmin at igate.com>. iGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of iGATE. iGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While iGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about iGATE please visit www.igate.com <http://www.igate.com>.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6335 bytes
Desc: image001.jpg
Url : http://codesynthesis.com/pipermail/xsd-users/attachments/20131129/b088206d/image001.jpg


More information about the xsd-users mailing list