[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 528
  • Last Modified:

Rewrite of Java front end

I have an existing Java application. The application has a complex GUI, number crunching and db interaction. The front and back ends are cleanly separate. Suppose I wanted to host the backend of the application in a server and rewrite the front end in something other than Java to work on a client browser. What would be the best choice for this? PHP? This is probably a religious issue, but I'm interested to hear all opinions.
0
allelopath
Asked:
allelopath
3 Solutions
 
ksivananthCommented:
it all depends the requirement, for e.g., if the front end manage lots of contents, PHP good option. the question id why do you want to move away from Java!
0
 
CEHJCommented:
We really need more detail. When you say 'application' is this a Java web app or a standard, desktop-type app?
0
 
for_yanCommented:
In a sense of "working inside the browser" Java with applets which really "work inside the browser" is fairly unique.
You can replace this functuionality sometimes with Flash or Adobe Flex, sometimes with Ajax or even sometimes  with plain JavaScript, I guess, with ActiveX controls, however nothing will probably give you equal level of flexibility and ability to rely on the presence in the browsers as java.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
objectsCommented:
I'd go with javascript for the front end.

> PHP?

php is a backend technology
0
 
allelopathAuthor Commented:
CEHJ: Standard desk-type application
0
 
objectsCommented:
php is a backend technology that you would use to generate the html for the frontend.
You're leaving the backend as is aren't you?
0
 
CEHJCommented:
Why not make as few changes as possible? Think about (since the gui seems to be correctly loosely coupled) making it an applet communicating  with the back end (hosted on the web). You will of course need a bridging comms layer, possibly something like RMI, to allow the applet to communicate with the application.

OTOH, if really all you want is web delivery and it's not essential for the ui to be in a browser window, then Web Start will leave you with the least work
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now