nd.JAXBContext.newInstance(JAXBContext.java:632)
>>> > at
>>> >
>>> org.apache.manifoldcf.authorities.authorities.generic.GenericAuthority$FetchTokensThread.run(GenericAuthority.java:717)
>>> > Caused by: java.lang.ClassNotFoundException:
>>
orities.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.
lina.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.ContextF
. 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
: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 qu
)
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
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, an
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
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
ion Connector JDK > 11
> ---
>
> Key: CONNECTORS-1646
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1646
> Project: ManifoldCF
> Issue Type: Bug
> Components: Email conn
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
>
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
[
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 &
Uwe Wolfinger created CONNECTORS-1646:
-
Summary: Notification Connector JDK > 11
Key: CONNECTORS-1646
URL: https://issues.apache.org/jira/browse/CONNECTORS-1646
Project: ManifoldCF
Is
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 appa
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. S
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
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
18 matches
Mail list logo
