• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

ways for swing client to connect to weblogic server behind firewall

 
Ranch Hand
Posts: 270
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Good day!

I have a 3-tier enterprise j2ee application running on weblogic. Now i have a requirement to develop a thin swing client that shall desirably connect to the business layer (EJBs) directly.

As per standard, my weblogic servers are behind firewall and only http/s on port 80/443 is allowed.

So what are the options for the connection between thin client and EJB?

1. WebLogic T3 HTTP tunneling. However, as we are not enforcing role based authentication and authorization (A&A) in EJBs currently, by HTTP tunneling, all EJBs are exposed to public.....

2. Web Services, overhead is tremendous. Host based PKI A&A can be expensive.

3.....???

Thanks in advance!
 
Ranch Hand
Posts: 1170
Hibernate Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What about servlets?
 
Bartender
Posts: 4121
IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why not make a session bean that enforces A&A, and have it delegate to the rest of your EJBs. Only make this one session bean public, and enforce that all interaction with the server from your application go through this session bean - basically a Session Facade pattern that also enforces A&A.
 
Yi Meng
Ranch Hand
Posts: 270
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
seems not much choice...similar as you suggested....

1. urlconnection to login url and save jsession id upon successful login
2. urlconnection with jsessionid to my own ejb proxy url, which forward to the relevant ejb and do the job

the constraint is mainly the A&A part, it's a component and we have to POST to the url.....
 
The only taste of success some people get is to take a bite out of you. Or this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic