You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@deltaspike.apache.org by Thomas Kernstock <t....@e-technologies.at> on 2023/07/12 16:36:06 UTC
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Hi Mark,
sorry, took longer than expected. Even my Applications compiled fine (in eclipse) I was not able to deploy one of them. Since I didn't know if it was a problem in my code or deployment descriptors I created a fresh "Dynamic Web Project" in eclipse and added all the deltaspike libraries plus omnifaces and primefaces.
First interesting thing is, that I see a validation problem in the faces-config " Class org.apache.deltaspike.jsf.impl.navigation.DeltaSpikeNavigationHandlerWrapper must extend the type javax.faces.application.NavigationHandler", even though I'm using the latest schemas ->
faces-config xmlns="https://jakarta.ee/xml/ns/jakartaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee https://jakarta.ee/xml/ns/jakartaee/web-facesconfig_4_0.xsd"
version="4.0">
<application>
<navigation-handler>org.apache.deltaspike.jsf.impl.navigation.DeltaSpikeNavigationHandlerWrapper</navigation-handler>
<locale-config>
<default-locale>en</default-locale>
<supported-locale>de</supported-locale>
<supported-locale>de_AT</supported-locale>
<supported-locale>de_DE</supported-locale>
</locale-config>
</application>
This could probably be an eclipse problem. But if I deploy the empty app (without the navigation-handler) I see following errors ->
2023-07-12T18:11:30.793+0200|INFORMATION: Custom config found by DeltaSpike. Name: 'META-INF/apache-deltaspike.properties', URL: 'jar:file:/C:/payara6.2023.1/glassfish/domains/domain1/eclipseApps/Test/WEB-INF/lib/deltaspike-jpa-module-impl-2.0.0-20230403.151152-1.jar!/META-INF/apache-deltaspike.properties'
2023-07-12T18:11:30.827+0200|INFORMATION: Computed the following DeltaSpike ProjectStage: Production
2023-07-12T18:11:30.890+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.core.impl.config.ConfigurationExtension.findDynamicConfigurationBeans(@Observes ProcessAnnotatedType<?>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.895+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes ProcessAnnotatedType, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.895+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.message.MessageBundleExtension.detectInterfaces(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.901+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.core.impl.interceptor.interdyn.InterDynExtension.processAnnotatedType(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.919+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.jsf.impl.config.view.ViewConfigExtension.buildViewConfigMetaDataTree(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.927+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.partialbean.impl.PartialBeanBindingExtension.findInvocationHandlerBindings(@Observes ProcessAnnotatedType<X>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.931+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.security.impl.extension.SecurityExtension.processAnnotatedType(@Observes ProcessAnnotatedType<X>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Exception during lifecycle processing
org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:285)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:141)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:515)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:501)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:476)
at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:492)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:94)
at org.glassfish.weld.WeldDeployer.processApplicationLoaded(WeldDeployer.java:582)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:437)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:344)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepare(ApplicationLifecycle.java:577)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:612)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:556)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:552)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:551)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:582)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:574)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:573)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1497)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1869)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1755)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:604)
at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:256)
at org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:150)
at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:520)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:217)
at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:174)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:153)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:196)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:88)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:246)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:178)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:118)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:96)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:51)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:510)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:82)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:83)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:101)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515)
at java.base/java.lang.Thread.run(Thread.java:833)
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Exception while loading the app
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Undeployment failed for context /Test
2023-07-12T18:11:31.564+0200|SCHWERWIEGEND: Exception while loading the app : CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
There are a couple more problems, but since I don't know if they are deltaspike related I do not elaborate them here.
liebe grüße
Thomas
-----Ursprüngliche Nachricht-----
Von: Mark Struberg <st...@yahoo.de.INVALID>
Gesendet: Donnerstag, 29. Juni 2023 17:24
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
That's great news, thank you all!
LieGrue,
strub
> Am 29.06.2023 um 10:52 schrieb Thomas Kernstock <t....@e-technologies.at>:
>
> Hi Charlee,
>
> thanx for the hint. I downloaded the Snapshot Versions for 2.0 (except the Validation is only for 1.9) and my project compiles now.
>
> @Mark: I will deploy and test my application on my server next week.
>
> Lg
> Thomas
>
>
> -----Ursprüngliche Nachricht-----
> Von: Charlee Chitsuk <ch...@gmail.com>
> Gesendet: Donnerstag, 29. Juni 2023 02:57
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> Hi Thomas,
>
> If I were you, I would prefer to use it from the snapshot repository rather than build it myself.
>
> Regarding to the Use DeltaSpike Snapshots[1], it mentions as the following:
> -
>
> 1. The `settings.xml` or in our `pom.xml`
>
> <repositories>
> <repository>
> <id>apache-snapshot-repository</id>
> <url>http://repository.apache.org/snapshots/</url>
> <releases>
> <enabled>false</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> </repositories>
>
> 2. Please take a BIG NOTE that, the
> `org.apache.deltaspike.distribution:distributions-bom` does not provide the version `2.0.0-SNAPSHOT` [2], then in our `pom.xml` will be looked like this.
>
> <properties>
> <deltaspike.version>2.0.0-SNAPSHOT</deltaspike.version>
> </properties>
>
> <dependency>
> <groupId>org.apache.deltaspike.core</groupId>
> <artifactId>deltaspike-core-api</artifactId>
> <version>${deltaspike.version}</version>
> <scope>compile</scope>
> </dependency>
>
> <dependency>
> <groupId>org.apache.deltaspike.core</groupId>
> <artifactId>deltaspike-core-impl</artifactId>
> <version>${deltaspike.version}</version>
> <scope>runtime</scope>
> </dependency>
>
> I hope this may help.
>
>
> [1] https://deltaspike.apache.org/documentation/snapshots.html
> [2]
> https://repository.apache.org/content/groups/snapshots/org/apache/delt
> aspike/distribution/distributions-bom/
>
>
> --
> Best Regards,
>
> Charlee Ch
>
>
> ในวันที่ พ. 28 มิ.ย. 2023 เวลา 23:27 Thomas Kernstock < t.kernstock@e-technologies.at> เขียนว่า:
>
>> Hi Mark,
>>
>> I checked the whole project out from the master on github (
>> https://github.com/apache/deltaspike/) and started maven with "mvn
>> clean install -PWeld -Dweld.version=3.1.9.Final > mvn-weld.log" like
>> I found it in the buildall.sh, except that -PWeld3 didn't work at all
>> (see mvn-weld3_1_9.log).
>>
>> I have to admit that I don't usually work with maven at all, so I'm
>> clearly not very fit to solve the errors mentioned in the log. It
>> seems that there are some properties missing like ${weld.el.api} but
>> I couldn't find the definition in deltaspike\parent\code\pom.xml nor
>> do I know which version I would need and where to set them.
>>
>> By the way, I'm using:
>> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
>> Maven home: D:\Java\apache-maven-3.9.3 Java version: 17.0.5, vendor:
>> Azul Systems, Inc., runtime: C:\Program
>> Files\Java\jdk17
>> Default locale: de_AT, platform encoding: Cp1252 OS name: "windows
>> 10", version: "10.0", arch: "amd64", family: "windows"
>>
>> What shall I do to build the project?
>>
>> Lg
>> Thomas
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Mark Struberg <st...@yahoo.de.INVALID>
>> Gesendet: Sonntag, 25. Juni 2023 23:51
>> An: users@deltaspike.apache.org
>> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>>
>> Hi Thomas!
>>
>> Could you do us a favour and test with the snaphot version of ds-2.0
>> to get some feedback?
>> In which case we would push forward with it soonish.
>>
>> txs and LieGrue,
>> strub
>>
>>> Am 23.06.2023 um 14:43 schrieb Thomas Kernstock <
>> t.kernstock@e-technologies.at>:
>>>
>>> Hi Guys,
>>>
>>> I tried to move my projects from Payara 5 to Payara 6 using
>>> Deltaspike
>> 1.9.4 including all Payara Libraries in the projects classpath.
>>>
>>> In one of these projects I'm using Deltaspike Repositories with
>>> @query()
>> definitions. Now eclipse shows this error ->
>>>
>>> "The type javax.persistence.LockModeType cannot be resolved. It is
>> indirectly referenced from required type
>> org.apache.deltaspike.data.api.Query"
>>>
>>> which is understandable, because instead of
>> javax.persistence.LockModeType it should reference
>> jakarta.persistence.LockModeType which is actually on the classpath.
>>>
>>> So I can't use the recent release version anymore.
>>>
>>> Looking in the sourcecode on github I found, this is already changed
>>> in
>> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/d
>> a ta/api/src/main/java/org/apache/deltaspike/data/api/Query.java
>> and found that Mark committed this and other changes towards Jakarta
>> in
>> 2021 but its not included in 1.9.6 either.
>>>
>>> Are there any plans or dates when DeltaSpike 2.0 will be released?
>>>
>>> Best regards
>>>
>>> Thomas
>>
>>
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Kernstock <t....@e-technologies.at>.
Sounds great, I will test it with my projects next week! Thanx a lot!
Thomas
-----Ursprüngliche Nachricht-----
Von: Thomas Frühbeck <t....@gmail.com>
Gesendet: Dienstag, 10. Oktober 2023 18:59
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Depending on the target server I see different options.
On OWB: build seems to be working fine, you could just take current build or build you own On Weld:
imho currently broken: MessageBundle (only relevant, if you use it - hard exception in Weld on annotated interfaces)
Data: CMT/BMT strategy management seems to have disappeared, I had to disable BMT strategy completely I just took the relevant projects and added them to my current one, changed the DS-version accordingly and everthing works (not using MessageBundle!).
Thus I am instantly ready to switch to official build when available.
Thomas
Am Di., 10. Okt. 2023 um 15:12 Uhr schrieb Thomas Kernstock <
t.kernstock@e-technologies.at>:
> Hi Thomas,
>
> thanx for the fix and the info. Does this mean that I may use the
> Version
> 2.0 now to resolve my problem or was this the fix for Thomas Frühbeck ?
>
> I'm not sure if Deltaspike 2.0 will be maintained in future - since
> you all seem to be (understandably) very busy. Does it make sense to
> remove Deltaspike from my projects (which will be a huge effort) or
> are the some release plans so that we can use it with the current JEE Versions.
>
> br
> Thomas
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Andraschko <an...@gmail.com>
> Gesendet: Donnerstag, 5. Oktober 2023 16:46
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> i fixed the OWB dependency version, maven build works fine now again.
>
> Am Do., 5. Okt. 2023 um 16:34 Uhr schrieb Thomas Kernstock <
> t.kernstock@e-technologies.at>:
>
> > Hi,
> >
> > unfortunately I have no experience with aquillian and furthermore
> > wouldn't even know where to start in deltaspike project. I guess it
> > is rather complex to try to understand everything it does. I wasn't
> > even able to build the release from the repository, because in
> > eclipse the maven project doesn't load correctly. So I'm afraid
> > working on the fix will not be possible for me too.
> >
> > Br
> > Thomas
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Thomas Andraschko <an...@gmail.com>
> > Gesendet: Donnerstag, 5. Oktober 2023 16:20
> > An: users@deltaspike.apache.org
> > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> >
> > Hi guys,
> >
> > in theory we did the most work in the master. We would just need
> > some help to re-activate our arquillian tests and fix the result.
> > I just dont have enough time, probably same as other commiters.
> >
> > So if you can work on it, it would be great.
> >
> >
> >
> > Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <
> > fruehbeck@aon.at
> > >:
> >
> > > Hi Thomas,
> > >
> > > the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> > > reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> > > redesigned? me clueless :-/ For Weld only few adaptations
> > > necessary, the one I noted below seems to be one.
> > > My build works fine for me to finally move project to jakarta.
> > >
> > > Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > > > Hi Thomas
> > > >
> > > > Do you mean me?
> > > > Just for clarification - I'm using the jar files that are
> > > > already
> > > downloadable at http://repository.apache.org/snapshots/ . I didn't
> > > change the source!
> > > > Br
> > > > Thomas
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Thomas Frühbeck <fr...@aon.at>
> > > > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > > > An: users@deltaspike.apache.org
> > > > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> > > >
> > > > Did you move the META-INF/services files to jakarta namespace?
> > > > e.g.:
> > > >
> > >
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> > > >
> > > > inject.spi.Extension
> > > > There you find:
> > > > org.apache.deltaspike.data.impl.RepositoryExtension
> > > >
> > > > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> > > >> Hi Guys,
> > > >>
> > > >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from
> > > >> April but
> > > still can't deploy my project. Still a problem with some
> > > Deltaspike
> > > Dependencies:
> > > >>
> > > >>
> > > >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9]
> > > >> [SCHWERWIEGEND]
> > > [NCLS-CORE-00026] [javax.enterprise.system.core] [tid:
> > > _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> > > 1696337747693] [levelValue: 1000] [[
> > > >> Exception during lifecycle processing
> > > >> org.glassfish.deployment.common.DeploymentException: CDI
> > > >> deployment
> > > failure:WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >> -- WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >>
> > >
> >
>
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Kernstock <t....@e-technologies.at>.
Hi again,
Sorry if I bother you, but just checked the snapshot folders at https://repository.apache.org/content/groups/snapshots/org/apache/deltaspike/
The folder dates have changed to today, but the jar Files are still from April !? Do I miss here something? These were the folders that Charlee Chitsuk suggested for download, since my build didn't work at all.
Br
Thomas
-----Ursprüngliche Nachricht-----
Von: Thomas Frühbeck <t....@gmail.com>
Gesendet: Dienstag, 10. Oktober 2023 18:59
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Depending on the target server I see different options.
On OWB: build seems to be working fine, you could just take current build or build you own On Weld:
imho currently broken: MessageBundle (only relevant, if you use it - hard exception in Weld on annotated interfaces)
Data: CMT/BMT strategy management seems to have disappeared, I had to disable BMT strategy completely I just took the relevant projects and added them to my current one, changed the DS-version accordingly and everthing works (not using MessageBundle!).
Thus I am instantly ready to switch to official build when available.
Thomas
Am Di., 10. Okt. 2023 um 15:12 Uhr schrieb Thomas Kernstock <
t.kernstock@e-technologies.at>:
> Hi Thomas,
>
> thanx for the fix and the info. Does this mean that I may use the
> Version
> 2.0 now to resolve my problem or was this the fix for Thomas Frühbeck ?
>
> I'm not sure if Deltaspike 2.0 will be maintained in future - since
> you all seem to be (understandably) very busy. Does it make sense to
> remove Deltaspike from my projects (which will be a huge effort) or
> are the some release plans so that we can use it with the current JEE Versions.
>
> br
> Thomas
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Andraschko <an...@gmail.com>
> Gesendet: Donnerstag, 5. Oktober 2023 16:46
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> i fixed the OWB dependency version, maven build works fine now again.
>
> Am Do., 5. Okt. 2023 um 16:34 Uhr schrieb Thomas Kernstock <
> t.kernstock@e-technologies.at>:
>
> > Hi,
> >
> > unfortunately I have no experience with aquillian and furthermore
> > wouldn't even know where to start in deltaspike project. I guess it
> > is rather complex to try to understand everything it does. I wasn't
> > even able to build the release from the repository, because in
> > eclipse the maven project doesn't load correctly. So I'm afraid
> > working on the fix will not be possible for me too.
> >
> > Br
> > Thomas
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Thomas Andraschko <an...@gmail.com>
> > Gesendet: Donnerstag, 5. Oktober 2023 16:20
> > An: users@deltaspike.apache.org
> > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> >
> > Hi guys,
> >
> > in theory we did the most work in the master. We would just need
> > some help to re-activate our arquillian tests and fix the result.
> > I just dont have enough time, probably same as other commiters.
> >
> > So if you can work on it, it would be great.
> >
> >
> >
> > Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <
> > fruehbeck@aon.at
> > >:
> >
> > > Hi Thomas,
> > >
> > > the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> > > reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> > > redesigned? me clueless :-/ For Weld only few adaptations
> > > necessary, the one I noted below seems to be one.
> > > My build works fine for me to finally move project to jakarta.
> > >
> > > Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > > > Hi Thomas
> > > >
> > > > Do you mean me?
> > > > Just for clarification - I'm using the jar files that are
> > > > already
> > > downloadable at http://repository.apache.org/snapshots/ . I didn't
> > > change the source!
> > > > Br
> > > > Thomas
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Thomas Frühbeck <fr...@aon.at>
> > > > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > > > An: users@deltaspike.apache.org
> > > > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> > > >
> > > > Did you move the META-INF/services files to jakarta namespace?
> > > > e.g.:
> > > >
> > >
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> > > >
> > > > inject.spi.Extension
> > > > There you find:
> > > > org.apache.deltaspike.data.impl.RepositoryExtension
> > > >
> > > > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> > > >> Hi Guys,
> > > >>
> > > >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from
> > > >> April but
> > > still can't deploy my project. Still a problem with some
> > > Deltaspike
> > > Dependencies:
> > > >>
> > > >>
> > > >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9]
> > > >> [SCHWERWIEGEND]
> > > [NCLS-CORE-00026] [javax.enterprise.system.core] [tid:
> > > _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> > > 1696337747693] [levelValue: 1000] [[
> > > >> Exception during lifecycle processing
> > > >> org.glassfish.deployment.common.DeploymentException: CDI
> > > >> deployment
> > > failure:WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >> -- WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.ext
> > > en
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >>
> > >
> >
>
Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Frühbeck <t....@gmail.com>.
Depending on the target server I see different options.
On OWB: build seems to be working fine, you could just take current build
or build you own
On Weld:
imho currently broken: MessageBundle (only relevant, if you use it -
hard exception in Weld on annotated interfaces)
Data: CMT/BMT strategy management seems to have disappeared, I had to
disable BMT strategy completely
I just took the relevant projects and added them to my current one, changed
the DS-version accordingly and everthing works (not using MessageBundle!).
Thus I am instantly ready to switch to official build when available.
Thomas
Am Di., 10. Okt. 2023 um 15:12 Uhr schrieb Thomas Kernstock <
t.kernstock@e-technologies.at>:
> Hi Thomas,
>
> thanx for the fix and the info. Does this mean that I may use the Version
> 2.0 now to resolve my problem or was this the fix for Thomas Frühbeck ?
>
> I'm not sure if Deltaspike 2.0 will be maintained in future - since you
> all seem to be (understandably) very busy. Does it make sense to remove
> Deltaspike from my projects (which will be a huge effort) or are the some
> release plans so that we can use it with the current JEE Versions.
>
> br
> Thomas
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Andraschko <an...@gmail.com>
> Gesendet: Donnerstag, 5. Oktober 2023 16:46
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> i fixed the OWB dependency version, maven build works fine now again.
>
> Am Do., 5. Okt. 2023 um 16:34 Uhr schrieb Thomas Kernstock <
> t.kernstock@e-technologies.at>:
>
> > Hi,
> >
> > unfortunately I have no experience with aquillian and furthermore
> > wouldn't even know where to start in deltaspike project. I guess it is
> > rather complex to try to understand everything it does. I wasn't even
> > able to build the release from the repository, because in eclipse the
> > maven project doesn't load correctly. So I'm afraid working on the fix
> > will not be possible for me too.
> >
> > Br
> > Thomas
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Thomas Andraschko <an...@gmail.com>
> > Gesendet: Donnerstag, 5. Oktober 2023 16:20
> > An: users@deltaspike.apache.org
> > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> >
> > Hi guys,
> >
> > in theory we did the most work in the master. We would just need some
> > help to re-activate our arquillian tests and fix the result.
> > I just dont have enough time, probably same as other commiters.
> >
> > So if you can work on it, it would be great.
> >
> >
> >
> > Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <
> > fruehbeck@aon.at
> > >:
> >
> > > Hi Thomas,
> > >
> > > the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> > > reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> > > redesigned? me clueless :-/ For Weld only few adaptations necessary,
> > > the one I noted below seems to be one.
> > > My build works fine for me to finally move project to jakarta.
> > >
> > > Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > > > Hi Thomas
> > > >
> > > > Do you mean me?
> > > > Just for clarification - I'm using the jar files that are already
> > > downloadable at http://repository.apache.org/snapshots/ . I didn't
> > > change the source!
> > > > Br
> > > > Thomas
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Thomas Frühbeck <fr...@aon.at>
> > > > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > > > An: users@deltaspike.apache.org
> > > > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> > > >
> > > > Did you move the META-INF/services files to jakarta namespace?
> > > > e.g.:
> > > >
> > >
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> > > >
> > > > inject.spi.Extension
> > > > There you find:
> > > > org.apache.deltaspike.data.impl.RepositoryExtension
> > > >
> > > > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> > > >> Hi Guys,
> > > >>
> > > >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from
> > > >> April but
> > > still can't deploy my project. Still a problem with some Deltaspike
> > > Dependencies:
> > > >>
> > > >>
> > > >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND]
> > > [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100
> > > _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> > > 1696337747693] [levelValue: 1000] [[
> > > >> Exception during lifecycle processing
> > > >> org.glassfish.deployment.common.DeploymentException: CDI
> > > >> deployment
> > > failure:WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >> -- WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >>
> > >
> >
>
Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Andraschko <an...@gmail.com>.
it means just that the build works again now and you can open it in the IDE
and try to fix (arquillian) tests.
The rough tasks are already done from the committers for 2.0, we just dont
have enough time to fix tests. Thomas F. is working on it currently.
I general many stuff of DS is already in the specs now (CDI, especially JSF
e.g.) but currently there is no alternative for Data.
I would try to check your applications if you can remove DS usages with the
new spec parts.
Am Di., 10. Okt. 2023 um 15:12 Uhr schrieb Thomas Kernstock <
t.kernstock@e-technologies.at>:
> Hi Thomas,
>
> thanx for the fix and the info. Does this mean that I may use the Version
> 2.0 now to resolve my problem or was this the fix for Thomas Frühbeck ?
>
> I'm not sure if Deltaspike 2.0 will be maintained in future - since you
> all seem to be (understandably) very busy. Does it make sense to remove
> Deltaspike from my projects (which will be a huge effort) or are the some
> release plans so that we can use it with the current JEE Versions.
>
> br
> Thomas
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Andraschko <an...@gmail.com>
> Gesendet: Donnerstag, 5. Oktober 2023 16:46
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> i fixed the OWB dependency version, maven build works fine now again.
>
> Am Do., 5. Okt. 2023 um 16:34 Uhr schrieb Thomas Kernstock <
> t.kernstock@e-technologies.at>:
>
> > Hi,
> >
> > unfortunately I have no experience with aquillian and furthermore
> > wouldn't even know where to start in deltaspike project. I guess it is
> > rather complex to try to understand everything it does. I wasn't even
> > able to build the release from the repository, because in eclipse the
> > maven project doesn't load correctly. So I'm afraid working on the fix
> > will not be possible for me too.
> >
> > Br
> > Thomas
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Thomas Andraschko <an...@gmail.com>
> > Gesendet: Donnerstag, 5. Oktober 2023 16:20
> > An: users@deltaspike.apache.org
> > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> >
> > Hi guys,
> >
> > in theory we did the most work in the master. We would just need some
> > help to re-activate our arquillian tests and fix the result.
> > I just dont have enough time, probably same as other commiters.
> >
> > So if you can work on it, it would be great.
> >
> >
> >
> > Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <
> > fruehbeck@aon.at
> > >:
> >
> > > Hi Thomas,
> > >
> > > the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> > > reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> > > redesigned? me clueless :-/ For Weld only few adaptations necessary,
> > > the one I noted below seems to be one.
> > > My build works fine for me to finally move project to jakarta.
> > >
> > > Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > > > Hi Thomas
> > > >
> > > > Do you mean me?
> > > > Just for clarification - I'm using the jar files that are already
> > > downloadable at http://repository.apache.org/snapshots/ . I didn't
> > > change the source!
> > > > Br
> > > > Thomas
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Thomas Frühbeck <fr...@aon.at>
> > > > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > > > An: users@deltaspike.apache.org
> > > > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> > > >
> > > > Did you move the META-INF/services files to jakarta namespace?
> > > > e.g.:
> > > >
> > >
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> > > >
> > > > inject.spi.Extension
> > > > There you find:
> > > > org.apache.deltaspike.data.impl.RepositoryExtension
> > > >
> > > > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> > > >> Hi Guys,
> > > >>
> > > >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from
> > > >> April but
> > > still can't deploy my project. Still a problem with some Deltaspike
> > > Dependencies:
> > > >>
> > > >>
> > > >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND]
> > > [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100
> > > _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> > > 1696337747693] [levelValue: 1000] [[
> > > >> Exception during lifecycle processing
> > > >> org.glassfish.deployment.common.DeploymentException: CDI
> > > >> deployment
> > > failure:WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >> -- WELD-001408: Unsatisfied dependencies for type
> > > RepositoryExtension with qualifiers @Default
> > > >> at injection point [BackedAnnotatedField] @Inject private
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on
> > > >> at
> > > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > > si
> > > on(RepositoryMetadataHandler.java:0)
> > > >>
> > >
> >
>
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Kernstock <t....@e-technologies.at>.
Hi Thomas,
thanx for the fix and the info. Does this mean that I may use the Version 2.0 now to resolve my problem or was this the fix for Thomas Frühbeck ?
I'm not sure if Deltaspike 2.0 will be maintained in future - since you all seem to be (understandably) very busy. Does it make sense to remove Deltaspike from my projects (which will be a huge effort) or are the some release plans so that we can use it with the current JEE Versions.
br
Thomas
-----Ursprüngliche Nachricht-----
Von: Thomas Andraschko <an...@gmail.com>
Gesendet: Donnerstag, 5. Oktober 2023 16:46
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
i fixed the OWB dependency version, maven build works fine now again.
Am Do., 5. Okt. 2023 um 16:34 Uhr schrieb Thomas Kernstock <
t.kernstock@e-technologies.at>:
> Hi,
>
> unfortunately I have no experience with aquillian and furthermore
> wouldn't even know where to start in deltaspike project. I guess it is
> rather complex to try to understand everything it does. I wasn't even
> able to build the release from the repository, because in eclipse the
> maven project doesn't load correctly. So I'm afraid working on the fix
> will not be possible for me too.
>
> Br
> Thomas
>
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Andraschko <an...@gmail.com>
> Gesendet: Donnerstag, 5. Oktober 2023 16:20
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> Hi guys,
>
> in theory we did the most work in the master. We would just need some
> help to re-activate our arquillian tests and fix the result.
> I just dont have enough time, probably same as other commiters.
>
> So if you can work on it, it would be great.
>
>
>
> Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <
> fruehbeck@aon.at
> >:
>
> > Hi Thomas,
> >
> > the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> > reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> > redesigned? me clueless :-/ For Weld only few adaptations necessary,
> > the one I noted below seems to be one.
> > My build works fine for me to finally move project to jakarta.
> >
> > Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > > Hi Thomas
> > >
> > > Do you mean me?
> > > Just for clarification - I'm using the jar files that are already
> > downloadable at http://repository.apache.org/snapshots/ . I didn't
> > change the source!
> > > Br
> > > Thomas
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Thomas Frühbeck <fr...@aon.at>
> > > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > > An: users@deltaspike.apache.org
> > > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> > >
> > > Did you move the META-INF/services files to jakarta namespace?
> > > e.g.:
> > >
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> > >
> > > inject.spi.Extension
> > > There you find:
> > > org.apache.deltaspike.data.impl.RepositoryExtension
> > >
> > > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> > >> Hi Guys,
> > >>
> > >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from
> > >> April but
> > still can't deploy my project. Still a problem with some Deltaspike
> > Dependencies:
> > >>
> > >>
> > >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND]
> > [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100
> > _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> > 1696337747693] [levelValue: 1000] [[
> > >> Exception during lifecycle processing
> > >> org.glassfish.deployment.common.DeploymentException: CDI
> > >> deployment
> > failure:WELD-001408: Unsatisfied dependencies for type
> > RepositoryExtension with qualifiers @Default
> > >> at injection point [BackedAnnotatedField] @Inject private
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > si
> > on
> > >> at
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > si
> > on(RepositoryMetadataHandler.java:0)
> > >> -- WELD-001408: Unsatisfied dependencies for type
> > RepositoryExtension with qualifiers @Default
> > >> at injection point [BackedAnnotatedField] @Inject private
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > si
> > on
> > >> at
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.exten
> > si
> > on(RepositoryMetadataHandler.java:0)
> > >>
> >
>
Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Andraschko <an...@gmail.com>.
i fixed the OWB dependency version, maven build works fine now again.
Am Do., 5. Okt. 2023 um 16:34 Uhr schrieb Thomas Kernstock <
t.kernstock@e-technologies.at>:
> Hi,
>
> unfortunately I have no experience with aquillian and furthermore
> wouldn't even know where to start in deltaspike project. I guess it is
> rather complex to try to understand everything it does. I wasn't even able
> to build the release from the repository, because in eclipse the maven
> project doesn't load correctly. So I'm afraid working on the fix will not
> be possible for me too.
>
> Br
> Thomas
>
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Andraschko <an...@gmail.com>
> Gesendet: Donnerstag, 5. Oktober 2023 16:20
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> Hi guys,
>
> in theory we did the most work in the master. We would just need some help
> to re-activate our arquillian tests and fix the result.
> I just dont have enough time, probably same as other commiters.
>
> So if you can work on it, it would be great.
>
>
>
> Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <
> fruehbeck@aon.at
> >:
>
> > Hi Thomas,
> >
> > the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> > reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> > redesigned? me clueless :-/ For Weld only few adaptations necessary,
> > the one I noted below seems to be one.
> > My build works fine for me to finally move project to jakarta.
> >
> > Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > > Hi Thomas
> > >
> > > Do you mean me?
> > > Just for clarification - I'm using the jar files that are already
> > downloadable at http://repository.apache.org/snapshots/ . I didn't
> > change the source!
> > > Br
> > > Thomas
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Thomas Frühbeck <fr...@aon.at>
> > > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > > An: users@deltaspike.apache.org
> > > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> > >
> > > Did you move the META-INF/services files to jakarta namespace?
> > > e.g.:
> > >
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> > >
> > > inject.spi.Extension
> > > There you find:
> > > org.apache.deltaspike.data.impl.RepositoryExtension
> > >
> > > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> > >> Hi Guys,
> > >>
> > >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from April
> > >> but
> > still can't deploy my project. Still a problem with some Deltaspike
> > Dependencies:
> > >>
> > >>
> > >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND]
> > [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100
> > _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> > 1696337747693] [levelValue: 1000] [[
> > >> Exception during lifecycle processing
> > >> org.glassfish.deployment.common.DeploymentException: CDI deployment
> > failure:WELD-001408: Unsatisfied dependencies for type
> > RepositoryExtension with qualifiers @Default
> > >> at injection point [BackedAnnotatedField] @Inject private
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> > on
> > >> at
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> > on(RepositoryMetadataHandler.java:0)
> > >> -- WELD-001408: Unsatisfied dependencies for type
> > RepositoryExtension with qualifiers @Default
> > >> at injection point [BackedAnnotatedField] @Inject private
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> > on
> > >> at
> > org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> > on(RepositoryMetadataHandler.java:0)
> > >>
> >
>
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Kernstock <t....@e-technologies.at>.
Hi,
unfortunately I have no experience with aquillian and furthermore wouldn't even know where to start in deltaspike project. I guess it is rather complex to try to understand everything it does. I wasn't even able to build the release from the repository, because in eclipse the maven project doesn't load correctly. So I'm afraid working on the fix will not be possible for me too.
Br
Thomas
-----Ursprüngliche Nachricht-----
Von: Thomas Andraschko <an...@gmail.com>
Gesendet: Donnerstag, 5. Oktober 2023 16:20
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Hi guys,
in theory we did the most work in the master. We would just need some help to re-activate our arquillian tests and fix the result.
I just dont have enough time, probably same as other commiters.
So if you can work on it, it would be great.
Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <fruehbeck@aon.at
>:
> Hi Thomas,
>
> the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> redesigned? me clueless :-/ For Weld only few adaptations necessary,
> the one I noted below seems to be one.
> My build works fine for me to finally move project to jakarta.
>
> Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > Hi Thomas
> >
> > Do you mean me?
> > Just for clarification - I'm using the jar files that are already
> downloadable at http://repository.apache.org/snapshots/ . I didn't
> change the source!
> > Br
> > Thomas
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Thomas Frühbeck <fr...@aon.at>
> > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > An: users@deltaspike.apache.org
> > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> >
> > Did you move the META-INF/services files to jakarta namespace?
> > e.g.:
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> >
> > inject.spi.Extension
> > There you find:
> > org.apache.deltaspike.data.impl.RepositoryExtension
> >
> > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> >> Hi Guys,
> >>
> >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from April
> >> but
> still can't deploy my project. Still a problem with some Deltaspike
> Dependencies:
> >>
> >>
> >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND]
> [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100
> _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> 1696337747693] [levelValue: 1000] [[
> >> Exception during lifecycle processing
> >> org.glassfish.deployment.common.DeploymentException: CDI deployment
> failure:WELD-001408: Unsatisfied dependencies for type
> RepositoryExtension with qualifiers @Default
> >> at injection point [BackedAnnotatedField] @Inject private
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> on
> >> at
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> on(RepositoryMetadataHandler.java:0)
> >> -- WELD-001408: Unsatisfied dependencies for type
> RepositoryExtension with qualifiers @Default
> >> at injection point [BackedAnnotatedField] @Inject private
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> on
> >> at
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extensi
> on(RepositoryMetadataHandler.java:0)
> >>
>
Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Andraschko <an...@gmail.com>.
Hi guys,
in theory we did the most work in the master. We would just need some help
to re-activate our arquillian tests and fix the result.
I just dont have enough time, probably same as other commiters.
So if you can work on it, it would be great.
Am Do., 5. Okt. 2023 um 15:57 Uhr schrieb Thomas Frühbeck <fruehbeck@aon.at
>:
> Hi Thomas,
>
> the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
> reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
> redesigned? me clueless :-/
> For Weld only few adaptations necessary, the one I noted below seems to
> be one.
> My build works fine for me to finally move project to jakarta.
>
> Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> > Hi Thomas
> >
> > Do you mean me?
> > Just for clarification - I'm using the jar files that are already
> downloadable at http://repository.apache.org/snapshots/ . I didn't change
> the source!
> > Br
> > Thomas
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Thomas Frühbeck <fr...@aon.at>
> > Gesendet: Donnerstag, 5. Oktober 2023 15:30
> > An: users@deltaspike.apache.org
> > Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
> >
> > Did you move the META-INF/services files to jakarta namespace?
> > e.g.:
> >
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
> >
> > inject.spi.Extension
> > There you find:
> > org.apache.deltaspike.data.impl.RepositoryExtension
> >
> > Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> >> Hi Guys,
> >>
> >> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from April but
> still can't deploy my project. Still a problem with some Deltaspike
> Dependencies:
> >>
> >>
> >> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND]
> [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100
> _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis:
> 1696337747693] [levelValue: 1000] [[
> >> Exception during lifecycle processing
> >> org.glassfish.deployment.common.DeploymentException: CDI deployment
> failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension
> with qualifiers @Default
> >> at injection point [BackedAnnotatedField] @Inject private
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
> >> at
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
> >> -- WELD-001408: Unsatisfied dependencies for type
> RepositoryExtension with qualifiers @Default
> >> at injection point [BackedAnnotatedField] @Inject private
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
> >> at
> org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
> >>
>
Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Frühbeck <fr...@aon.at>.
Hi Thomas,
the current HEAD (2.0.0-SNAPSHOT) doesn't work for me, for various
reasons (e.g. distinction CMT/BeanManaged strategy - seems to be
redesigned? me clueless :-/
For Weld only few adaptations necessary, the one I noted below seems to
be one.
My build works fine for me to finally move project to jakarta.
Am 05.10.23 um 15:35 schrieb Thomas Kernstock:
> Hi Thomas
>
> Do you mean me?
> Just for clarification - I'm using the jar files that are already downloadable at http://repository.apache.org/snapshots/ . I didn't change the source!
> Br
> Thomas
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Frühbeck <fr...@aon.at>
> Gesendet: Donnerstag, 5. Oktober 2023 15:30
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> Did you move the META-INF/services files to jakarta namespace?
> e.g.:
> deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
>
> inject.spi.Extension
> There you find:
> org.apache.deltaspike.data.impl.RepositoryExtension
>
> Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
>> Hi Guys,
>>
>> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from April but still can't deploy my project. Still a problem with some Deltaspike Dependencies:
>>
>>
>> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND] [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1696337747693] [levelValue: 1000] [[
>> Exception during lifecycle processing
>> org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
>> at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
>> at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
>> -- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
>> at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
>> at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
>>
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Kernstock <t....@e-technologies.at>.
Hi Thomas
Do you mean me?
Just for clarification - I'm using the jar files that are already downloadable at http://repository.apache.org/snapshots/ . I didn't change the source!
Br
Thomas
-----Ursprüngliche Nachricht-----
Von: Thomas Frühbeck <fr...@aon.at>
Gesendet: Donnerstag, 5. Oktober 2023 15:30
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Did you move the META-INF/services files to jakarta namespace?
e.g.:
deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
inject.spi.Extension
There you find:
org.apache.deltaspike.data.impl.RepositoryExtension
Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> Hi Guys,
>
> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from April but still can't deploy my project. Still a problem with some Deltaspike Dependencies:
>
>
> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND] [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1696337747693] [levelValue: 1000] [[
> Exception during lifecycle processing
> org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
> at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
> -- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
> at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
>
Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Frühbeck <fr...@aon.at>.
Did you move the META-INF/services files to jakarta namespace?
e.g.:
deltaspike/modules/data/impl/src/main/resources/META-INF/services/jakarta.enterprise.
inject.spi.Extension
There you find:
org.apache.deltaspike.data.impl.RepositoryExtension
Am 03.10.23 um 15:04 schrieb Thomas Kernstock:
> Hi Guys,
>
> Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from April but still can't deploy my project. Still a problem with some Deltaspike Dependencies:
>
>
> [2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND] [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1696337747693] [levelValue: 1000] [[
> Exception during lifecycle processing
> org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
> at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
> -- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
> at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
>
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Kernstock <t....@e-technologies.at>.
Hi Guys,
Now I'm using Payara 6.2003.9 with Deltaspike Snapshots from April but still can't deploy my project. Still a problem with some Deltaspike Dependencies:
[2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND] [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1696337747693] [levelValue: 1000] [[
Exception during lifecycle processing
org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:285)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:141)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:515)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:501)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:476)
at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:492)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:94)
at org.glassfish.weld.WeldDeployer.processApplicationLoaded(WeldDeployer.java:582)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:437)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:344)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepare(ApplicationLifecycle.java:580)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:570)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:556)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:552)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:551)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:582)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:574)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:573)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1497)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1879)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1755)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:604)
at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:256)
at org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:150)
at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:520)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:217)
at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:174)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:153)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:196)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:88)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:246)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:178)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:118)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:96)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:51)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:510)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:82)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:83)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:101)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515)
at java.base/java.lang.Thread.run(Thread.java:833)
]]
[2023-10-03T14:55:47.693+0200] [Payara 6.2023.9] [SCHWERWIEGEND] [] [javax.enterprise.system.core] [tid: _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1696337747693] [levelValue: 1000] [[
Exception while loading the app]]
[2023-10-03T14:55:47.696+0200] [Payara 6.2023.9] [SCHWERWIEGEND] [AS-WEB-GLUE-00192] [jakarta.enterprise.web] [tid: _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1696337747696] [levelValue: 1000] [[
Undeployment failed for context /jobs]]
[2023-10-03T14:55:47.709+0200] [Payara 6.2023.9] [SCHWERWIEGEND] [] [javax.enterprise.system.core] [tid: _ThreadID=100 _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1696337747709] [levelValue: 1000] [[
Exception while loading the app : CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
]]
Are there any news or workarounds on this?
Best regards
Thomas
-----Ursprüngliche Nachricht-----
Von: Thomas Kernstock <t....@e-technologies.at>
Gesendet: Mittwoch, 12. Juli 2023 18:36
An: users@deltaspike.apache.org
Betreff: AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Hi Mark,
sorry, took longer than expected. Even my Applications compiled fine (in eclipse) I was not able to deploy one of them. Since I didn't know if it was a problem in my code or deployment descriptors I created a fresh "Dynamic Web Project" in eclipse and added all the deltaspike libraries plus omnifaces and primefaces.
First interesting thing is, that I see a validation problem in the faces-config " Class org.apache.deltaspike.jsf.impl.navigation.DeltaSpikeNavigationHandlerWrapper must extend the type javax.faces.application.NavigationHandler", even though I'm using the latest schemas ->
faces-config xmlns="https://jakarta.ee/xml/ns/jakartaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee https://jakarta.ee/xml/ns/jakartaee/web-facesconfig_4_0.xsd"
version="4.0">
<application>
<navigation-handler>org.apache.deltaspike.jsf.impl.navigation.DeltaSpikeNavigationHandlerWrapper</navigation-handler>
<locale-config>
<default-locale>en</default-locale>
<supported-locale>de</supported-locale>
<supported-locale>de_AT</supported-locale>
<supported-locale>de_DE</supported-locale>
</locale-config>
</application>
This could probably be an eclipse problem. But if I deploy the empty app (without the navigation-handler) I see following errors ->
2023-07-12T18:11:30.793+0200|INFORMATION: Custom config found by DeltaSpike. Name: 'META-INF/apache-deltaspike.properties', URL: 'jar:file:/C:/payara6.2023.1/glassfish/domains/domain1/eclipseApps/Test/WEB-INF/lib/deltaspike-jpa-module-impl-2.0.0-20230403.151152-1.jar!/META-INF/apache-deltaspike.properties'
2023-07-12T18:11:30.827+0200|INFORMATION: Computed the following DeltaSpike ProjectStage: Production
2023-07-12T18:11:30.890+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.core.impl.config.ConfigurationExtension.findDynamicConfigurationBeans(@Observes ProcessAnnotatedType<?>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.895+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes ProcessAnnotatedType, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.895+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.message.MessageBundleExtension.detectInterfaces(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.901+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.core.impl.interceptor.interdyn.InterDynExtension.processAnnotatedType(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.919+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.jsf.impl.config.view.ViewConfigExtension.buildViewConfigMetaDataTree(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.927+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.partialbean.impl.PartialBeanBindingExtension.findInvocationHandlerBindings(@Observes ProcessAnnotatedType<X>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.931+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.security.impl.extension.SecurityExtension.processAnnotatedType(@Observes ProcessAnnotatedType<X>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Exception during lifecycle processing
org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:285)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:141)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:515)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:501)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:476)
at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:492)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:94)
at org.glassfish.weld.WeldDeployer.processApplicationLoaded(WeldDeployer.java:582)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:437)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:344)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepare(ApplicationLifecycle.java:577)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:612)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:556)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:552)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:551)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:582)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:574)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:573)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1497)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1869)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1755)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:604)
at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:256)
at org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:150)
at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:520)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:217)
at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:174)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:153)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:196)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:88)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:246)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:178)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:118)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:96)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:51)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:510)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:82)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:83)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:101)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515)
at java.base/java.lang.Thread.run(Thread.java:833)
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Exception while loading the app
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Undeployment failed for context /Test
2023-07-12T18:11:31.564+0200|SCHWERWIEGEND: Exception while loading the app : CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
There are a couple more problems, but since I don't know if they are deltaspike related I do not elaborate them here.
liebe grüße
Thomas
-----Ursprüngliche Nachricht-----
Von: Mark Struberg <st...@yahoo.de.INVALID>
Gesendet: Donnerstag, 29. Juni 2023 17:24
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
That's great news, thank you all!
LieGrue,
strub
> Am 29.06.2023 um 10:52 schrieb Thomas Kernstock <t....@e-technologies.at>:
>
> Hi Charlee,
>
> thanx for the hint. I downloaded the Snapshot Versions for 2.0 (except the Validation is only for 1.9) and my project compiles now.
>
> @Mark: I will deploy and test my application on my server next week.
>
> Lg
> Thomas
>
>
> -----Ursprüngliche Nachricht-----
> Von: Charlee Chitsuk <ch...@gmail.com>
> Gesendet: Donnerstag, 29. Juni 2023 02:57
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> Hi Thomas,
>
> If I were you, I would prefer to use it from the snapshot repository rather than build it myself.
>
> Regarding to the Use DeltaSpike Snapshots[1], it mentions as the following:
> -
>
> 1. The `settings.xml` or in our `pom.xml`
>
> <repositories>
> <repository>
> <id>apache-snapshot-repository</id>
> <url>http://repository.apache.org/snapshots/</url>
> <releases>
> <enabled>false</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> </repositories>
>
> 2. Please take a BIG NOTE that, the
> `org.apache.deltaspike.distribution:distributions-bom` does not provide the version `2.0.0-SNAPSHOT` [2], then in our `pom.xml` will be looked like this.
>
> <properties>
> <deltaspike.version>2.0.0-SNAPSHOT</deltaspike.version>
> </properties>
>
> <dependency>
> <groupId>org.apache.deltaspike.core</groupId>
> <artifactId>deltaspike-core-api</artifactId>
> <version>${deltaspike.version}</version>
> <scope>compile</scope>
> </dependency>
>
> <dependency>
> <groupId>org.apache.deltaspike.core</groupId>
> <artifactId>deltaspike-core-impl</artifactId>
> <version>${deltaspike.version}</version>
> <scope>runtime</scope>
> </dependency>
>
> I hope this may help.
>
>
> [1] https://deltaspike.apache.org/documentation/snapshots.html
> [2]
> https://repository.apache.org/content/groups/snapshots/org/apache/delt
> aspike/distribution/distributions-bom/
>
>
> --
> Best Regards,
>
> Charlee Ch
>
>
> ในวันที่ พ. 28 มิ.ย. 2023 เวลา 23:27 Thomas Kernstock < t.kernstock@e-technologies.at> เขียนว่า:
>
>> Hi Mark,
>>
>> I checked the whole project out from the master on github (
>> https://github.com/apache/deltaspike/) and started maven with "mvn
>> clean install -PWeld -Dweld.version=3.1.9.Final > mvn-weld.log" like
>> I found it in the buildall.sh, except that -PWeld3 didn't work at all
>> (see mvn-weld3_1_9.log).
>>
>> I have to admit that I don't usually work with maven at all, so I'm
>> clearly not very fit to solve the errors mentioned in the log. It
>> seems that there are some properties missing like ${weld.el.api} but
>> I couldn't find the definition in deltaspike\parent\code\pom.xml nor
>> do I know which version I would need and where to set them.
>>
>> By the way, I'm using:
>> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
>> Maven home: D:\Java\apache-maven-3.9.3 Java version: 17.0.5, vendor:
>> Azul Systems, Inc., runtime: C:\Program
>> Files\Java\jdk17
>> Default locale: de_AT, platform encoding: Cp1252 OS name: "windows
>> 10", version: "10.0", arch: "amd64", family: "windows"
>>
>> What shall I do to build the project?
>>
>> Lg
>> Thomas
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Mark Struberg <st...@yahoo.de.INVALID>
>> Gesendet: Sonntag, 25. Juni 2023 23:51
>> An: users@deltaspike.apache.org
>> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>>
>> Hi Thomas!
>>
>> Could you do us a favour and test with the snaphot version of ds-2.0
>> to get some feedback?
>> In which case we would push forward with it soonish.
>>
>> txs and LieGrue,
>> strub
>>
>>> Am 23.06.2023 um 14:43 schrieb Thomas Kernstock <
>> t.kernstock@e-technologies.at>:
>>>
>>> Hi Guys,
>>>
>>> I tried to move my projects from Payara 5 to Payara 6 using
>>> Deltaspike
>> 1.9.4 including all Payara Libraries in the projects classpath.
>>>
>>> In one of these projects I'm using Deltaspike Repositories with
>>> @query()
>> definitions. Now eclipse shows this error ->
>>>
>>> "The type javax.persistence.LockModeType cannot be resolved. It is
>> indirectly referenced from required type
>> org.apache.deltaspike.data.api.Query"
>>>
>>> which is understandable, because instead of
>> javax.persistence.LockModeType it should reference
>> jakarta.persistence.LockModeType which is actually on the classpath.
>>>
>>> So I can't use the recent release version anymore.
>>>
>>> Looking in the sourcecode on github I found, this is already changed
>>> in
>> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/d
>> a ta/api/src/main/java/org/apache/deltaspike/data/api/Query.java
>> and found that Mark committed this and other changes towards Jakarta
>> in
>> 2021 but its not included in 1.9.6 either.
>>>
>>> Are there any plans or dates when DeltaSpike 2.0 will be released?
>>>
>>> Best regards
>>>
>>> Thomas
>>
>>
AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Posted by Thomas Kernstock <t....@e-technologies.at>.
Servus Mark,
are there any infos about Deltaspike Version 2.0? Do you plan to create a release version sometime this year?
Liebe Grüße
Thomas
-----Ursprüngliche Nachricht-----
Von: Thomas Kernstock <t....@e-technologies.at>
Gesendet: Mittwoch, 12. Juli 2023 18:36
An: users@deltaspike.apache.org
Betreff: AW: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
Hi Mark,
sorry, took longer than expected. Even my Applications compiled fine (in eclipse) I was not able to deploy one of them. Since I didn't know if it was a problem in my code or deployment descriptors I created a fresh "Dynamic Web Project" in eclipse and added all the deltaspike libraries plus omnifaces and primefaces.
First interesting thing is, that I see a validation problem in the faces-config " Class org.apache.deltaspike.jsf.impl.navigation.DeltaSpikeNavigationHandlerWrapper must extend the type javax.faces.application.NavigationHandler", even though I'm using the latest schemas ->
faces-config xmlns="https://jakarta.ee/xml/ns/jakartaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee https://jakarta.ee/xml/ns/jakartaee/web-facesconfig_4_0.xsd"
version="4.0">
<application>
<navigation-handler>org.apache.deltaspike.jsf.impl.navigation.DeltaSpikeNavigationHandlerWrapper</navigation-handler>
<locale-config>
<default-locale>en</default-locale>
<supported-locale>de</supported-locale>
<supported-locale>de_AT</supported-locale>
<supported-locale>de_DE</supported-locale>
</locale-config>
</application>
This could probably be an eclipse problem. But if I deploy the empty app (without the navigation-handler) I see following errors ->
2023-07-12T18:11:30.793+0200|INFORMATION: Custom config found by DeltaSpike. Name: 'META-INF/apache-deltaspike.properties', URL: 'jar:file:/C:/payara6.2023.1/glassfish/domains/domain1/eclipseApps/Test/WEB-INF/lib/deltaspike-jpa-module-impl-2.0.0-20230403.151152-1.jar!/META-INF/apache-deltaspike.properties'
2023-07-12T18:11:30.827+0200|INFORMATION: Computed the following DeltaSpike ProjectStage: Production
2023-07-12T18:11:30.890+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.core.impl.config.ConfigurationExtension.findDynamicConfigurationBeans(@Observes ProcessAnnotatedType<?>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.895+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension.vetoBeans(@Observes ProcessAnnotatedType, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.895+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.core.impl.message.MessageBundleExtension.detectInterfaces(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.901+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.core.impl.interceptor.interdyn.InterDynExtension.processAnnotatedType(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.919+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] protected org.apache.deltaspike.jsf.impl.config.view.ViewConfigExtension.buildViewConfigMetaDataTree(@Observes ProcessAnnotatedType) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.927+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.partialbean.impl.PartialBeanBindingExtension.findInvocationHandlerBindings(@Observes ProcessAnnotatedType<X>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:30.931+0200|INFORMATION: WELD-000411: Observer method [BackedAnnotatedMethod] public org.apache.deltaspike.security.impl.extension.SecurityExtension.processAnnotatedType(@Observes ProcessAnnotatedType<X>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Exception during lifecycle processing
org.glassfish.deployment.common.DeploymentException: CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:285)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:141)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:515)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:501)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:476)
at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:492)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:94)
at org.glassfish.weld.WeldDeployer.processApplicationLoaded(WeldDeployer.java:582)
at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:437)
at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:344)
at com.sun.enterprise.v3.server.ApplicationLifecycle.prepare(ApplicationLifecycle.java:577)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:612)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:556)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:552)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:551)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:582)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:574)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/javax.security.auth.Subject.doAs(Subject.java:376)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:573)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1497)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1869)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1755)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:604)
at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:256)
at org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:150)
at com.sun.enterprise.v3.services.impl.ContainerMapper$HttpHandlerCallable.call(ContainerMapper.java:520)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:217)
at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:174)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:153)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:196)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:88)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:246)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:178)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:118)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:96)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:51)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:510)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:82)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:83)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:101)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:535)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:515)
at java.base/java.lang.Thread.run(Thread.java:833)
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Exception while loading the app
2023-07-12T18:11:31.552+0200|SCHWERWIEGEND: Undeployment failed for context /Test
2023-07-12T18:11:31.564+0200|SCHWERWIEGEND: Exception while loading the app : CDI deployment failure:WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
-- WELD-001408: Unsatisfied dependencies for type RepositoryExtension with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension
at org.apache.deltaspike.data.impl.meta.RepositoryMetadataHandler.extension(RepositoryMetadataHandler.java:0)
There are a couple more problems, but since I don't know if they are deltaspike related I do not elaborate them here.
liebe grüße
Thomas
-----Ursprüngliche Nachricht-----
Von: Mark Struberg <st...@yahoo.de.INVALID>
Gesendet: Donnerstag, 29. Juni 2023 17:24
An: users@deltaspike.apache.org
Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
That's great news, thank you all!
LieGrue,
strub
> Am 29.06.2023 um 10:52 schrieb Thomas Kernstock <t....@e-technologies.at>:
>
> Hi Charlee,
>
> thanx for the hint. I downloaded the Snapshot Versions for 2.0 (except the Validation is only for 1.9) and my project compiles now.
>
> @Mark: I will deploy and test my application on my server next week.
>
> Lg
> Thomas
>
>
> -----Ursprüngliche Nachricht-----
> Von: Charlee Chitsuk <ch...@gmail.com>
> Gesendet: Donnerstag, 29. Juni 2023 02:57
> An: users@deltaspike.apache.org
> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>
> Hi Thomas,
>
> If I were you, I would prefer to use it from the snapshot repository rather than build it myself.
>
> Regarding to the Use DeltaSpike Snapshots[1], it mentions as the following:
> -
>
> 1. The `settings.xml` or in our `pom.xml`
>
> <repositories>
> <repository>
> <id>apache-snapshot-repository</id>
> <url>http://repository.apache.org/snapshots/</url>
> <releases>
> <enabled>false</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> </repositories>
>
> 2. Please take a BIG NOTE that, the
> `org.apache.deltaspike.distribution:distributions-bom` does not provide the version `2.0.0-SNAPSHOT` [2], then in our `pom.xml` will be looked like this.
>
> <properties>
> <deltaspike.version>2.0.0-SNAPSHOT</deltaspike.version>
> </properties>
>
> <dependency>
> <groupId>org.apache.deltaspike.core</groupId>
> <artifactId>deltaspike-core-api</artifactId>
> <version>${deltaspike.version}</version>
> <scope>compile</scope>
> </dependency>
>
> <dependency>
> <groupId>org.apache.deltaspike.core</groupId>
> <artifactId>deltaspike-core-impl</artifactId>
> <version>${deltaspike.version}</version>
> <scope>runtime</scope>
> </dependency>
>
> I hope this may help.
>
>
> [1] https://deltaspike.apache.org/documentation/snapshots.html
> [2]
> https://repository.apache.org/content/groups/snapshots/org/apache/delt
> aspike/distribution/distributions-bom/
>
>
> --
> Best Regards,
>
> Charlee Ch
>
>
> ในวันที่ พ. 28 มิ.ย. 2023 เวลา 23:27 Thomas Kernstock < t.kernstock@e-technologies.at> เขียนว่า:
>
>> Hi Mark,
>>
>> I checked the whole project out from the master on github (
>> https://github.com/apache/deltaspike/) and started maven with "mvn
>> clean install -PWeld -Dweld.version=3.1.9.Final > mvn-weld.log" like
>> I found it in the buildall.sh, except that -PWeld3 didn't work at all
>> (see mvn-weld3_1_9.log).
>>
>> I have to admit that I don't usually work with maven at all, so I'm
>> clearly not very fit to solve the errors mentioned in the log. It
>> seems that there are some properties missing like ${weld.el.api} but
>> I couldn't find the definition in deltaspike\parent\code\pom.xml nor
>> do I know which version I would need and where to set them.
>>
>> By the way, I'm using:
>> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
>> Maven home: D:\Java\apache-maven-3.9.3 Java version: 17.0.5, vendor:
>> Azul Systems, Inc., runtime: C:\Program
>> Files\Java\jdk17
>> Default locale: de_AT, platform encoding: Cp1252 OS name: "windows
>> 10", version: "10.0", arch: "amd64", family: "windows"
>>
>> What shall I do to build the project?
>>
>> Lg
>> Thomas
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Mark Struberg <st...@yahoo.de.INVALID>
>> Gesendet: Sonntag, 25. Juni 2023 23:51
>> An: users@deltaspike.apache.org
>> Betreff: Re: Deltaspike 1.9.4 on Payara 6 not working anymore - 2.0 ?
>>
>> Hi Thomas!
>>
>> Could you do us a favour and test with the snaphot version of ds-2.0
>> to get some feedback?
>> In which case we would push forward with it soonish.
>>
>> txs and LieGrue,
>> strub
>>
>>> Am 23.06.2023 um 14:43 schrieb Thomas Kernstock <
>> t.kernstock@e-technologies.at>:
>>>
>>> Hi Guys,
>>>
>>> I tried to move my projects from Payara 5 to Payara 6 using
>>> Deltaspike
>> 1.9.4 including all Payara Libraries in the projects classpath.
>>>
>>> In one of these projects I'm using Deltaspike Repositories with
>>> @query()
>> definitions. Now eclipse shows this error ->
>>>
>>> "The type javax.persistence.LockModeType cannot be resolved. It is
>> indirectly referenced from required type
>> org.apache.deltaspike.data.api.Query"
>>>
>>> which is understandable, because instead of
>> javax.persistence.LockModeType it should reference
>> jakarta.persistence.LockModeType which is actually on the classpath.
>>>
>>> So I can't use the recent release version anymore.
>>>
>>> Looking in the sourcecode on github I found, this is already changed
>>> in
>> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/d
>> a ta/api/src/main/java/org/apache/deltaspike/data/api/Query.java
>> and found that Mark committed this and other changes towards Jakarta
>> in
>> 2021 but its not included in 1.9.6 either.
>>>
>>> Are there any plans or dates when DeltaSpike 2.0 will be released?
>>>
>>> Best regards
>>>
>>> Thomas
>>
>>