[jira] [Commented] (DELTASPIKE-1314) ContainerCtrlTckTest fails with tomee7-build-managed
[ https://issues.apache.org/jira/browse/DELTASPIKE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291951#comment-17291951 ] ASF subversion and git services commented on DELTASPIKE-1314: - Commit 3ca131009825a7ccd98a76ccc19f181e127a4d85 in deltaspike's branch refs/heads/master from Mark Struberg [ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=3ca1310 ] DELTASPIKE-1314 fix tomee7-build-managed profile no other magic setting needed anymore to make it work. > ContainerCtrlTckTest fails with tomee7-build-managed > > > Key: DELTASPIKE-1314 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1314 > Project: DeltaSpike > Issue Type: Bug >Reporter: Thomas Andraschko >Assignee: Mark Struberg >Priority: Major > > mvn clean package -Ptomee7-build-managed > [~struberg] Could you check that? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1177) [Deltaspike Data] Regoznize Entity Type by method returned type if @Repository.forEntity is set to default
[
https://issues.apache.org/jira/browse/DELTASPIKE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko closed DELTASPIKE-1177.
-
Resolution: Won't Fix
Current design is 1 entity for 1 repo only
> [Deltaspike Data] Regoznize Entity Type by method returned type if
> @Repository.forEntity is set to default
> --
>
> Key: DELTASPIKE-1177
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1177
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module
>Affects Versions: 1.7.0
>Reporter: Tibor Digana
>Priority: Major
>
> I want to use Deltaspike Data Repo as a Service because it is simplistic and
> not DAO.
> Since of service operates over multiple entities I want the extension to
> recognize the Entity type dynamically by method return type.
> Notice the example does not implement _EntityRepository_ and therefore the
> only return type should be checked.
> {code}
> @Repository
> public interface Java8Repository {
> MyEntity findByCourse(@NotNull String courseName);
> AnotherEntity findByCustomer(@NotNull String customerName);
> @Query("")
> Object[] findMultipleEntityTypes(@NotNull String attribute);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1238) Create a better default TransactionStrategy
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko closed DELTASPIKE-1238. - Resolution: Won't Fix Talked with Mark, lets close it for now. 4 years no progress > Create a better default TransactionStrategy > --- > > Key: DELTASPIKE-1238 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1238 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament >Priority: Major > Fix For: 2.0 > > > Create a better default TransactionStrategy that handles more use cases out > of the box. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1190) Add more examples
[ https://issues.apache.org/jira/browse/DELTASPIKE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko closed DELTASPIKE-1190. - Resolution: Incomplete noone provided a PR for that, lets close for now > Add more examples > - > > Key: DELTASPIKE-1190 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1190 > Project: DeltaSpike > Issue Type: Task > Components: Documentation, Examples >Reporter: John D. Ament >Priority: Major > > We've added a lot of new functionality in recent releases. It would be great > to see some new examples being added. > Current examples are found at : > https://github.com/apache/deltaspike/tree/master/deltaspike/examples > - Add examples w/ Data > - Add examples w/ JPA > - Add test control examples > - Add examples for partial bean/proxy -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-988) ViewAccessHandler API
[ https://issues.apache.org/jira/browse/DELTASPIKE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko closed DELTASPIKE-988. Resolution: Won't Fix lets close for now > ViewAccessHandler API > - > > Key: DELTASPIKE-988 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-988 > Project: DeltaSpike > Issue Type: Improvement > Components: JSF-Module >Affects Versions: 1.5.0 >Reporter: Richard DiCroce >Assignee: Gerhard Petracek >Priority: Major > > Currently, there is no way to programmatically evaluate the Secured > annotations on a ViewConfig. I have created a PR on GitHub to add such an > API. As a bonus, I also added some tests for the Secured/ViewConfig > integration. > PR is here: https://github.com/apache/deltaspike/pull/44 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1413) dsrwid cookie should not be set to sameSite="None"
[ https://issues.apache.org/jira/browse/DELTASPIKE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291681#comment-17291681 ] Thomas Andraschko commented on DELTASPIKE-1413: --- [~mwalliczek] a PR would be great > dsrwid cookie should not be set to sameSite="None" > -- > > Key: DELTASPIKE-1413 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1413 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Matthias Walliczek >Priority: Critical > > Currently the dsrwid cookie set by the lazy window handler is set to > secure=false and sameSite=None. > This combination will not be allowed by Firefox in the future. See > [https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite.|https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite] > Instead sameSite should be set to "lax", which is default in modern browsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1104) Import Microscoped scopes into DeltaSpike
[ https://issues.apache.org/jira/browse/DELTASPIKE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Andraschko closed DELTASPIKE-1104. - Resolution: Won't Fix noone requested it or worked on it, lets close for now > Import Microscoped scopes into DeltaSpike > - > > Key: DELTASPIKE-1104 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1104 > Project: DeltaSpike > Issue Type: New Feature > Components: Core, Servlet-Module, Timer-Module >Reporter: John D. Ament >Priority: Major > > Import the newly created microscoped scopes into DeltaSpike. > Some high level mappings > MethodScoped -> Core > DomainScoped -> Servlet > HeaderScoped -> Servlet > TimerScoped -> New module? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1418) BeanManagerProvider didn't implement the javax.enterprise.inject.spi.Extension interface
[
https://issues.apache.org/jira/browse/DELTASPIKE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko closed DELTASPIKE-1418.
-
Resolution: Incomplete
no feedback
> BeanManagerProvider didn't implement the
> javax.enterprise.inject.spi.Extension interface
>
>
> Key: DELTASPIKE-1418
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1418
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.8.2
> Environment: Wildfly 18.1
> Deltaspike 1.8.2
>Reporter: THEODOROS CHAIKALIS
>Assignee: Mark Struberg
>Priority: Major
>
> Iam getting a strange error during deployment:
> The scenario is: Iam trying to port the application from Weblogic 12c to
> Wildfly 18.1.
> The war deploys successfully on WL 12c
>
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException:
> WFLYWELD0021: Service class
> org.apache.deltaspike.core.api.provider.BeanManagerProvider didn't implement
> the javax.enterprise.inject.spi.Extension interface
>
>
>
> FULL ERROR STACK:
>
> {{17:39:06,999 INFO [org.jboss.as.repository] (management-handler-thread - 1)
> WFLYDR0001: Content added at location
> C:\Wildfly\wildfly-18.0.1.Final\standalone\data\content\ae\a8437df71db3a6747bc93111cc195e59d7355a\content}}
> {{17:39:07,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3)
> WFLYSRV0027: Starting deployment of "ssp.webservices.process.war"
> (runtime-name: "ssp.webservices.process.war")}}
> {{17:39:08,786 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
> Read persistence.xml for auditPU}}
> {{17:39:08,788 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
> Read persistence.xml for commonPU}}
> {{17:39:08,791 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
> Read persistence.xml for processPU}}
> {{17:39:08,797 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
> Read persistence.xml for registryPU}}
> {{17:39:08,800 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002:
> Read persistence.xml for rulesPU}}
> {{17:39:09,337 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 83)
> WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
> 'ssp.webservices.process.war#auditPU'}}
> {{17:39:09,337 INFO [org.hibernate.jpa.internal.util.LogHelper]
> (ServerService Thread Pool -- 83) HHH000204: Processing PersistenceUnitInfo
> [}}
> {{ name: auditPU}}
> {{ ...]}}
> {{17:39:09,415 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 95)
> WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
> 'ssp.webservices.process.war#registryPU'}}
> {{17:39:09,418 INFO [org.hibernate.jpa.internal.util.LogHelper]
> (ServerService Thread Pool -- 95) HHH000204: Processing PersistenceUnitInfo
> [}}
> {{ name: registryPU}}
> {{ ...]}}
> {{17:39:09,417 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 96)
> WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
> 'ssp.webservices.process.war#rulesPU'}}
> {{17:39:09,429 INFO [org.hibernate.jpa.internal.util.LogHelper]
> (ServerService Thread Pool -- 96) HHH000204: Processing PersistenceUnitInfo
> [}}
> {{ name: rulesPU}}
> {{ ...]}}
> {{17:39:09,417 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 93)
> WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
> 'ssp.webservices.process.war#processPU'}}
> {{17:39:09,438 INFO [org.hibernate.jpa.internal.util.LogHelper]
> (ServerService Thread Pool -- 93) HHH000204: Processing PersistenceUnitInfo
> [}}
> {{ name: processPU}}
> {{ ...]}}
> {{17:39:09,418 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 94)
> WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
> 'ssp.webservices.process.war#commonPU'}}
> {{17:39:09,447 INFO [org.hibernate.jpa.internal.util.LogHelper]
> (ServerService Thread Pool -- 94) HHH000204: Processing PersistenceUnitInfo
> [}}
> {{ name: commonPU}}
> {{ ...]}}
> {{17:39:09,999 INFO [org.jboss.weld.deployer] (MSC service thread 1-8)
> WFLYWELD0003: Processing weld deployment ssp.webservices.process.war}}
> {{17:39:10,122 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8)
> MSC01: Failed to start service
> jboss.deployment.unit."ssp.webservices.process.war".POST_MODULE:
> org.jboss.msc.service.StartException in service
> jboss.deployment.unit."ssp.webservices.process.war".POST_MODULE: WFLYSRV0153:
> Failed to process phase POST_MODULE of deployment
> "ssp.webservices.process.war"}}
> {{ at
> org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)}}
> {{ at
>
[jira] [Closed] (DELTASPIKE-1218) Backport CDI 2.0 Request Context Controller
[
https://issues.apache.org/jira/browse/DELTASPIKE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Andraschko closed DELTASPIKE-1218.
-
Resolution: Won't Fix
CDI 2.0 is already some years old now, lets close it.
> Backport CDI 2.0 Request Context Controller
> ---
>
> Key: DELTASPIKE-1218
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1218
> Project: DeltaSpike
> Issue Type: New Feature
> Components: CdiControl
>Reporter: John D. Ament
>Assignee: John D. Ament
>Priority: Major
>
> Backport the new features of context control to enable users to leverage the
> functionality now.
> {{@ActivateRequestContext}}
> {{RequestContextController}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1262) Remove CdiContainer control
[ https://issues.apache.org/jira/browse/DELTASPIKE-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-1262. - Resolution: Won't Fix still provides far more than CDI-2.0 can do. E.g. add container properties for the startup. > Remove CdiContainer control > --- > > Key: DELTASPIKE-1262 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1262 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Priority: Major > Fix For: 2.0 > > > The bootstrap mechanisms for CDI are present in CDI 2.0. We no longer need > this functionality. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1350) TransactionalInterceptor should use the EntityManagerResolver for lookups
[
https://issues.apache.org/jira/browse/DELTASPIKE-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-1350.
-
Resolution: Not A Problem
> TransactionalInterceptor should use the EntityManagerResolver for lookups
> -
>
> Key: DELTASPIKE-1350
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1350
> Project: DeltaSpike
> Issue Type: Improvement
> Components: JPA-Module
>Affects Versions: 1.8.2
>Reporter: Andrei Ivanov
>Priority: Major
>
> Hi,
> I'm trying to use the transaction support from the JPA module with multiple
> entity managers that are created by a producer defined in a separate/common
> module.
> That means that any specific qualifiers defined in the client modules (like
> {{@DbA}} / {{@DbB}}{{ from the examples) are not visible to the producer. To
> make this work, I've followed the approach from the
> EntityManagerFactoryProducer}} and I've defined my own qualifier,
> {{PersistenceContextName}}, duplicated from {{PersistenceUnitName}} (and
> similar to the {{CustomQualifier}} from the example).
> I've also created an {{EntityManagerResolver}} in one of the client modules
> and configured it in the DAOs inside it (which are not DeltaSpike
> repositories), with {{@Transactional}} and
> {{@EntityManagerConfig(entityManagerResolver =
> BranchManagementResolver.class, qualifier = PersistenceContextName.class)}}
> As far as I see, only the {{qualifier}} attribute is used, but it invokes my
> producer with a {{null}} {{InjectionPoint}}:
> {noformat}
> java.lang.NullPointerException: null
> at
> EntityManagerProducer.getEntityManagerFactory(EntityManagerProducer.java:109)
> ~[server-core-impl-1.0.21-SNAPSHOT.jar:?]
> at
> EntityManagerProducer.createEntityManager(EntityManagerProducer.java:95)
> ~[server-core-impl-1.0.21-SNAPSHOT.jar:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_172]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_172]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_172]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_172]
> at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:103)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:161)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:180)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.contexts.unbound.DependentContextImpl.get(DependentContextImpl.java:70)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:700)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:723)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.util.ForwardingBeanManager.getReference(ForwardingBeanManager.java:64)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:86)
> ~[weld-core-impl-3.0.4.Final.jar:3.0.4.Final]
> at
> org.apache.deltaspike.jpa.spi.entitymanager.QualifierBackedEntityManagerResolver.resolveEntityManager(QualifierBackedEntityManagerResolver.java:59)
> ~[deltaspike-jpa-module-api-1.8.2.jar:1.8.2]
> at
> org.apache.deltaspike.jpa.impl.transaction.ResourceLocalTransactionStrategy.resolveEntityManagerForQualifier(ResourceLocalTransactionStrategy.java:381)
> ~[deltaspike-jpa-module-impl-1.8.2.jar:1.8.2]
> {noformat}
> The NPE line has {{LOGGER.info(injectionPoint.getAnnotated())}}, and
> {{injectionPoint}} is null.
> Maybe this is a separate bug?
>
> If I understand this correctly, my problem would be solved if my custom
> resolver would be used for lookups, but the only reference to it is from
>
[GitHub] [deltaspike] tandraschko merged pull request #114: Merged external.adoc#add-ons with addons.adoc
tandraschko merged pull request #114: URL: https://github.com/apache/deltaspike/pull/114 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [deltaspike] tandraschko merged pull request #113: Avoid NPE in WindowContextImpl
tandraschko merged pull request #113: URL: https://github.com/apache/deltaspike/pull/113 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [deltaspike] tandraschko commented on pull request #113: Avoid NPE in WindowContextImpl
tandraschko commented on pull request #113: URL: https://github.com/apache/deltaspike/pull/113#issuecomment-786540826 i think the null check doesnt hurt here, i will merge it This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [deltaspike] tandraschko merged pull request #116: Proxy support for Quarkus and Hibernate
tandraschko merged pull request #116: URL: https://github.com/apache/deltaspike/pull/116 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (DELTASPIKE-508) @Transaction return NPE on qualified Datasource injections
[ https://issues.apache.org/jira/browse/DELTASPIKE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-508. Resolution: Fixed fixed a long time ago > @Transaction return NPE on qualified Datasource injections > -- > > Key: DELTASPIKE-508 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-508 > Project: DeltaSpike > Issue Type: Bug > Components: JPA-Module >Affects Versions: 0.5 > Environment: Linux, JBoss-EAP-6.2, Java 7 >Reporter: Cloves J. G. Almeida >Assignee: Mark Struberg >Priority: Minor > > When using JTA transactions (and probably Resouce Local), a bean injecting a > qualified DataSource _without an EntityManager also being injected_ will fail > with an NPE if there's no default EntityManager or won't put the correct > datasource into the transaction (and fail or act inconsistently). > The reason is that in > org.apache.deltaspike.jpa.impl.transaction.TransactionStrategyHelper.resolveEntityManagerQualifiers > only injected EntityManagers are scanned for qualifiers used to resolve. > A workaround is to place a qualified EntityManager pointing to the same > datasource. This is limited, however. Some use cases, like batch processing > does not require an EntityManager and one might not be available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-440) discuss helper for adding deployment-problems
[ https://issues.apache.org/jira/browse/DELTASPIKE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-440. Resolution: Won't Fix cleaning up old tickets > discuss helper for adding deployment-problems > - > > Key: DELTASPIKE-440 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-440 > Project: DeltaSpike > Issue Type: Task > Components: Core >Reporter: Gerhard Petracek >Assignee: Rafael Benevides >Priority: Major > > in many cases it's possible to detect deployment-problems before > AfterDeploymentValidation. it's possible to throw an exception at any time, > however, it might be useful to unify it. e.g. collecting problems via a > helper which adds all issues via > AfterDeploymentValidation#addDeploymentProblem -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-413) Add the ability to create Seam 2 like Factories
[ https://issues.apache.org/jira/browse/DELTASPIKE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-413. Resolution: Won't Fix np PR so far, closing. > Add the ability to create Seam 2 like Factories > --- > > Key: DELTASPIKE-413 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-413 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Affects Versions: 0.5 >Reporter: Jason Porter >Assignee: Thomas Hug >Priority: Major > > For more information see > http://stackoverflow.com/questions/18774025/how-can-i-update-a-collection-that-is-produces-applicationscoped > and > http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Data-module-full-replacement-for-Seam-Factories-td4655749.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-193) Setup SecurityManager enabled CI build
[ https://issues.apache.org/jira/browse/DELTASPIKE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-193. -- Resolution: Won't Fix SecurityManager is supported in DeltaSpike itself, but most libs and containers do not fully appreciate it. > Setup SecurityManager enabled CI build > -- > > Key: DELTASPIKE-193 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-193 > Project: DeltaSpike > Issue Type: Task > Components: Build >Affects Versions: 0.2-incubating >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > > We currently don't have any CI environment which uses a SecurityManager. We > should add such an environment to check whether DeltaSpike properly uses > doPrivileged blocks where needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DELTASPIKE-1318) Unsatisfied dependencies for type ApplicationContext (deltaspike-cdictrl-weld) in payara 4.1.2.174
[
https://issues.apache.org/jira/browse/DELTASPIKE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-1318.
-
Assignee: Mark Struberg (was: Matej Novotny)
Resolution: Cannot Reproduce
> Unsatisfied dependencies for type ApplicationContext
> (deltaspike-cdictrl-weld) in payara 4.1.2.174
> --
>
> Key: DELTASPIKE-1318
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1318
> Project: DeltaSpike
> Issue Type: Bug
> Components: CdiControl
>Affects Versions: 1.8.1
> Environment: payara 4.1.2.174
>Reporter: Andreas Keefer
>Assignee: Mark Struberg
>Priority: Major
>
> ApplicationContext can't be injected in WeldContextControl on payara 4.1.2.174
>
> Maven dependencies
> {code:java}
>
> org.apache.deltaspike.cdictrl
> deltaspike-cdictrl-api
> compile
>
>
> org.apache.deltaspike.cdictrl
> deltaspike-cdictrl-weld
> runtime
>
> {code}
> Sample Bean:
> {code:java}
> @Singleton
> @Startup
> public class KafkaVehicleReceiver {
> @Inject
> private ContextControl contextControl;
> ...
> }{code}
> payara log:
> {code:java}
> [2018-02-27T00:40:54.713+0100] [Payara 4.1] [SCHWERWIEGEND] [NCLS-CORE-00026]
> [javax.enterprise.system.core] [tid: _ThreadID=47
> _ThreadName=admin-thread-pool::admin-listener(1)] [timeMillis: 1519688454713]
> [levelValue: 1000] [[
> Exception during lifecycle processing
> org.glassfish.deployment.common.DeploymentException: CDI deployment
> failure:WELD-001408: Unsatisfied dependencies for type ApplicationContext
> with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private
> org.apache.deltaspike.cdise.weld.WeldContextControl.applicationContext
> at
> org.apache.deltaspike.cdise.weld.WeldContextControl.applicationContext(WeldContextControl.java:0)
> at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:270)
> at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
> at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:333)
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:497)
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:220)
> at
> org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:508)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:544)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:540)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:539)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:570)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:562)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:561)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1469)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:111)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1851)
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1727)
> at
> org.glassfish.admin.rest.resources.admin.CommandResource.executeCommand(CommandResource.java:407)
> at
> org.glassfish.admin.rest.resources.admin.CommandResource.execCommandSimpInMultOut(CommandResource.java:234)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> at
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
> at
>
