 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | JSP - A mailing list about Java Server Pages specification and reference | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
| | | C++ - Java communication | C++ - Java communication 2004-03-31 - By BOWMAN, James
Back
Corba is the solution to the problem. RMI will work either over JRMP or
over IIOP. Corba support is inbuilt into J2EE to solve the interoperability
problem.
-- --Original Message-- --
From: Deb, Abhijit [mailto:Adeb@(protected)]
Sent: 31 March 2004 16:39
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: [J2EEPAT-INT] C++ - Java communication
Hi Guys,
Hi have the same problem. And I would like to use the some of the solutions
that you have suggested.
However, I have a requirement of XA compliant transactions between C++ and
Java and vice versa. In that case I guess CORBA will be the best option.
CORBA supports XA. Am I wrong?
J2EE has given scant look into the interoperability problem. They should
look into issues like this in more details and provide a quick and easy
standard for accomplishing interoperability - especially with transaction,
security etc. When is web service going to support transactions and when are
going to have soap toolkit that supports transaction?
Thanks for any suggestion.
-Abhijit
-- --Original Message-- --
From: An interest list for Sun Java Center J2EE Pattern Catalog
[mailto:J2EEPATTE.RNS-INTEREST@(protected)] On Behalf Of Prabhakar Goel
Sent: Tuesday, March 02, 2004 11:08 PM
To: J2EEPATTERNS-INTEREST@(protected)
Subject: Re: C++ - Java communication
CORBA provides you with a solution but the requirements may not be fulfilled
in entirety.
The requirements which you might have to sacrifice or adjust are: -
* Reliability - It mainly depends on the ORB reliability. Be very carefull
while making your choice. Good commercial ORB from Borland, Oracle etc are
again not FREE.
* Performance - The communication is a bit slow when a ORB is involved. You
have to see for the ORB performance benchmarks before making the choice.
XML based RPC provides another alternate solution. But again it may require
a bit of development effort to be put into.
Use of MQ's is another option, and you can look around for JBoss etc for
cheap and good alternatives.
Thanks & Regards,
Prabhakar Goel
Quoting Aaron Tubman <aharon@(protected)>:
> > Hi,
> >
> >
> >
> > Our system has two code-bases C++ and Java.
> >
> > We search for transport layer between C++ and Java that satisfy the
> > following requirements:
> >
> > 1. Support synchronous and a-synchronous message passing
> > 2. Easy development
> > 3. point-to-point and publish-subscribe(optional)
> > 4. Reliability
> > 5. Low cost
> > 6. Performance
> > 7. Standard
> >
> >
> >
> > We have checked two approaches:
> >
> >
> >
> > 1. JMS - no C++ support
> > 2. Tibco that is too expensive for our case.
> > 3. Web services require a lot of development
> >
> >
> >
> > Somebody knows other approaches?
> >
> >
> >
> > Thanks
> >
> >
> >
> > Aaron Tubman
> >
> >
> >
> >
> >
> >
> > ====================================================================
> > Companion Site: http://www.corej2eepatterns.com
> > J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> > List Archive:
> > http://archives.java.sun.com/archives/j2eepatterns-interest.html
> > Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> > listserv@(protected)
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
listserv@(protected)
===================
This email/fax message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution of this email/fax is prohibited. If
you are not the intended recipient, please contact the sender by email/fax
and destroy all paper and electronic copies of the original message.
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
listserv@(protected)
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.644 / Virus Database: 412 - Release Date: 26/03/2004
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail in
error, please notify the sender immediately and destroy it. As its integrity
cannot be secured on the Internet, the Atos Origin group liability cannot be
triggered for the message content. Although the sender endeavours to maintain
a computer virus-free network, the sender does not warrant that this
transmission is virus-free and will not be liable for any damages resulting
from any virus transmitted.
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
