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 3272944
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T18:52:47+00:00 2026-05-17T18:52:47+00:00

We have created a web service using JAX-WS and ProSyst OSGi. Accessing the service

  • 0

We have created a web service using JAX-WS and ProSyst OSGi.
Accessing the service with the following code works fine in a standalone Java application
as well as in the ProSyst framework.

this.service = new MyServicePortService(
            new URL("http://" + host + ":" + port + "/MyService?wsdl"),
            new QName("http://myservice.example.com/", "MyServicePortService"));
this.client = this.service.getMyServicePort();

AS JAX-WS needs some packages from javax.* and others I have to make them exported by the framework bundle. This is done by telling the ProSyst framework to export them via its configuration but could also be done by writing an extension bundle with the following export statement: (what we have done for equinox.)

Export-Package
  com.sun.net.ssl.internal.ssl          
  com.sun.xml                           
  com.sun.xml.internal.bind.api         
  javax.crypto                          
  javax.crypto.spec                     
  javax.jw                              
  javax.naming                          
  javax.naming.directory                
  javax.naming.event                    
  javax.naming.ldap                     
  javax.naming.spi                      
  javax.net                             
  javax.net.ssl                         
  javax.security.cert                   
  javax.transaction.xa                  
  javax.xml.bind.util                   
  javax.xml.stream                      
  javax.xml.transform.stax              
  javax.xml.ws                          
  org.apache.log4j                      
  sun.security.action

My understanding is, that this should also work in Equinox, as they use the same JVM. So if those bundles are accessible, JAX-WS should work in both.

However, calling this.service.getMyServicePort() will result in the following exception:

java.lang.IllegalArgumentException: interface com.sun.xml.internal.ws.developer.WSBindingProvider is not visible from class loader
    at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353)
    at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.createEndpointIFBaseProxy(WSServiceDelegate.java:546)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:292)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:274)
    at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:267)
    at javax.xml.ws.Service.getPort(Service.java:92)
    at com.example.myservice.MyServicePortService.MyServicePort(MyServicePortService.java:56)
    at com.example.myservice.MyServicePort.<init>(MyServicePort.java:36)
    at com.example.myservice.ClientActivator.activate(ClientActivator.java:78)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)
    at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
    at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
    at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
    at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
    at org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:393)
    at org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:176)
    at org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:791)
    at org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:758)
    at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:90)
    at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)

Anybody an idea how to solve this? Or is there an other/better possibility to access the service from equinox? (DOSGI is not used, as the service should also be accessible by other native applications).

Thanks is advance

  • 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-17T18:52:48+00:00Added an answer on May 17, 2026 at 6:52 pm

    It seems that package com.sun.xml.internal.ws.developer is not visible.

    Try 2 ways:

    • add this package (and maybe not only this one) to the list of exported packages in system bundle (system property: org.osgi.framework.system.packages). Import this package(s) explicitly or with Dynamic-ImportPackage header
    • use system property org.osgi.framework.bootdelegation to delegate this package to the system classloader.

    Hope it helps you.

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

Sidebar

Related Questions

I have created a simple web-service using Java. i want to load jars related
I have created a RESTful PHP web service using Lithium which contains comments, each
I have created one application in flex that is accessing the Java webservice using
I have created a Web Service (with Java, Axis). Depending on the content of
I have a JAX-RPC web service that I am attempting to consume using Spring.
I have created a web service which has a couple of methods developed using
I have developed a web service using JAX-WS and in the web.xml i had
I have created a Web service using Netbeans', JEE6 and Jersey - Webservice from
I have created a REST web service using WCF and use HTTP Post Method.
I have created a web service using Microsoft C# and i was able to

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.