• 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 ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Communicating with Glassfish v2 from v3

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi everybody.
First of all, thanks for all the clever pieces of information I usually find here. Best help I can get.

Here's my problem:
We have a legacy application that's running in GlassFish v2.0. No, we won't migrate it to v3. Political issues.
My only option, theorically speaking, to connect to it is by invoking JMS Queues or EJB3s from outside.

Now for the crunchy part.
My duty is to develop an OSGi app running in GlassFish v3.1.1 that is to connect to the legacy app to fetch some old-fashioned data.

I've been sweating blood and tears, so to speak, to make these too exchange even a single (binary) word through JMS, until I found out that one simply cannot use JMS between GlassFish v2 and v3. Something to do with two incompatible Serial Context objects. And still, I have to figure out a way to build a bridge between the two. Don't ask, I don't know, I'm just paid for it.

So my question is: Does any of you have an idea? Any suggestion? A clue? How can I invoke a functionality of the legacy app from within my OSGi devs? I'm out of idea right now.

In a word: HELP!
 
Bartender
Posts: 1381
39
IBM DB2 Netbeans IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well,

as a simple idea - but I can't swear it may work - you may try to develop some 'bridge-endpoint' on GlassFish 2 which actual connects to the 'legacy' apps on it, and then try to interface that bridge from outside... at least, if you may develop again something on the old appserver. You can try to serialize all your payload in a Base64 string and exchange it between the two endpoints. A Base64 string should be fairly portable
 
Athanase Percevalve
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Good Morning Claude.

Thank you for the suggestion, which meets my own conclusions. Yes, a web service endpoint seems to be the only solution here. I am actually pretty free to add up to the legacy platform as long as it doesn't modify the running application. A web service is not as sexy as I would like the solution to be , but...

Again, thanks!
Athanase
 
Claude Moore
Bartender
Posts: 1381
39
IBM DB2 Netbeans IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm glad to have you helped !
Good luck for your work and regards !
 
Politics is a circus designed to distract you from what is really going on. So is this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic