yang
07-09-2007, 06:06 PM
What is the lightest-weight, least-overhead way to integrate an OpenLaszlo frontend with a Java backend?
I currently have a console Java application, which I'd like to give a UI facelift and expose via OpenLaszlo. The frontend will have an editable Grid, and as the user modifies the grid, the frontend will continually send the current Grid data to the server and display the results of the server's analysis next to the Grid.
What I'm currently doing is using XMLRPC - is this the simplest approach? I don't want to deal with setting up Tomcat servers or servlets or XML configuration files or any of that stuff. With XMLRPC (running off the ws-xmlrpc embedded server), I can avoid these, but I still need to serialize my data to XMLRPC-friendly structures, and vice-versa, on each side of the transport.
Also, are there any facilities for two-way network-transparent binding (not just the read-only "src" attribute on components, and not necessarily requiring XML marshalling)? I wouldn't be surprised if there isn't, as I think it would require backend-specific stuff. (Although, such an ambitious step would be revolutionary! And it's something I fear is practical for Silverlight, as there is only one primary backend, .NET, which also happens to be the same platform as the frontend.)
Thanks for any answers.
I currently have a console Java application, which I'd like to give a UI facelift and expose via OpenLaszlo. The frontend will have an editable Grid, and as the user modifies the grid, the frontend will continually send the current Grid data to the server and display the results of the server's analysis next to the Grid.
What I'm currently doing is using XMLRPC - is this the simplest approach? I don't want to deal with setting up Tomcat servers or servlets or XML configuration files or any of that stuff. With XMLRPC (running off the ws-xmlrpc embedded server), I can avoid these, but I still need to serialize my data to XMLRPC-friendly structures, and vice-versa, on each side of the transport.
Also, are there any facilities for two-way network-transparent binding (not just the read-only "src" attribute on components, and not necessarily requiring XML marshalling)? I wouldn't be surprised if there isn't, as I think it would require backend-specific stuff. (Although, such an ambitious step would be revolutionary! And it's something I fear is practical for Silverlight, as there is only one primary backend, .NET, which also happens to be the same platform as the frontend.)
Thanks for any answers.