Win a copy of Pro Spring MVC with WebFlux: Web Development in Spring Framework 5 and Spring Boot 2 this week in the Spring 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Bear Bibeault
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:
  • Frits Walraven
  • Himai Minh

Why bytecodes???

 
Ranch Hand
Posts: 236
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Isn't a "web service" supposed to pass XML (not bytecodes/class files)? It sounds a bit like you're trying to re-invent RMI.

Axis implements SOAP. Why don't you have your Java app use SOAP, too?
 
Ranch Hand
Posts: 78
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Web Service is supposed to pass XML because of the interoperability issue. Because these byte codes/class files does some computation and are not simply messages, passing them as XML may not be work, right.

I am trying to use SOAP bindings here .... client sends these byte codes thru AXIS....AXIS takes the byte codes and serializes....deserialization on the server Web Service side...back to Java object....bindings still remains SOAP binding as on the client side.....but when I execute this on the server....fails ! Interestingly, these byte codes arrive safely on the server and when I run them on the server side via a command shell, works great !

This client code is similar to ones in their samples from Axis 1.1.

Best bet would be to use local binding because SOAP is expensive. In short, client sends class file on the server, server executes these arrived byte codes on the fly, the byte codes makes a local method call on the server Web Service already exposed methods, and comes back with the result. Hence, I consume less network resources.

What do you think?
 
Ranch Hand
Posts: 8944
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

but when I execute this on the server....fails



How are you excecuting it?
 
reply
    Bookmark Topic Watch Topic
  • New Topic