[
https://issues.apache.org/jira/browse/AXIOM-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622347#comment-17622347
]
Jeff Thomas commented on AXIOM-506:
-----------------------------------
Possible the Veithen XJC plugin is no longer necessary?
Maybe the jaxb2-maven-plugin is now sufficient with Java 11 compiler? With the
proper dependeny setup this should also generate the jakarta imports.
Andreas documented this plugin as a temporary solution to the following 3
problems.
* It must have separate goals to generate main and test sources
(maven-jaxb2-plugin does not) and generated test sources must be added
correctly to the Maven project (jaxb2-maven-plugin [does
not|http://svn.apache.org/viewvc/axis/axis2/java/core/trunk/modules/metadata/pom.xml?r1=1815130&r2=1815129&pathrev=1815130]).
* It must works out of the box with recent Java versions (At the time of
writing, cxf-xjc-plugin did not; jaxb2-maven-plugin was
[fixed|https://github.com/mojohaus/jaxb2-maven-plugin/issues/138] in 2.5.0).
* It shouldn't fork a new VM to invoke xjc.
>From the plugin documentation:
>https://www.mojohaus.org/jaxb2-maven-plugin/Documentation/v3.1.0/index.html
#1 - I think has been fixed - there are now "xjc" and "testXjc" goals.
#2 - Built with JDK8 I believe
#3 - not sure
Hint: I know from experience when moving to this plugin and migrating to
jakarta you need to pay attention to update the schema references in any XJB
Binding FIles to jakarta as well. :)
> Upgrade to org.glassfish 3.0.1 and jakarta packages
> ---------------------------------------------------
>
> Key: AXIOM-506
> URL: https://issues.apache.org/jira/browse/AXIOM-506
> Project: Axiom
> Issue Type: Improvement
> Reporter: Robert Lazarski
> Priority: Major
>
> The following was my attempt to upgrade axiom to the latest Glassfish and the
> new jakarta package name that replaces javax.
> I am trying to upgrade Axis2 to the current Glassfish release, 3.0.1.
> Concerning Axiom, the problem is that one of our Axis2 classes extends the
> Axiom DataHandlerWrapper class.
> I got stuck on this dependency in the axiom-testsuite module.
> <groupId>com.github.veithen.maven</groupId>
> <artifactId>xjc-maven-plugin</artifactId>
> The problem is that this plugin generates sources with javax.xml.bind instead
> of jakarta.xml.bind.
>
> Please see below for the required changes to support the new package name. .
>
> sed -i 's/import javax.xml.bind/import jakarta.xml.bind/g' $(find . -type f)
> sed -i 's/import javax.activation/import jakarta.activation/g' $(find .
> -type f)
> sed -i 's/import javax.mail/import jakarta.mail/g' $(find . -type f)
>
> Replaced awt classes in DataHandlerWrapper with jakarta classes.
>
> pom.xml, and module pom.xml files:
>
> <jaxbri.version>3.0.1</jaxbri.version>
> <activation.version>2.0.1</activation.version
> <jakarta.mail.version>2.0.1</jakarta.mail.version>
>
> <dependency>
> <groupId>jakarta.activation</groupId> <!-- instead of
> com.sun.activation -->
> <artifactId>jakarta.activation-api</artifactId>
> <version>${activation.version}</version>
> </dependency>
> <dependency>
> <groupId>jakarta.mail</groupId>
> <artifactId>jakarta.mail-api</artifactId> <!-- instead of
> com.sun.mail -->
> <version>${jakarta.mail.version}</version>
> </dependency>
> <dependency>
> <groupId>com.sun.mail</groupId>
> <artifactId>jakarta.mail</artifactId>
> <version>2.0.1</version>
> </dependency>
> <dependency>
> <groupId>jakarta.xml.bind</groupId>
> <artifactId>jakarta.xml.bind-api</artifactId>
> <version>${jaxbri.version}</version>
> </dependency>
>
>
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
