Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JTwain API not responding from applet (Called through a JSP)

 
deepak veyan
Greenhorn
Posts: 10
Java MySQL Database Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We had been migrating our projects to Linux from windows.Among which is a Java Applet being invoked from a JSP to facilitate scanning via JTwain API.This has stopped working.On checking the Applet console , code execution seems to be smooth till the following



There is no exception being thrown as well. Also , jar signing has also been done (Though there is another application that works superbly even without this).

Any advice would be highly appreciated.

This is my first question on the forum , kindly excuse if there had been any non-compliance with standards.
 
Maneesh Godbole
Saloon Keeper
Posts: 11021
12
Android Eclipse IDE Google Web Toolkit Java Mac Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Disclaimer: I haven't worked with JTwain

When you say "stopped working" what exactly happens?
There is no exception being thrown as well

Did you check for empty catch blocks in your code?
As per the API docs, http://asprise.com/product/jtwain/javadoc/com/asprise/util/jtwain/Source.html#acquireImage(), it does throw an exception
 
Darryl Burke
Bartender
Posts: 5125
11
Java Netbeans IDE Opera
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
deepak vn wrote:code execution seems to be smooth till the following



That's not valid, compilable Java code. To get help on a forum, you need to PostRealCode (<-link).
 
deepak veyan
Greenhorn
Posts: 10
Java MySQL Database Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you everyone for your kind responses.I will ensure to post more explanatory code next time on wards.The code we were trying to migrate itself had certain problems and we later on went on to identify the module though was on production was not being used at all. Hence the same is halted as of now.

Once again , thank you everyone !
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic