remove obsolete content from docs
Signed-off-by: Lukas Jungmann <lukas.jungmann@oracle.com>
diff --git a/jaxb-ri/docs/release-documentation/src/docbook/release-notes.xml b/jaxb-ri/docs/release-documentation/src/docbook/release-notes.xml
index 6bca9ef..ab15fe2 100644
--- a/jaxb-ri/docs/release-documentation/src/docbook/release-notes.xml
+++ b/jaxb-ri/docs/release-documentation/src/docbook/release-notes.xml
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
- Copyright (c) 2012, 2021 Oracle and/or its affiliates. All rights reserved.
+ Copyright (c) 2012, 2022 Oracle and/or its affiliates. All rights reserved.
This program and the accompanying materials are made available under the
terms of the Eclipse Distribution License v. 1.0, which is available at
@@ -38,7 +38,7 @@
<trademark>Java</trademark> SE Requirements
</title>
- <para>This release of the &binding.impl.name; requires Java SE 8 or higher.</para>
+ <para>This release of the &binding.impl.name; requires Java SE 11 or higher.</para>
</section>
<section xml:id="jars">
@@ -72,8 +72,11 @@
<entry>
<para>
+ <filename>jakarta.activation-api.jar</filename>,
+ <filename>angus-activation.jar</filename>,
<filename>jakarta.xml.bind-api.jar</filename>,
- <filename>jaxb-impl.jar</filename>,
+ <filename>jaxb-core.jar</filename>,
+ <filename>jaxb-impl.jar</filename>
</para>
</entry>
</row>
@@ -87,8 +90,7 @@
<entry>
<para>
- <filename>jakarta.xml.bind-api.jar</filename>,
- <filename>jaxb-impl.jar</filename>,
+ <filename>jaxb-jxc.jar</filename>,
<filename>jaxb-xjc.jar</filename>
</para>
</entry>
@@ -102,7 +104,7 @@
<title>Locating the Normative Binding Schema</title>
<para>You may find information about the normative binding schema
- defined in the &binding.spec.name; Specification at<link
+ defined in the &binding.spec.name; Specification at <link
xlink:href="https://jakarta.ee/xml/ns/jaxb">https://jakarta.ee/xml/ns/jaxb</link>.
</para>
</section>
diff --git a/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment-migrating-jaxb-2-0-applications-to-javase-6.xml b/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment-migrating-jaxb-2-0-applications-to-javase-6.xml
deleted file mode 100644
index 32fd4e4..0000000
--- a/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment-migrating-jaxb-2-0-applications-to-javase-6.xml
+++ /dev/null
@@ -1,146 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-
- Copyright (c) 2012, 2021 Oracle and/or its affiliates. All rights reserved.
-
- This program and the accompanying materials are made available under the
- terms of the Eclipse Distribution License v. 1.0, which is available at
- http://www.eclipse.org/org/documents/edl-v10.php.
-
- SPDX-License-Identifier: BSD-3-Clause
-
--->
-
-<!DOCTYPE book [
-<!ENTITY % ents SYSTEM "docbook.ent">
-%ents;
-]>
-<section version="5.0"
- xml:id="deployment-migrating-jaxb-2-0-applications-to-javase-6"
- xml:lang="en" xmlns="http://docbook.org/ns/docbook"
- xmlns:xlink="http://www.w3.org/1999/xlink"
- xmlns:ns5="http://www.w3.org/1999/xhtml"
- xmlns:ns3="http://www.w3.org/2000/svg"
- xmlns:ns="http://docbook.org/ns/docbook"
- xmlns:m="http://www.w3.org/1998/Math/MathML">
- <title>Older versions of JAXB and JavaSE</title>
-
- <para>JavaSE 6 ships with its own JAXB 2.0 implementation. This
- implementation is based on the JAXB RI, where the only differences
- are:</para>
-
- <itemizedlist>
- <listitem>
- <para><emphasis role="bold">No RI-specific vendor extensions are
- supported:</emphasis> This is so that portability across different
- JavaSE 6 implementations will be guaranteed.</para>
- </listitem>
-
- <listitem>
- <para><emphasis role="bold">Code in JavaSE 6 is hosted in its own
- packages to avoid conflicts:</emphasis> This allows applications
- to continue to use a specific version of the JAXB RI that they
- choose to use.</para>
- </listitem>
- </itemizedlist>
-
- <para>Therefore, if you develop an application that uses JAXB 2.0 for
- JavaSE 5 today, the easiest way to upgrade to JavaSE 6 is to do nothing.
- You should keep the JAXB RI in your development environment, keep bundling
- the JAXB RI runtime jars to your app, just like you do that today.</para>
-
- <section xml:id="Reducing_footprint">
- <title>Reducing footprint</title>
-
- <para>If you'd like to reduce the footprint of your application by
- taking advantage of a JAXB implementation in JavaSE, you can take
- the following steps:</para>
-
- <orderedlist>
- <listitem>
- <para>You will no longer have to ship
- <filename>jakarta.xml.bind-api.jar</filename> in your application. This doesn't
- require any change to your code.</para>
- </listitem>
-
- <listitem>
- <para>If your application does not use any of the vendor
- extension features of the JAXB RI runtime (such as
- unmarshaller/marshaller properties whose names start with
- "<literal>com.sun.</literal>"), then you will no longer have to ship
- <filename>jaxb-impl.jar</filename> (nor <filename>jaxb1-impl.jar</filename>,
- <filename>jaxb-libs.jar</filename>.) When you do this, be sure to test
- your application since it's not very easy to find all such
- dependencies.</para>
- </listitem>
- </orderedlist>
- </section>
-
- <section xml:id="Using_JAXB_with_JavaSE">
- <title>Using JAXB with Java SE</title>
-
- <para>JavaSE comes with JAXB 2.x API/implementation in <literal>rt.jar</literal>. Each
- version of JavaSE (6, 7, 8, ...) contains different version of JAXB 2.x
- API. Therefore, if you want to use different version of JAXB API/implementation
- than the one present in your version of JDK, you are required to override
- a portion of <literal>rt.jar</literal> with the new API. There are
- several ways to achieve this:</para>
-
- <orderedlist>
- <listitem>
- <para>
- Place the <filename>jakarta.xml.bind-api.jar</filename> into
- <code>$JRE_HOME/lib/endorsed</code>. <emphasis role="bold">Do not put other JAXB jars into the
- endorsed directory.</emphasis> And put jaxb-impl, jaxb-core to classpath of your application.
- This essentially makes your JRE to "JRE X + JAXB 2.y". This would
- affect any other applications that use this JRE, and it's easy.
- On the other hand, in various scenarios you may not be able to
- alter the JRE.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Use the system property <literal>java.endorsed.dirs</literal> when you launch your application, and
- have it point to the directory which contains the <filename>jakarta.xml.bind-api.jar</filename> only.
- <emphasis role="bold">The directory must not contain any other jaxb artifacts (like jaxb-impl.jar or
- jaxb-xjc.jar).</emphasis> This allows you use to use different version of JAXB for different
- applications.
- </para>
- </listitem>
-
- </orderedlist>
-
- <para>No matter which approach you take, make sure not to include jar
- files other than <filename>jakarta.xml.bind-api.jar</filename>. Doing so, for example
- including <filename>jaxb-xjc.jar</filename>, may result in classloading
- related errors such as "taskdef A class needed by class
- com.sun.tools.xjc.XJCTask cannot be found:
- org/apache/tools/ant/...."</para>
-
- <para>See <link
- xlink:href="http://docs.oracle.com/javase/6/docs/technotes/guides/standards/">the
- endorsed directory mechanism</link> for more details.</para>
- </section>
-
- <section xml:id="Where_s_the_XJC_ant_task_">
- <title>Where's the XJC ant task?</title>
-
- <para>JavaSE has never shipped an Ant task implementation, so we are
- just following that tradition. There's an (process-wise) overhead of
- adding additional dependencies during the JavaSE build, and there
- would likely be some runtime dependency issues in having a class in
- <literal>tools.jar</literal> that would require the ant classes, due to
- class loader delegation.</para>
-
- <para>We are thinking about perhaps releasing a small jar that only
- contains the ant task for JDK6.</para>
-
- <para>Please also note that the syntax of <literal><xjc></literal> task is neither
- defined in the JAXB spec nor in the JavaSE spec. Therefore other
- JavaSE vendors may not implement that at all, or do so in a different
- class name, etc. Therefore, from a portability perspective, if you
- choose to depend on the <literal><xjc></literal> task you should bundle the JAXB
- RI.</para>
- </section>
-</section>
diff --git a/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment-runtime-errors.xml b/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment-runtime-errors.xml
deleted file mode 100644
index 8143451..0000000
--- a/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment-runtime-errors.xml
+++ /dev/null
@@ -1,87 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-
- Copyright (c) 2012, 2021 Oracle and/or its affiliates. All rights reserved.
-
- This program and the accompanying materials are made available under the
- terms of the Eclipse Distribution License v. 1.0, which is available at
- http://www.eclipse.org/org/documents/edl-v10.php.
-
- SPDX-License-Identifier: BSD-3-Clause
-
--->
-
-<!DOCTYPE book [
-<!ENTITY % ents SYSTEM "docbook.ent">
-%ents;
-]>
-<section version="5.0" xml:id="deployment-runtime-errors" xml:lang="en"
- xmlns="http://docbook.org/ns/docbook"
- xmlns:xlink="http://www.w3.org/1999/xlink"
- xmlns:ns5="http://www.w3.org/1999/xhtml"
- xmlns:ns3="http://www.w3.org/2000/svg"
- xmlns:ns="http://docbook.org/ns/docbook"
- xmlns:m="http://www.w3.org/1998/Math/MathML">
- <title>Runtime Errors</title>
-
- <section xml:id="Illegal_class_modifiers_for_package_info__0x1600">
- <title>Illegal class modifiers for package-info: 0x1600</title>
-
- <para>When you compile your sources files with JDK from Java6 and try
- to run it on Java5 JVMs, you may see a <literal>ClassFormatError</literal>
- at runtime like this:</para>
-
- <informalexample>
- <programlisting language=""><![CDATA[main" java.lang.ClassFormatError: Illegal class modifiers in class
-com/alu/parentalcontrol/jaxb/package-info: 0x1600
-at java.lang.ClassLoader.defineClass1(Native Method)
-at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
-at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
-at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
-at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
-at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
-at java.security.AccessController.doPrivileged(Native Method)
-at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
-at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
-at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
-at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
-at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
-at java.lang.Class.forName0(Native Method)
-at java.lang.Class.forName(Class.java:242)
-at java.lang.Package.getPackageInfo(Package.java:350)
-at java.lang.Package.getAnnotation(Package.java:361)
-at com.sun.xml.bind.v2.model.annotation.RuntimeInlineAnnotationReader.getPackageAnnotation(RuntimeInlineAnnotationReader.java:125)
-at com.sun.xml.bind.v2.model.annotation.RuntimeInlineAnnotationReader.getPackageAnnotation(RuntimeInlineAnnotationReader.java:53)
-at com.sun.xml.bind.v2.model.impl.TypeInfoImpl.parseElementName(TypeInfoImpl.java:122)
-at com.sun.xml.bind.v2.model.impl.ClassInfoImpl.<init>(ClassInfoImpl.java:166)]]></programlisting>
- </informalexample>
-
- <para>This is due to a bug, and so far the only way to fix this is to
- compile your project with JavaSE 5.</para>
-
- <para>Here is what's happening. Java5 added a new class file modifier
- attribute called <literal>ACC_SYNTHETIC</literal>, whose bit value is
- 0x1000. This attribute marks types and methods that are not present in
- the source file but generated by the compiler. When
- <filename>package-info.java</filename> is compiled into
- <filename>package-info.class</filename>, javac in Java5 apparently only put
- 0x0600 (= <code>ACC_ABSTRACT|ACC_INTERFACE</code>.) Some time during
- Java6 development, someone filed <link
- xlink:href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6232928">a
- bug, saying it should also include <literal>ACC_SYNTHETIC</literal>
- bit</link>, since it was a synthesized class.</para>
-
- <para>Later <link
- xlink:href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6313196">it
- is discovered that the corresponding VM change needs to be made to
- allow this 0x1600 combination</link>, but apparently no one realized
- the real implication of this --- namely, 0x1600 will break all the
- past JVMs. Of course, this problem is <link
- xlink:href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6553734">eventually
- discovered</link>, but as of this writing there's still no fix for
- this.</para>
-
- <para>So as you see, this is why the only workaround is to use javac
- from Java5.</para>
- </section>
-</section>
diff --git a/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment.xml b/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment.xml
index 765d769..f77d9fe 100644
--- a/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment.xml
+++ b/jaxb-ri/docs/release-documentation/src/docbook/users-guide-deployment.xml
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
- Copyright (c) 2010, 2021 Oracle and/or its affiliates. All rights reserved.
+ Copyright (c) 2010, 2022 Oracle and/or its affiliates. All rights reserved.
This program and the accompanying materials are made available under the
terms of the Eclipse Distribution License v. 1.0, which is available at
@@ -28,8 +28,6 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users-guide-deployment-maven-coordinates.xml" />
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users-guide-deployment-jaxb-on-jpms.xml" />
-<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users-guide-deployment-migrating-jaxb-2-0-applications-to-javase-6.xml" />-->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users-guide-deployment-which-jaxb-ri-is-included-in-which-jdk.xml" />
-<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users-guide-deployment-runtime-errors.xml" />-->
</section>
