Hi Lukas,
Thank you very much for the hint.
I encountered two problems with the webservices-osgi-2.4.3 plugin.
Firstly I get a class not found exception:
Caused by: java.lang.NoClassDefFoundError: com/sun/org/apache/xml/internal/resolver/CatalogManager
at com.sun.xml.ws.util.xml.XmlUtil.createDefaultCatalogResolver(XmlUtil.java:296)
at com.sun.xml.ws.client.WSServiceDelegate.createCatalogResolver(WSServiceDelegate.java:348)
at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:334)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:292)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:201)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:182)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:178)
at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:89)
at javax.xml.ws.Service.<init>(Service.java:82)
at au.net.synergy.wts.server.ws.client.management.ServerManagerImplService.<init>(ServerManagerImplService.java:46)
As far as I can tell that class is not in the webservices-osgi-2.4.3.jar file but it does appear in webservices-osgi-2.4.3-sources.jar.
Secondly, webservices-osgi-2.4.3.jar requires javax.servlet; version="[4.0.0,5.0.0)" while Jetty with comes with Eclipse 2019-03 RCP/RAP
requires javax.servlet; version="[3.1.0,4.0.0). If I include both bundles (jakarta.servlet-api-4.0.2 and javax.servlet_3.1.0.v201410161800) then Eclipse complains about unresolved dependencies for all the Jetty plugins. If I only include javax.servlet_3.1.0.v201410161800
then Eclipse complains about an unresolved dependency for webservices-osgi-2.4.3.
Thanks
Manuel
From: jaxws-dev-bounces@xxxxxxxxxxx [mailto:jaxws-dev-bounces@xxxxxxxxxxx]
On Behalf Of Lukas Jungmann
Sent: Sunday, 7 April 2019 9:01 PM
To: jaxws developer discussions <jaxws-dev@xxxxxxxxxxx>
Subject: Re: [jaxws-dev] How to deploy jax-ws into an Eclipse RCP target platform?
org.glassfish.metro:webservices-osgi artifact together with jaxb-osgi is probably what you want.
Hi,
I am pretty sure this is not the correct mailing list but I can't find anything more appropriate and the Eclipse EE4J related forums are dead and have no
messages.
We have a sizeable (>100 plugins) Eclipse RCP and RAP application and decided (foolishly?) to undertake a technology refresh and upgrading everything to the
latest stable versions. Currently we are on Java 8 and Eclipse Neon. So we are now trying to get this thing working under Eclipse 2019-03 and Java 11. Everything seems largely fine but the JAX-WS stack. I cannot figure out how to deploy it into our target
platform so that all our existing plugins that require JAX-WS can make use of it. I grabbed the jaxws 2.3.2 all-in-one ZIP from Maven Central and while most of the jakarta-...-api and related jar files happily live in our new RCP target-platform and are visible
to our plugins (and everything compiles and builds fine) the implementation jar files like for example jaxws-ri are not packaged as OSGI bundles and therefore at runtime nothing works as the implementation of various services are not found.
So in the nutshell my question is just about how to make jaxws 2.3.2 available in OSGI based Eclipse RCP and RAP target-platforms using RCP/RAP 2019-03 and
Java 11?
Any pointers would be much appreciated.
Kind Regards
Manuel
ELECTRICITY GENERATION AND RETAIL CORPORATION
TRADING AS SYNERGY (ABN 58 673 830 106)
Perth, Western Australia
Telephone:-
For residential enquiries: 13 13 53
For business enquiries: 13 13 54
TO THE ADDRESSEE: Unencrypted email is not secure and may not be authentic. We cannot guarantee the accuracy, reliability, completeness or confidentiality of this email and any attachments ("email").
IF YOU ARE NOT THE INTENDED ADDRESSEE: This email is intended solely for the intended addressee and may be subject to legal or other professional privilege, or may contain information that is confidential or exempt from disclosure by law. Copying, distributing
or taking action in reliance on the contents of this email or any information it may contain, by anyone other than the intended addressee, is prohibited. If you have received this email in error please notify us immediately by return email or by telephone;
and destroy this email and any electronic or hard copies of it. Any claim to privilege or confidentiality is not waived or lost by reason of mistaken transmission of this email.
VIRUSES: Although we scan all outgoing email and attachments for viruses, we cannot guarantee that viruses will not be transmitted with this email. It is the recipient's responsibility to check this email for viruses. Synergy accepts no liability for
any damage caused by any virus transmitted by this emails.
