Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

J2EE - Swing comunication

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all!
I have a complex J2EE application (with EJB, Servlet, Jsp ecc.), with a Html interface (For Internet Explorer).
I would like to bring the client side to Swing. I think to use Xml-Rpc ower http for the communication.
I need to know: 1. Is this the best solution?
2. If not, what can I do? (any links, examples ecc.)

PS: I need to open .pdf and .doc files from this client.

Thanks in advance.
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Your Swing client can use the home interfaces and make remote EJB calls just like your web apps do now, can't they? If your business is in your J2EE components, they should be reusable from Swing clients.

If the Swing and EJB work is divided between two teams or developers, I'd ask the EJB team to provide Business Delegates so the Swing folk don't have to know any EJB at all. An added benefit is that if you go to some other protocol in the future you can put it behind compatible Business Delegates and not break the Swing client.
 
Veri Strora
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank You very much Stan for the reply,
but there is a problem:
The servlet use other business classes that communicate with the ejb and make other things. Those classes are fondamental for the application, and I would like to conserve their functionality (because the application work wery wery well). Any other idea?
Thanks again!
 
Stan James
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You might see if you could make new EJB session facades that access the critical business objects. In fact you might consider moving anything business-ish at all behind such facades so the web tier goes through them, too. That would take you toward an EJB back-end that could be used by any type of client.

anyClient -> sessionFacade -> businessObjects -> otherEJBs
    Bookmark Topic Watch Topic
  • New Topic