to where? a new branch or trunk?
> On Jan 11, 2024, at 10:40 AM, Thomas Andraschko <andraschko.tho...@gmail.com>
> wrote:
>
> i applied your suggestions
>
> Am Mo., 8. Jan. 2024 um 13:19 Uhr schrieb Thomas Andraschko <
> andraschko.tho...@gmail.com>:
>
>> yep
>> that would be great
>>
>> i will also come back this month as we migrating our company applications
>> to jakarta and we also depend on DS.
>>
>> Am So., 7. Jan. 2024 um 18:25 Uhr schrieb Arnold Morein
>> <arnie.mor...@mac.com.invalid>:
>>
>>> oh, a pull request. ok.
>>>
>>>> On Jan 7, 2024, at 10:40 AM, Arnold Morein <arnie.mor...@mac.com.INVALID>
>>> wrote:
>>>>
>>>> I know that not all of javax was renamed to jakarta, but several of
>>> these would appear to be incorrect and need to be updated.
>>>>
>>>>
>>>> /**
>>>> * These config keys will get used to detect the ProjectStage.
>>>> * We iterate through them until we find the first non-empty value.
>>>> */
>>>> public static final String[] CONFIG_SETTING_KEYS =
>>>> {
>>>> //TODO discuss it
>>>> "org.apache.deltaspike.ProjectStage",
>>>> "javax.faces.PROJECT_STAGE",
>>>> "faces.PROJECT_STAGE"
>>>> };
>>>>
>>>> in ProjectStageProducer.
>>>>
>>>> and:
>>>>
>>>> /** Fetch graph. */
>>>> FETCH("javax.persistence.fetchgraph"),
>>>>
>>>> /** Load graph. */
>>>> LOAD("javax.persistence.loadgraph");
>>>>
>>>>
>>>> in EntityGraphType.
>>>>
>>>> and:
>>>>
>>>> Class<? extends Annotation> priorityAnnotationClass =
>>>>
>>> ClassUtils.tryToLoadClassForName("javax.annotation.Priority");
>>>>
>>>> in public abstract class AnnotationInstanceUtils. Which oddly enough,
>>> is right above:
>>>>
>>>> //check for @Priority and CDI v1.1+
>>>> if (priorityAnnotationClass != null &&
>>>>
>>> ClassUtils.tryToLoadClassForName("jakarta.enterprise.inject.spi.AfterTypeDiscovery")
>>> != null)
>>>>
>>>> and:
>>>>
>>>> // add spec expected attributes
>>>> unitProperties.put("javax.persistence.bean.manager",
>>> BeanManagerProvider.getInstance().getBeanManager());
>>>>
>>>> in
>>>>
>>>> @ApplicationScoped
>>>> public class PersistenceConfigurationProviderImpl implements
>>> PersistenceConfigurationProvider
>>>>
>>>>
>>>> and:
>>>>
>>>> if (interfaceClass.getName().startsWith("java.") ||
>>> interfaceClass.getName().startsWith("javax."))
>>>> {
>>>> continue;
>>>> }
>>>>
>>>> in
>>>>
>>>> PartialBeanBindingExtension#createPartialProducersDefinedIn
>>>>
>>>> and:
>>>>
>>>> annotationName = annotation.annotationType().getName();
>>>> if (annotationName.startsWith("java.") ||
>>> annotationName.startsWith("javax."))
>>>>
>>>> in SecurityUtils#getAllAnnotations
>>>>
>>>>
>>>>
>>>>> On Jan 4, 2024, at 8:14 AM, Arnold Morein <arnie.mor...@mac.com.INVALID>
>>> wrote:
>>>>>
>>>>> Could some one clarify this error message?
>>>>>
>>>>> It looks like DS is responding to a boot up event and checking for a
>>> configuration provider and not finding one.
>>>>>
>>>>> I read that section and no where does it say that the use of the
>>> configuration subsystem is required. I certainly do not have need of it at
>>> this time.
>>>>>
>>>>> Does DS need some like of default provider? I created one and it
>>> didn’t notice it. I created a configuration source (with and without the
>>> annotation) and it wasn’t noticed either.
>>>>>
>>>>> What concept am I missing here?
>>>>>
>>>>>> On Dec 28, 2023, at 7:40 PM, Arnold Morein <arnie.mor...@mac.com>
>>> wrote:
>>>>>>
>>>>>> I had to tweak a few of the POM files to get the build to work
>>> locally with OpenJDK 19.0.1 but done.
>>>>>>
>>>>>> During deployment of my WAR (from EAR) I’m getting:
>>>>>>
>>>>>> java.lang.RuntimeException: Could not load ConfigProvider
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.api.config.ConfigResolver.getConfigProvider(ConfigResolver.java:670)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.api.config.ConfigResolver.getPropertyValue(ConfigResolver.java:167)
>>>>>>
>>>>>> Even after creating a class that implements ConfigSource with the
>>> @Source annotation attached (and then ConfigSourceProvider thinking I’d try
>>> that).
>>>>>>
>>>>>> Then I removed the annotation and created the
>>> war/META-INF/services/org.apache.deltaspike.core.spi.config.ConfigSource
>>> file with the related class name.
>>>>>>
>>>>>> And still the ConfigResolver#getConfigProvider method does not see it.
>>>>>>
>>>>>> ALSO: my ear-subdeployments-isolated setting is FALSE.
>>>>>>
>>>>>> All the deltaspike jars are in my WEB-INF/lib and its functionality
>>> will be (at least for now) consumed just from the WAR module.
>>>>>>
>>>>>> I do not understand what is happening here. I wonder if CDI is
>>> reacting to an extension set up event BEFORE the class path has had a
>>> chance to scan the WAR /classes folder?
>>>>>>
>>>>>>
>>>>>> java.lang.RuntimeException: Could not load ConfigProvider
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.api.config.ConfigResolver.getConfigProvider(ConfigResolver.java:670)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.api.config.ConfigResolver.getPropertyValue(ConfigResolver.java:167)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.util.ProjectStageProducer.resolveProjectStage(ProjectStageProducer.java:151)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.util.ProjectStageProducer.initProjectStage(ProjectStageProducer.java:170)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.util.ProjectStageProducer.lazyInit(ProjectStageProducer.java:138)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.util.ProjectStageProducer.getInstance(ProjectStageProducer.java:118)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.util.ClassDeactivationUtils.performProjectStageDependentCleanup(ClassDeactivationUtils.java:100)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.util.ClassDeactivationUtils.isActivated(ClassDeactivationUtils.java:84)
>>>>>> at
>>> deployment.pirt-1.0.0.ear.pirt.war//org.apache.deltaspike.core.impl.jmx.MBeanExtension.init(MBeanExtension.java:61)
>>>>>> at
>>> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
>>>>>> at java.base/java.lang.reflect.Method.invoke(Method.java:578)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:168)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:126)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
>>>>>> at
>>> jakarta.enterprise.api//jakarta.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:142)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.util.Observers.notify(Observers.java:166)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:45)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:54)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:404)
>>>>>> at org.jboss.weld.core@5.1.1.SP1
>>> //org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:80)
>>>>>> at org.jboss.as.weld@29.0.0.Final
>>> //org.jboss.as.weld.WeldStartService.start(WeldStartService.java:96)
>>>>>> at org.jboss.msc@1.5.1.Final
>>> //org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1617)
>>>>>> at org.jboss.msc@1.5.1.Final
>>> //org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1580)
>>>>>> at org.jboss.msc@1.5.1.Final
>>> //org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1438)
>>>>>> at org.jboss.threads@2.4.0.Final
>>> //org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
>>>>>> at org.jboss.threads@2.4.0.Final
>>> //org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
>>>>>> at org.jboss.threads@2.4.0.Final
>>> //org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
>>>>>> at org.jboss.threads@2.4.0.Final
>>> //org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
>>>>>> at java.base/java.lang.Thread.run(Thread.java:1589)
>>>>>>
>>>>>
>>>>
>>>
>>>
