Failure to comply will result in the removal of your account.
Originally posted by Ben Souther:
If they need to work together, why make them two separate applications?
Why not just add some administrator components to the application?
I had done that originally, but these two sites are being used to replace an old static website and the network administrator insists they be separated so he can apply SSL to the administrative end. He demanded complete separation of the two sites, so my hands are tied in this case.
For some reason this is a common topic here (cross context servlet communication) so you'll find plenty of discussions if you use the search feature.
Before making any suggestions, can you clarify what you mean by:
I have a servlet in the back-end that does a little processing and then needs to post an update to a servlet in the customer's side.
If the two apps share a common database, you might not need to actually post to the 'customer' app. Otherwise, if you mean that you need to make HTTP posts from one application to another, you might want to look into the httpclient libraries from the Apache Jakarta group:
[ April 05, 2007: Message edited by: Ben Souther ]