Lists Home |
Date Index |
- To: Antonio Jose Jimeno Yepes <firstname.lastname@example.org>
- Subject: Re: [xml-dev] Transmitting XML between different applications
- From: Mukul Gandhi <email@example.com>
- Date: Fri, 18 Feb 2005 04:57:20 -0800 (PST)
- Cc: firstname.lastname@example.org
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=NGTVrq6uNc0CALiwprxCBweOE+uqhRT7xj7hpYyxCRqlIhIvRhjZc1Rns8QNVDejZF6fuD0Y0Bmu+7hh0EtObAeWHSMcpSy41BZGO9ITlKN6es7u9vkDnVm56tmuVSNsaP+0dLRnp2tLtdFlDfLNHjFyMNuDQOkAHptpiV6HIIo= ;
- In-reply-to: <4215EC47.email@example.com>
Thanks for your suggestions.. In my application,
transmitting XML seems a necessity. There is a client
application, which will request to run a business
logic(for e.g. a EJB on a J2EE server). Had it been a
normal web application I can directly invoke the EJB
from the client, without transmitting XML. Or use
RMI/CORBA as you have suggested. But my client can be
Web browser, WAP phone, SMS request or IVR. For any
client type, the business logic component will be
same(i.e. the same EJB). There will be an adpater(a
library) for each client type, which will translate
client data(encoded in its protocol) to XML. This
request XML will be stored in a messaging store(for
reliable delivery). The XML will then be passed to the
The Business logic component will return XML as
result. A "client type" specific XSLT stylesheet will
be applied to the XML, and the result of XSLT
transformation will be sent to the client specific
adapter, which will forward the result to the client.
In this scenario, I feel XML is the right choice. And,
XSLT seems a good choice to cater to multiple client
--- Antonio Jose Jimeno Yepes
> Dear Mukul Gandhi,
> In my opinion I think that you should consider
> the requirements and constraints of your
> If you want to transmit data in a structured way
> in order to communicate two applications it
> would be a good idea using XML. You define
> your XML schema based on your needs so
> both applications "speak" the same language.
> Do not consider to send the DOM structure because
> as you said you can find those problems.
> If you want to call methods between two
> then you can consider using RMI/CORBA or
> Both of the options commented above can work
> if the systems that are sending/receiving
> the information (for instance J2EE and .NET)
> agree to work on the same communication protocols.
> What do you think?
> Best regards,
> Mukul Gandhi wrote:
> >I have a requirement to pass XML between 2
> >applications. The 2 applications are running on
> >different machines, and are Java based. The sender
> >application will generate XML to be sent, and would
> >send the XML to the receiving application.
> >I want to know the possible approaches for this.
> >The following two approaches are coming to my mind.
> >1) Create a DOM object at the sending application,
> >send this DOM object to the recieving application.
> >have some doubt with this approach.. I think, that
> >with this approach, if XML parser being used at
> >applications is same, it won't be a problem. But
> >say, if "Java XML parser" used by 2 applications is
> >different (but both conform to DOM specification),
> >will this approach work(for e.g., the sending
> >application is using Xerces, while receiving
> >application is using Oracle implementation)?
> >Lets say, if I create a DOM object at the sending
> >application using Xerces, like this -
> >Document doc= new DocumentImpl();
> >Element root = doc.createElement("person");
> >Element item = doc.createElement("name");
> >Here Document is an interface (defined in package
> >org.w3c.dom) , while DocumentImpl is a concrete
> >class(defined in package org.apache.xerces.dom).
> >And I send the "doc" object to the recieving
> >application. If the receiving application is using
> >"Oracle Java XML parser", will it be able to parse
> >recieved DOM object?
> >2) Encode XML as string at the sending application,
> >and send this XML string to the receiving
> >I want to compare the above approaches from
> >feasibility and performance point of view. I also
> >to know other approaches..
> >As a secondary requirement, I want to make the XML
> >transmission reliable(i.e. guranteed and 1 time
> >delivery). I belive, I can use messaging softwares
> >this (like WebSphere MQ and others). What are the
> >practices for reliable transmission? Should I pass
> >object, String.. etc.?
> >Later, it might be possible that 2 participating
> >applications may run on different technologies
> >J2EE and .NET). What are the possible XML
> >transmission(i.e. creation, transmission and
> >consuming) techniques in this scenario?
> >Do you Yahoo!?
> >Yahoo! Mail - Find what you need with new enhanced
> >The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an
> >initiative of OASIS <http://www.oasis-open.org>
> >The list archives are at
> >To subscribe or unsubscribe from this list use the
> The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at
> To subscribe or unsubscribe from this list use the
Do you Yahoo!?
The all-new My Yahoo! - What will yours do?