• Post Reply Bookmark Topic Watch Topic
  • New Topic

How to package client which requires access to server interfaces?  RSS feed

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

I'm new to distributed systems and thick clients, so I have a basic question.

I'm trying to devise a strategy for packaging an application that comprises of a server and a thick client, which communicate through Spring's HTTPInvoker (a simple RMI like mechanism).

The question is: how should I package the client, which requires access to interfaces from the server side application?

I want to minimise access to the server application from the client; I want to avoid having to include dependencies of the server app. in the client package.

Any thoughts?

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

you need to create an server-api-package and a server-impl-package. You Server-Api-Package contains all interfaces, but no implementation. So your client and your server-impl can include this package and use the same interfaces. If you change an interface, it will automaticly available in the server and the client, there is no code-redundance.

For smaller or learning-projects, you can create this packages by hand, for processional use, maven has good plugins.

hope i could help

Igor
 
Nitesh Kant
Bartender
Posts: 1638
IntelliJ IDE Java MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi "Igor instanceof HumanBeing",

Please check your private messages for an important administrative matter.

You can see the same using this
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!