Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7676079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T17:06:58+00:00 2026-05-31T17:06:58+00:00

I have several web service written formerley and deployed on tomcat. Now I am

  • 0

I have several web service written formerley and deployed on tomcat. Now I am to develop a new UI with eclipse RCP ( Old SWT application is a little bit redundat). I must make a chooice. I’ll use this web service directly with jax-ws client or I’ll use OSGI to wrap this service and use this structure via OSGI. Which solution do you suggest ?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T17:07:00+00:00Added an answer on May 31, 2026 at 5:07 pm

    Expose your webservices as OSGi services. This keeps a nice separation between implementation details and the consumer (the UI).

    This make it easy if you decide to change the web service to some other type of service (straight servlet calls for instance), and more importantly, trivial to mock your services for developing/testing the new UI.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have build several web service based on .net. Now we want to create
I have to use several SOAP messages to get data from a web service.
I have a web service with several methods, each method has its own response
I have a web service project with several web services. Two of this web
Here's my problem. I have a middleware web service used by several web clients.
I have a tricky situation here. I have a web service written in C#
I have a web service with several web methods, each web method requires client
I have several projects written in f/x4.0 that are not MVC. No web involved.
I have a web application written in C# that consumes several internal web services.
Several web service APIs have you sign up for an API key. For example,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.