Win a copy of Secure Financial Transactions with Ansible, Terraform, and OpenSCAP this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

What The Legacy Connectivity Pointing to???

Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Friends As per the Objective Legacy Connectivity of SCEA What Actually it is Pointing I confused a bit.
My Doubt is given below...
If a J2EE Application wants to communicate with Legacy System then It has to use CORBA or Low level Socket Interface .
But if we talk about normal java application then it can follow JNI technique.
What exactly the Legacy Connectivity Objective is pointing from the Above Two?
Ranch Hand
Posts: 56
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I assume that you are talking from the point of view of the exam. I'd say that Sun doesn't really specify if Legacy Connectivity includes JNI or not and no-one on this list knows all of the questions that you are likely to be asked.
IMHO JNI would be the last thing that I would turn to in order to connect to Legacy systems and I'll be even more contentious by saying that if you use JNI then where possible it should be as a stop-gap measure.
Probably the way to approach Legacy Connectivity is to split it into two. On one hand you have Legacy API's that Java has built in support for and on the other you have Legacy API's, systems and protocols that Java doesn't have built in support for. Examples of the former are JavaIDL and JDBC (including the JDBC-ODBC bridge) and you can include others such as JMS which supports connectivity to existing messaging systems. For the latter, you have things like Screen Scrapers, Objects mappers, protocol bridges and middleware products that support Java on one side and a Legacy API on the other. You can also write your own Java code that connects to legacy applictions/systems where there is no off the shelf product available. You may do this using sockets to a networked application or you may do this using JNI to a local application that doesn't have network connectivity and these are just two examples from many.
The fact is that there are an infinite number of legacy connectivity scenarios, many of which have already been addressed, but also many of which have not (or have been in one or two places but have never been documented). It's the job of the architect to be aware of what is available in terms of tools and to use those tools appropriately.
Hope this helps
I don't get it. A whale wearing overalls? How does that even work? It's like a tiny ad wearing overalls.
SKIP - a book about connecting industrious people with elderly land owners
    Bookmark Topic Watch Topic
  • New Topic