I have several products at work which use Perl and Oracle to generate HTML/JSON for a jQuery front end. Use a framework (Dancer/CGI::Application) to quickly develop a prototype system that allows you to test the functionality/widgets you require. Then you'll be able to tell if this is a "good option" or not. Consider using a templating system (Template::Toolkit, HTML::Template...) to keep your perl code seperate from the HTML/CSS/JavaScript.

marto

could you please provide links for the products developed to get an idea

An idea of what? These are internal tools for our client, and aren't internet accessable. It sounds like you need to spend the time to investigate which serverside and client side framework to use. A google/web search will provide various resources I'm sure. This is seems like a vague set of requirements, if you have any concrete technical questions feel free to let us know.

Vague answer:

Providing links like http://www.jqwidgets.com facilitate getting more "thoughts and ideas" and helping others to profit from the discussion. =)

edit

Another thought is that you could although try to better narrow your goal and requirements, to make answering easier.

HTH =)

I am trying to develop a website using Perl, Oracle and jQWidgets. I know this is a vague question whether this is a good option, but any thoughts and ideas are appreciated.

Try knots :)

important details

Mojolicious/Ajax Server-Side File Tree

Copy/paste from Re: To call a .pl file when a button is pressed on a GUI created using Perl CGI (webserver) for the links below

Its simple, you need a webserver

Why? Because webpages and CGI needs a webserver, thats how it works

Its weird that so many folks manage to create a GUI using Perl CGI without understanding this

learn about the internet,Web Programming: For Beginners, to get an overall picture of how the internet works, how tcp/ip, sockets, html, ajax, all fit together....

See also Mojolicious::Lite +and jQuery +AJAX + Mojo::Template

And a copy-pasta for you:)

Also, there are checklists for that , Basic debugging checklist , brian's Guide to Solving Any Perl Problem, CGI Help Guide , Troubleshooting Perl CGI scripts

Yes, work through these checklists, when you find a problem on the list, use a solution from the list, when you find a problem not on the list (rare), post the error message and problem description here

brian's Guide to Solving Any Perl Problem, CGI Help Guide , Troubleshooting Perl CGI scripts

So examine your server configuration and compare to https://httpd.apache.org/docs/2.2/howto/public_html.html#cgi / Apache Tutorial: Dynamic Content with CGI

learn about the internet,Web Programming: For Beginners, to get an overall picture of how the internet works, how tcp/ip, sockets, html, ajax, all fit together.

... a vague question whether this is a good option ...

You can save a lot of money by ditching Oracle and adopting PostgreSQL instead.

Happy New Year!

I'd ++ this a hundred times if I could. From my experience, PostgreSQL is also easier to work with for developers, DBAs and sysadmins.

Update:

At $work, we're probably saving about $80k a year in royalties and/or licensing fees to Oracle. We no longer need to keep an Oracle DBA on retainer so we're saving more money there.

It takes less than a 1 minute to install our custom compilation of Pg as opposed to 15 or 20 minutes for the equivalent Oracle install. I couldn't tell you how many software engineer man-hours each year we used to spend tracking down Oracle specific bugs because we received absolutely no support from them (several hundred at least). As you all know, time is money.

You're experiences may be different from ours but everyone that I've spoken to who has also made the switch has had nothing but good things to say about PostgreSQL and always gush about the total cost of ownership. :)