Re: JAXBContext - JDK 11
It looks like jaxb is already included in connector-common. These are the versions downloaded: Karl On Tue, Dec 5, 2023 at 10:18 AM Karl Wright wrote: > And Uwe: you also would need to add it to connector-build.xml. > Karl > > > On Tue, Dec 5, 2023 at 10:03 AM Karl Wright wrote: > >> Have a look at the list of dependencies in framework/build.xml for >> various contexts. I believe jaxb-api is there already but possibly not >> jaxb-impl. The fix would then be to add jaxb-impl to every place we see >> jaxb-api in that file. Also, the download for jaxb is in the main >> build.xml and it would have to include that jar as well. >> >> I'll look into this when I get done work. >> >> Karl >> >> >> On Tue, Dec 5, 2023 at 6:11 AM Piergiorgio Lucidi >> wrote: >> >>> Hi Uwe, >>> >>> Thank you for sharing this issue and I think that the jaxb library is >>> needed to solve this problem. >>> I didn't tested it yet but probably adding these dependencies should >>> solve >>> it: >>> >>>- jaxb-core:2.3.1 >>>- jaxb-api:2.3.1 >>>- jaxb-impl:2.3.1 >>> >>> I'm going to replicate the issue and raise a ticket on Jira about this. >>> Thank you again and hope this helps ;) >>> >>> Cheers, >>> PG >>> >>> >>> >>> >>> >>> Il giorno mar 5 dic 2023 alle ore 11:55 Wolfinger Uwe < >>> uwe.wolfin...@oegk.at> >>> ha scritto: >>> >>> > When trying to use the Generic Authority Connector >>> > >>> (org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority) we >>> > experienced some problems: >>> > >>> > Line 681 (context = JAXBContext.newInstance(Auth.class);) results in an >>> > error: >>> > >>> > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been >>> > found on module path or classpath. >>> > - with linked exception: >>> > [java.lang.ClassNotFoundException: >>> > com.sun.xml.internal.bind.v2.ContextFactory] >>> > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been >>> > found on module path or classpath. >>> > - with linked exception: >>> > [java.lang.ClassNotFoundException: >>> > com.sun.xml.internal.bind.v2.ContextFactory] >>> > at >>> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232) >>> > at javax.xml.bind.ContextFinder.find(ContextFinder.java:375) >>> > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691) >>> > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632) >>> > at >>> > >>> org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority$FetchTokensThread.run(GenericAuthority.java:717) >>> > Caused by: java.lang.ClassNotFoundException: >>> > com.sun.xml.internal.bind.v2.ContextFactory >>> > at >>> > >>> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) >>> > at >>> > >>> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) >>> > at >>> > >>> javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:92) >>> > at >>> > >>> javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:125) >>> > at >>> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:230) >>> > ... 4 more >>> > >>> > We are using JDK 11 as our runtime envirnoment. As far as i understood, >>> > support for jaxb was removed in JDK 11. So my question is, does anybody >>> > know a workaround for this problem (adding jaxb libs manually?) or are >>> > there any plans to upgrade the GenericAuthority Connector to JDK 11 >>> > (jakarta.xml.bind). >>> > >>> > Kind Regards, >>> > Uwe >>> > >>> >>> >>> -- >>> Piergiorgio >>> >>
Re: JAXBContext - JDK 11
And Uwe: you also would need to add it to connector-build.xml. Karl On Tue, Dec 5, 2023 at 10:03 AM Karl Wright wrote: > Have a look at the list of dependencies in framework/build.xml for various > contexts. I believe jaxb-api is there already but possibly not jaxb-impl. > The fix would then be to add jaxb-impl to every place we see jaxb-api in > that file. Also, the download for jaxb is in the main build.xml and it > would have to include that jar as well. > > I'll look into this when I get done work. > > Karl > > > On Tue, Dec 5, 2023 at 6:11 AM Piergiorgio Lucidi > wrote: > >> Hi Uwe, >> >> Thank you for sharing this issue and I think that the jaxb library is >> needed to solve this problem. >> I didn't tested it yet but probably adding these dependencies should solve >> it: >> >>- jaxb-core:2.3.1 >>- jaxb-api:2.3.1 >>- jaxb-impl:2.3.1 >> >> I'm going to replicate the issue and raise a ticket on Jira about this. >> Thank you again and hope this helps ;) >> >> Cheers, >> PG >> >> >> >> >> >> Il giorno mar 5 dic 2023 alle ore 11:55 Wolfinger Uwe < >> uwe.wolfin...@oegk.at> >> ha scritto: >> >> > When trying to use the Generic Authority Connector >> > >> (org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority) we >> > experienced some problems: >> > >> > Line 681 (context = JAXBContext.newInstance(Auth.class);) results in an >> > error: >> > >> > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been >> > found on module path or classpath. >> > - with linked exception: >> > [java.lang.ClassNotFoundException: >> > com.sun.xml.internal.bind.v2.ContextFactory] >> > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been >> > found on module path or classpath. >> > - with linked exception: >> > [java.lang.ClassNotFoundException: >> > com.sun.xml.internal.bind.v2.ContextFactory] >> > at >> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232) >> > at javax.xml.bind.ContextFinder.find(ContextFinder.java:375) >> > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691) >> > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632) >> > at >> > >> org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority$FetchTokensThread.run(GenericAuthority.java:717) >> > Caused by: java.lang.ClassNotFoundException: >> > com.sun.xml.internal.bind.v2.ContextFactory >> > at >> > >> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) >> > at >> > >> org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) >> > at >> > >> javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:92) >> > at >> > >> javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:125) >> > at >> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:230) >> > ... 4 more >> > >> > We are using JDK 11 as our runtime envirnoment. As far as i understood, >> > support for jaxb was removed in JDK 11. So my question is, does anybody >> > know a workaround for this problem (adding jaxb libs manually?) or are >> > there any plans to upgrade the GenericAuthority Connector to JDK 11 >> > (jakarta.xml.bind). >> > >> > Kind Regards, >> > Uwe >> > >> >> >> -- >> Piergiorgio >> >
Re: JAXBContext - JDK 11
Have a look at the list of dependencies in framework/build.xml for various contexts. I believe jaxb-api is there already but possibly not jaxb-impl. The fix would then be to add jaxb-impl to every place we see jaxb-api in that file. Also, the download for jaxb is in the main build.xml and it would have to include that jar as well. I'll look into this when I get done work. Karl On Tue, Dec 5, 2023 at 6:11 AM Piergiorgio Lucidi wrote: > Hi Uwe, > > Thank you for sharing this issue and I think that the jaxb library is > needed to solve this problem. > I didn't tested it yet but probably adding these dependencies should solve > it: > >- jaxb-core:2.3.1 >- jaxb-api:2.3.1 >- jaxb-impl:2.3.1 > > I'm going to replicate the issue and raise a ticket on Jira about this. > Thank you again and hope this helps ;) > > Cheers, > PG > > > > > > Il giorno mar 5 dic 2023 alle ore 11:55 Wolfinger Uwe < > uwe.wolfin...@oegk.at> > ha scritto: > > > When trying to use the Generic Authority Connector > > (org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority) > we > > experienced some problems: > > > > Line 681 (context = JAXBContext.newInstance(Auth.class);) results in an > > error: > > > > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been > > found on module path or classpath. > > - with linked exception: > > [java.lang.ClassNotFoundException: > > com.sun.xml.internal.bind.v2.ContextFactory] > > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been > > found on module path or classpath. > > - with linked exception: > > [java.lang.ClassNotFoundException: > > com.sun.xml.internal.bind.v2.ContextFactory] > > at > javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232) > > at javax.xml.bind.ContextFinder.find(ContextFinder.java:375) > > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691) > > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632) > > at > > > org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority$FetchTokensThread.run(GenericAuthority.java:717) > > Caused by: java.lang.ClassNotFoundException: > > com.sun.xml.internal.bind.v2.ContextFactory > > at > > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) > > at > > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) > > at > > > javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:92) > > at > > > javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:125) > > at > javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:230) > > ... 4 more > > > > We are using JDK 11 as our runtime envirnoment. As far as i understood, > > support for jaxb was removed in JDK 11. So my question is, does anybody > > know a workaround for this problem (adding jaxb libs manually?) or are > > there any plans to upgrade the GenericAuthority Connector to JDK 11 > > (jakarta.xml.bind). > > > > Kind Regards, > > Uwe > > > > > -- > Piergiorgio >
AW: JAXBContext - JDK 11
Hi Piergiorgio! Thank you for your reply. Actually it tried adding these jars to /connector-lib-proprietary/, unfortunately with no effect - or do i have to add them to a different location? Kind Regards, Uwe -Ursprüngliche Nachricht- Von: Piergiorgio Lucidi Gesendet: Dienstag, 5. Dezember 2023 12:11 An: dev@manifoldcf.apache.org Betreff: Re: JAXBContext - JDK 11 Hi Uwe, Thank you for sharing this issue and I think that the jaxb library is needed to solve this problem. I didn't tested it yet but probably adding these dependencies should solve it: - jaxb-core:2.3.1 - jaxb-api:2.3.1 - jaxb-impl:2.3.1 I'm going to replicate the issue and raise a ticket on Jira about this. Thank you again and hope this helps ;) Cheers, PG Il giorno mar 5 dic 2023 alle ore 11:55 Wolfinger Uwe ha scritto: > When trying to use the Generic Authority Connector > (org.apache.manifoldcf.authorities.authorities.generic.GenericAuthorit > y) we experienced some problems: > > Line 681 (context = JAXBContext.newInstance(Auth.class);) results in > an > error: > > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been > found on module path or classpath. > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory] > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been > found on module path or classpath. > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232) > at javax.xml.bind.ContextFinder.find(ContextFinder.java:375) > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691) > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632) > at > org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority > $FetchTokensThread.run(GenericAuthority.java:717) > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) > at > javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:92) > at > javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:125) > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:230) > ... 4 more > > We are using JDK 11 as our runtime envirnoment. As far as i > understood, support for jaxb was removed in JDK 11. So my question is, > does anybody know a workaround for this problem (adding jaxb libs > manually?) or are there any plans to upgrade the GenericAuthority > Connector to JDK 11 (jakarta.xml.bind). > > Kind Regards, > Uwe > -- Piergiorgio
Re: JAXBContext - JDK 11
Hi Uwe, Thank you for sharing this issue and I think that the jaxb library is needed to solve this problem. I didn't tested it yet but probably adding these dependencies should solve it: - jaxb-core:2.3.1 - jaxb-api:2.3.1 - jaxb-impl:2.3.1 I'm going to replicate the issue and raise a ticket on Jira about this. Thank you again and hope this helps ;) Cheers, PG Il giorno mar 5 dic 2023 alle ore 11:55 Wolfinger Uwe ha scritto: > When trying to use the Generic Authority Connector > (org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority) we > experienced some problems: > > Line 681 (context = JAXBContext.newInstance(Auth.class);) results in an > error: > > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been > found on module path or classpath. > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory] > javax.xml.bind.JAXBException: Implementation of JAXB-API has not been > found on module path or classpath. > - with linked exception: > [java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory] > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232) > at javax.xml.bind.ContextFinder.find(ContextFinder.java:375) > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691) > at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632) > at > org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority$FetchTokensThread.run(GenericAuthority.java:717) > Caused by: java.lang.ClassNotFoundException: > com.sun.xml.internal.bind.v2.ContextFactory > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) > at > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) > at > javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:92) > at > javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:125) > at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:230) > ... 4 more > > We are using JDK 11 as our runtime envirnoment. As far as i understood, > support for jaxb was removed in JDK 11. So my question is, does anybody > know a workaround for this problem (adding jaxb libs manually?) or are > there any plans to upgrade the GenericAuthority Connector to JDK 11 > (jakarta.xml.bind). > > Kind Regards, > Uwe > -- Piergiorgio
JAXBContext - JDK 11
When trying to use the Generic Authority Connector (org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority) we experienced some problems: Line 681 (context = JAXBContext.newInstance(Auth.class);) results in an error: javax.xml.bind.JAXBException: Implementation of JAXB-API has not been found on module path or classpath. - with linked exception: [java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory] javax.xml.bind.JAXBException: Implementation of JAXB-API has not been found on module path or classpath. - with linked exception: [java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory] at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:232) at javax.xml.bind.ContextFinder.find(ContextFinder.java:375) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632) at org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority$FetchTokensThread.run(GenericAuthority.java:717) Caused by: java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1412) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) at javax.xml.bind.ServiceLoaderUtil.nullSafeLoadClass(ServiceLoaderUtil.java:92) at javax.xml.bind.ServiceLoaderUtil.safeLoadClass(ServiceLoaderUtil.java:125) at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:230) ... 4 more We are using JDK 11 as our runtime envirnoment. As far as i understood, support for jaxb was removed in JDK 11. So my question is, does anybody know a workaround for this problem (adding jaxb libs manually?) or are there any plans to upgrade the GenericAuthority Connector to JDK 11 (jakarta.xml.bind). Kind Regards, Uwe
Re: JDK 11
Thanks for the comment. OpenJDK, though, has also changed. It always has been released from a fork of the same java that goes into the Oracle releases. While it might be maintained by a different bunch of people, strategic decisions made by Oracle also impact OpenJDK and, under the license terms, I cannot imagine the situation changing. Karl On Sat, Dec 12, 2020 at 7:20 AM Piergiorgio Lucidi wrote: > Hi Karl, > > I think that we should consider only OpenJDK edition of JDK 11 without > considering the Oracle version. > > Probably we could be lucky with OpenJDK, anyway we have to go in deep also > with OpenJDK investing more time on this. > > Hope to find some time soon to understand more details for this porting > task to do :-P > > PJ > > Il Sab 12 Dic 2020, 13:01 Karl Wright ha scritto: > > > Hi, > > > > Whereas I was under the impression that one of our committers had > addressed > > the JDK 11 problem in ManifoldCF, upon detailed inspection and trial I > have > > determined that this is in fact quite false. The reason is that the > > relatively new csws connector used a ton of J2EE classes that are no > longer > > bundled with JDK 11. > > > > I've managed to get this to build now, while adding a number of these > > classes to the appropriate classpaths in connector-build.xml, but here's > > the problem: unless somebody actually tries this connector, and uses it > > under JDK 11 in a Livelink environment, I have no idea what classes may > be > > missing at runtime. So I am hoping we have a committer somewhere who > might > > be able to work with me on this experiment. > > > > There's more news, and it isn't good: Oracle has deprecated some > ubiquitous > > methods and some techniques that many open-source projects we depend on > > use. For example, new Long(long) is going away. I have no idea why they > > did this but they must know it will effectively deprecate 100% of the > Java > > codebase that is lightly maintained, and force massive rework of pretty > > near all opensource code. That MUST be intentional on Oracle's part, and > > to me it represents the writing on the wall concerning the lifetime of > > legacy ManifoldCF connectors. It will likely not be possible to support > > our existing connector family when this happens. > > > > Meanwhile, we still need to go through the JDK 11 deprecations in our own > > codebase and fix those, as well as verify proper function of all > connectors > > on JDK 11. I'll be tackling that project myself in my voluminous spare > > time. > > > > Karl > > >
Re: JDK 11
Hi Karl, I think that we should consider only OpenJDK edition of JDK 11 without considering the Oracle version. Probably we could be lucky with OpenJDK, anyway we have to go in deep also with OpenJDK investing more time on this. Hope to find some time soon to understand more details for this porting task to do :-P PJ Il Sab 12 Dic 2020, 13:01 Karl Wright ha scritto: > Hi, > > Whereas I was under the impression that one of our committers had addressed > the JDK 11 problem in ManifoldCF, upon detailed inspection and trial I have > determined that this is in fact quite false. The reason is that the > relatively new csws connector used a ton of J2EE classes that are no longer > bundled with JDK 11. > > I've managed to get this to build now, while adding a number of these > classes to the appropriate classpaths in connector-build.xml, but here's > the problem: unless somebody actually tries this connector, and uses it > under JDK 11 in a Livelink environment, I have no idea what classes may be > missing at runtime. So I am hoping we have a committer somewhere who might > be able to work with me on this experiment. > > There's more news, and it isn't good: Oracle has deprecated some ubiquitous > methods and some techniques that many open-source projects we depend on > use. For example, new Long(long) is going away. I have no idea why they > did this but they must know it will effectively deprecate 100% of the Java > codebase that is lightly maintained, and force massive rework of pretty > near all opensource code. That MUST be intentional on Oracle's part, and > to me it represents the writing on the wall concerning the lifetime of > legacy ManifoldCF connectors. It will likely not be possible to support > our existing connector family when this happens. > > Meanwhile, we still need to go through the JDK 11 deprecations in our own > codebase and fix those, as well as verify proper function of all connectors > on JDK 11. I'll be tackling that project myself in my voluminous spare > time. > > Karl >
JDK 11
Hi, Whereas I was under the impression that one of our committers had addressed the JDK 11 problem in ManifoldCF, upon detailed inspection and trial I have determined that this is in fact quite false. The reason is that the relatively new csws connector used a ton of J2EE classes that are no longer bundled with JDK 11. I've managed to get this to build now, while adding a number of these classes to the appropriate classpaths in connector-build.xml, but here's the problem: unless somebody actually tries this connector, and uses it under JDK 11 in a Livelink environment, I have no idea what classes may be missing at runtime. So I am hoping we have a committer somewhere who might be able to work with me on this experiment. There's more news, and it isn't good: Oracle has deprecated some ubiquitous methods and some techniques that many open-source projects we depend on use. For example, new Long(long) is going away. I have no idea why they did this but they must know it will effectively deprecate 100% of the Java codebase that is lightly maintained, and force massive rework of pretty near all opensource code. That MUST be intentional on Oracle's part, and to me it represents the writing on the wall concerning the lifetime of legacy ManifoldCF connectors. It will likely not be possible to support our existing connector family when this happens. Meanwhile, we still need to go through the JDK 11 deprecations in our own codebase and fix those, as well as verify proper function of all connectors on JDK 11. I'll be tackling that project myself in my voluminous spare time. Karl
[jira] [Resolved] (CONNECTORS-1646) Notification Connector JDK > 11
[ https://issues.apache.org/jira/browse/CONNECTORS-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-1646. - Fix Version/s: ManifoldCF 2.17 Resolution: Fixed r1879219 > Notification Connector JDK > 11 > --- > > Key: CONNECTORS-1646 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1646 > Project: ManifoldCF > Issue Type: Bug > Components: Email connector >Affects Versions: ManifoldCF 2.16 >Reporter: Uwe Wolfinger >Assignee: Karl Wright >Priority: Major > Fix For: ManifoldCF 2.17 > > > When running MCF with a JDK >=11 there is a problem with the Email > notification connector. Whenever it tries to send a mail, following error is > tossed: > FATAL 2020-06-25T14:58:43,097 (Job reset thread) - Error tossed: > javax/activation/DataSource > java.lang.NoClassDefFoundError: javax/activation/DataSource > at > org.apache.manifoldcf.crawler.notifications.email.EmailSession.send(EmailSession.java:95) > ~[?:?] > at > org.apache.manifoldcf.crawler.notifications.email.EmailConnector$SendThread.run(EmailConnector.java:963) > ~[?:?] > Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) > ~[?:?] > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > ~[?:?] > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?] > ... 2 more > > this is because the activation jars are no longer part of the jdk: > [https://docs.oracle.com/en/java/javase/11/migrate/index.html#JSMIG-GUID-561005C1-12BB-455C-AD41-00455CAD23A6] > verified solution is to put > javax.activation-1.2.0.jar > and > javax.activation-api-1.2.0.jar > in the lib directory and add them to cp in jetty-options.env... and > options.env... > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CONNECTORS-1646) Notification Connector JDK > 11
[ https://issues.apache.org/jira/browse/CONNECTORS-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145994#comment-17145994 ] Uwe Wolfinger commented on CONNECTORS-1646: --- unfortunately this will not work. i tried putting the jars in connector-common-lib, lib-proprietary,... but with no success. only when you put them on the classpath, the email connector will work > Notification Connector JDK > 11 > --- > > Key: CONNECTORS-1646 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1646 > Project: ManifoldCF > Issue Type: Bug > Components: Email connector >Affects Versions: ManifoldCF 2.16 >Reporter: Uwe Wolfinger >Assignee: Karl Wright >Priority: Major > > When running MCF with a JDK >=11 there is a problem with the Email > notification connector. Whenever it tries to send a mail, following error is > tossed: > FATAL 2020-06-25T14:58:43,097 (Job reset thread) - Error tossed: > javax/activation/DataSource > java.lang.NoClassDefFoundError: javax/activation/DataSource > at > org.apache.manifoldcf.crawler.notifications.email.EmailSession.send(EmailSession.java:95) > ~[?:?] > at > org.apache.manifoldcf.crawler.notifications.email.EmailConnector$SendThread.run(EmailConnector.java:963) > ~[?:?] > Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) > ~[?:?] > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > ~[?:?] > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?] > ... 2 more > > this is because the activation jars are no longer part of the jdk: > [https://docs.oracle.com/en/java/javase/11/migrate/index.html#JSMIG-GUID-561005C1-12BB-455C-AD41-00455CAD23A6] > verified solution is to put > javax.activation-1.2.0.jar > and > javax.activation-api-1.2.0.jar > in the lib directory and add them to cp in jetty-options.env... and > options.env... > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CONNECTORS-1646) Notification Connector JDK > 11
[ https://issues.apache.org/jira/browse/CONNECTORS-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144988#comment-17144988 ] Karl Wright commented on CONNECTORS-1646: - Hi, Please verify that if you put these jars into the connector-common-lib folder instead (and make no changes to the *.env files) that this still works for you. > Notification Connector JDK > 11 > --- > > Key: CONNECTORS-1646 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1646 > Project: ManifoldCF > Issue Type: Bug > Components: Email connector >Affects Versions: ManifoldCF 2.16 >Reporter: Uwe Wolfinger >Assignee: Karl Wright >Priority: Major > > When running MCF with a JDK >=11 there is a problem with the Email > notification connector. Whenever it tries to send a mail, following error is > tossed: > FATAL 2020-06-25T14:58:43,097 (Job reset thread) - Error tossed: > javax/activation/DataSource > java.lang.NoClassDefFoundError: javax/activation/DataSource > at > org.apache.manifoldcf.crawler.notifications.email.EmailSession.send(EmailSession.java:95) > ~[?:?] > at > org.apache.manifoldcf.crawler.notifications.email.EmailConnector$SendThread.run(EmailConnector.java:963) > ~[?:?] > Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) > ~[?:?] > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > ~[?:?] > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?] > ... 2 more > > this is because the activation jars are no longer part of the jdk: > [https://docs.oracle.com/en/java/javase/11/migrate/index.html#JSMIG-GUID-561005C1-12BB-455C-AD41-00455CAD23A6] > verified solution is to put > javax.activation-1.2.0.jar > and > javax.activation-api-1.2.0.jar > in the lib directory and add them to cp in jetty-options.env... and > options.env... > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CONNECTORS-1646) Notification Connector JDK > 11
[ https://issues.apache.org/jira/browse/CONNECTORS-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-1646: --- Assignee: Karl Wright > Notification Connector JDK > 11 > --- > > Key: CONNECTORS-1646 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1646 > Project: ManifoldCF > Issue Type: Bug > Components: Email connector >Affects Versions: ManifoldCF 2.16 >Reporter: Uwe Wolfinger >Assignee: Karl Wright >Priority: Major > > When running MCF with a JDK >=11 there is a problem with the Email > notification connector. Whenever it tries to send a mail, following error is > tossed: > FATAL 2020-06-25T14:58:43,097 (Job reset thread) - Error tossed: > javax/activation/DataSource > java.lang.NoClassDefFoundError: javax/activation/DataSource > at > org.apache.manifoldcf.crawler.notifications.email.EmailSession.send(EmailSession.java:95) > ~[?:?] > at > org.apache.manifoldcf.crawler.notifications.email.EmailConnector$SendThread.run(EmailConnector.java:963) > ~[?:?] > Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource > at > java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) > ~[?:?] > at > java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) > ~[?:?] > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?] > ... 2 more > > this is because the activation jars are no longer part of the jdk: > [https://docs.oracle.com/en/java/javase/11/migrate/index.html#JSMIG-GUID-561005C1-12BB-455C-AD41-00455CAD23A6] > verified solution is to put > javax.activation-1.2.0.jar > and > javax.activation-api-1.2.0.jar > in the lib directory and add them to cp in jetty-options.env... and > options.env... > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CONNECTORS-1646) Notification Connector JDK > 11
Uwe Wolfinger created CONNECTORS-1646: - Summary: Notification Connector JDK > 11 Key: CONNECTORS-1646 URL: https://issues.apache.org/jira/browse/CONNECTORS-1646 Project: ManifoldCF Issue Type: Bug Components: Email connector Affects Versions: ManifoldCF 2.16 Reporter: Uwe Wolfinger When running MCF with a JDK >=11 there is a problem with the Email notification connector. Whenever it tries to send a mail, following error is tossed: FATAL 2020-06-25T14:58:43,097 (Job reset thread) - Error tossed: javax/activation/DataSource java.lang.NoClassDefFoundError: javax/activation/DataSource at org.apache.manifoldcf.crawler.notifications.email.EmailSession.send(EmailSession.java:95) ~[?:?] at org.apache.manifoldcf.crawler.notifications.email.EmailConnector$SendThread.run(EmailConnector.java:963) ~[?:?] Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) ~[?:?] at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) ~[?:?] at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?] ... 2 more this is because the activation jars are no longer part of the jdk: [https://docs.oracle.com/en/java/javase/11/migrate/index.html#JSMIG-GUID-561005C1-12BB-455C-AD41-00455CAD23A6] verified solution is to put javax.activation-1.2.0.jar and javax.activation-api-1.2.0.jar in the lib directory and add them to cp in jetty-options.env... and options.env... -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: ElasticSearch-literate volunteers needed for JDK 11 port
We can take a look. Get Outlook for iOS<https://aka.ms/o0ukef> From: Karl Wright Sent: Sunday, March 22, 2020 10:05:40 AM To: dev Subject: ElasticSearch-literate volunteers needed for JDK 11 port Hi All, The version of ElasticSearch we support apparently is incompatible with JDK 11. We therefore will need to update that connector and the associated tests as well. See: https://issues.apache.org/jira/browse/CONNECTORS-1624?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=17059835 I would ask anyone with any recent experience with ElasticSearch to please step forward and lend a hand with this exercise. Any volunteers? Thanks in advance, Karl
Re: ElasticSearch-literate volunteers needed for JDK 11 port
Hi Karl, Although I am not an Elastic-search expert, I wrote the MongoDB Connector for Apache ManifoldCF as a Google Summer of Code Student. I was mentored by Piergiorgio Lucidi. I used to refer to the elastic-search connector when I was implementing the MongoDB Output Connector. I would like to help you all with this. Irindu Nugawela. On Sun, 22 Mar 2020 at 20:36, Karl Wright wrote: > Hi All, > > The version of ElasticSearch we support apparently is incompatible with JDK > 11. We therefore will need to update that connector and the associated > tests as well. See: > > > https://issues.apache.org/jira/browse/CONNECTORS-1624?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=17059835 > > > I would ask anyone with any recent experience with ElasticSearch to please > step forward and lend a hand with this exercise. Any volunteers? > > Thanks in advance, > Karl > -- Thanks and Regards, Irindu Nugawela, Computer Engineering <http://www.ce.pdn.ac.lk/> Undergraduate, Faculty of Engineering University of Peradeniya
ElasticSearch-literate volunteers needed for JDK 11 port
Hi All, The version of ElasticSearch we support apparently is incompatible with JDK 11. We therefore will need to update that connector and the associated tests as well. See: https://issues.apache.org/jira/browse/CONNECTORS-1624?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=17059835 I would ask anyone with any recent experience with ElasticSearch to please step forward and lend a hand with this exercise. Any volunteers? Thanks in advance, Karl
Tackling JDK 11+
Hi folks, Now that 2.15 is out, it's time to think what to do about JDK 11 and after. The transition from JDK 8 to JDK 11 will require significant work and testing, because between JDK 11 *removed* many JDK classes that used to exist in JDK 8. The classes can be reincluded as specific dependencies BUT in order to know what inclusions are needed we are going to need to test every connector on JDK 11. In addition, since ManifoldCF distribution includes a complete execution environment, we will be changing the jars we include in the binary and lib distributions considerably. One option is to simply include all components and classes that are no longer part of JDK 11 but were part of JDK 8, if such a list exists. This would be the safest way to proceed, but I have no idea how long this list of jars is, and what versions of all the component jars we'd need. It would be great to use somebody else's work here if it exists. Does anyone know a full list of jars and versions that would "convert" a JDK 11 to a full JDK 8-compatible environment? Thanks in advance, Karl
