Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

GWT and Hibernate - Issue with Dom4j

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Iam writing a small program to integrate GWT and Hibernate.

GWT RPC works fine by itself, tested it by hardcoding some data on server and sending the object back to client.

My standalone Hibernate program works fine. But when I try to integrate it with GWT, I get an error stating

"Initial SessionFactory creation failed. java.lang.NoClassDefFoundError: java.net.Socket is a restricted class. Please see the Google App Engine developer's guide for more details. "

I had read on one of the forums that the above class isn't permitted for GWT. Iam assuming the problem has to do with Dom4j's use of the above class. Is there any implementation of DOM4J which doesn't use this class?

Iam using the jar dom4j-1.6.1.jar; Below is the source for Server Implementation.

Any help would be greatly appreciated.

Thanks,
Ajay

Class - FetchPlgplfServiceImpl.java (Server side implementation)

Class - MyApplicationHibernateUtil

gwt.xml





 
Marshal
Posts: 25815
69
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would be surprised if Dom4J were explicitly using a socket. It's just an XML parser after all. But it's possible that something in your XML document refers to a URL, and therefore the parser tries to read the document at that URL. Culprits could be DTD or schema references, for example.
 
ajay krishna
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot Paul. I found out the problem. Iam trying to connect to DB2 database sitting on a AS/400.

Iam using the jt400.jar as the jdbc driver and that seems to be referencing the socket class.

 
Paul Clapham
Marshal
Posts: 25815
69
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's right, JDBC almost always communicates via socket (except for non-standard databases like MS Access).
 
I have a knack for fixing things like this ... um ... sorry ... here is a consilitory tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic