Re: Karaf + SOAP + JDK 21

2023-11-15 Thread Matt Pavlovich
Hi Mark-

Glad to hear it’s working for you! 

-Matt

> On Nov 15, 2023, at 3:58 PM, Mark Derricutt  wrote:
> 
> Hi Matt - that's both sad, and great to hear.
> 
> Updated the dependency and working like a charm.  Cheers!
> 
> On 16/11/23 3:44 am, Matt Pavlovich wrote:
>> The maven-jaxb2-plugin, jaxb2-basics and other jaxb2 commons plugins
>> have been modernized for jakarta (I’m now the project lead, since the
>> maintainer sadly passed away).



Re: Karaf + SOAP + JDK 21

2023-11-15 Thread Mark Derricutt

Hi Matt - that's both sad, and great to hear.

Updated the dependency and working like a charm.  Cheers!

On 16/11/23 3:44 am, Matt Pavlovich wrote:

The maven-jaxb2-plugin, jaxb2-basics and other jaxb2 commons plugins
have been modernized for jakarta (I’m now the project lead, since the
maintainer sadly passed away).

Re: Karaf + SOAP + JDK 21

2023-11-15 Thread Matt Pavlovich
Hi Mark-

The maven-jaxb2-plugin, jaxb2-basics and other jaxb2 commons plugins have been 
modernized for jakarta (I’m now the project lead, since the maintainer sadly 
passed away).

The Maven plugin, jaxb-basics (now called jaxb-plugins) and several of the 
ancillary projects have all been collapsed into a single repo ‘jaxb-tools' 


See version: 4.0.0 

https://github.com/highsource/jaxb-tools/

Thanks,
Matt Pavlovich

> On Nov 15, 2023, at 3:10 AM, Mark Derricutt  wrote:
> 
> and updated cxf-codegen-plugin to 4.0.3. Interestingly, I couldn't find any 
> suitable replacements/updates for org.jvnet.jaxb2_commons:jaxb2-fluent-api 
> it's sibling XCJ extensions so had to rewrite one wrapper service to match 
> the changed code-gen.



Re: Karaf + SOAP + JDK 21

2023-11-15 Thread Grzegorz Grzybek
Thanks for the feedback!

In my custom distro (Fuse), I'm still stuck with javax.* packages. This is
what I have in lib/jdk9plus:

istack-commons-runtime-3.0.10.redhat-3.jar
jakarta.jws-api-2.1.0.redhat-3.jar
jakarta.xml.bind-api-2.3.3.redhat-3.jar
jakarta.xml.soap-api-1.4.2.redhat-1.jar
jakarta.xml.ws-api-2.3.3.redhat-1.jar
jaxb-runtime-2.3.4.jar
txw2-2.3.4.jar

so yes - there's also jakarta.jws-api (but the one with javax packages).

regards
Grzegorz Grzybek

śr., 15 lis 2023 o 10:11 Mark Derricutt  napisał(a):

> Unfortunately that didn't quite work as I fell into the trap of then
> needing javax.jws.
>
> However - I do now have it working, tho I did have to end up updating
> the bundle that included the WSDL generation. In my custom distribution
> I now have:
>
> version="${project.version}">
>  mvn:jakarta.activation/jakarta.activation-api/2.1.2
>  mvn:jakarta.jws/jakarta.jws-api/3.0.0
>  mvn:jakarta.xml.bind/jakarta.xml.bind-api/4.0.0
>  mvn:jakarta.xml.ws/jakarta.xml.ws-api/4.0.1
>  mvn:jakarta.xml.soap/jakarta.xml.soap-api/3.0.1
>  cxf-core
>  cxf-jaxws
>  cxf-http
>  cxf-specs
>  cxf-wsdl
>  cxf-databinding-jaxb
>  cxf-bindings-soap
>
>
> It's possible I could trim some of the included 's there as
> they're transcluded by the others, but for now this works. This switches
> to the jakarta.xml version of packages, which avoids the default export
> of javax.xml. In the karaf-maven-plugin configuration, I had to set
> 11 tho as it was a requirement for one of those bundles
> (I forget which off hand), and for some reason I couldn't use
> 21 as it claimed it wasn't a valid Java version.
>
> On the service side, I had to add the following dependencies:
>
>
>jakarta.jws
>jakarta.jws-api
>3.0.0
>  
>  
>jakarta.xml.bind
>jakarta.xml.bind-api
>4.0.0
>  
>  
>jakarta.xml.ws
>jakarta.xml.ws-api
>4.0.1
>  
>  
>javax.xml.bind
>jaxb-api
>[2.3.1]
>
>  
>*
>*
>  
>
>  
>  
>javax.xml.ws
>jaxws-api
>[2.3.1]
>
>  
>*
>*
>  
>
>  
>
> and updated cxf-codegen-plugin to 4.0.3. Interestingly, I couldn't find
> any suitable replacements/updates for
> org.jvnet.jaxb2_commons:jaxb2-fluent-api it's sibling XCJ extensions so
> had to rewrite one wrapper service to match the changed code-gen.
>
> But it seems to be working now.  At least - the custom image
> builds/verifies and starts up - I've not yet tried calling any of the
> services yet.  Tomorrows job.
>
>
> Mark
>
> On 6/11/23 8:44 pm, Grzegorz Grzybek wrote:
> > I think you should simply drop jakarta.xml.ws-api-2.3.3.jar
> > <
> https://repo1.maven.org/maven2/jakarta/xml/ws/jakarta.xml.ws-api/2.3.3/jakarta.xml.ws-api-2.3.3.jar
> >
> > into KARAF_HOME/lib/jdk9plus


Re: Karaf + SOAP + JDK 21

2023-11-15 Thread Mark Derricutt
Unfortunately that didn't quite work as I fell into the trap of then 
needing javax.jws.


However - I do now have it working, tho I did have to end up updating 
the bundle that included the WSDL generation. In my custom distribution 
I now have:


  
mvn:jakarta.activation/jakarta.activation-api/2.1.2
mvn:jakarta.jws/jakarta.jws-api/3.0.0
mvn:jakarta.xml.bind/jakarta.xml.bind-api/4.0.0
mvn:jakarta.xml.ws/jakarta.xml.ws-api/4.0.1
mvn:jakarta.xml.soap/jakarta.xml.soap-api/3.0.1
cxf-core
cxf-jaxws
cxf-http
cxf-specs
cxf-wsdl
cxf-databinding-jaxb
cxf-bindings-soap
  

It's possible I could trim some of the included 's there as 
they're transcluded by the others, but for now this works. This switches 
to the jakarta.xml version of packages, which avoids the default export 
of javax.xml. In the karaf-maven-plugin configuration, I had to set 
11 tho as it was a requirement for one of those bundles 
(I forget which off hand), and for some reason I couldn't use 
21 as it claimed it wasn't a valid Java version.


On the service side, I had to add the following dependencies:

  
  jakarta.jws
  jakarta.jws-api
  3.0.0
    
    
  jakarta.xml.bind
  jakarta.xml.bind-api
  4.0.0
    
    
  jakarta.xml.ws
  jakarta.xml.ws-api
  4.0.1
    
    
  javax.xml.bind
  jaxb-api
  [2.3.1]
  
    
  *
  *
    
  
    
    
  javax.xml.ws
  jaxws-api
  [2.3.1]
  
    
  *
  *
    
  
    

and updated cxf-codegen-plugin to 4.0.3. Interestingly, I couldn't find 
any suitable replacements/updates for 
org.jvnet.jaxb2_commons:jaxb2-fluent-api it's sibling XCJ extensions so 
had to rewrite one wrapper service to match the changed code-gen.


But it seems to be working now.  At least - the custom image 
builds/verifies and starts up - I've not yet tried calling any of the 
services yet.  Tomorrows job.



Mark

On 6/11/23 8:44 pm, Grzegorz Grzybek wrote:

I think you should simply drop jakarta.xml.ws-api-2.3.3.jar

into KARAF_HOME/lib/jdk9plus