[jira] [Commented] (DELTASPIKE-1230) use of ContextControl in CdiTestRunner blows up with NullPointerException
[
https://issues.apache.org/jira/browse/DELTASPIKE-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829819#comment-15829819
]
ASF subversion and git services commented on DELTASPIKE-1230:
-
Commit 08d5916ed5719087abe4829f42b83d493c6ede3a in deltaspike's branch
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=08d5916 ]
DELTASPIKE-1230 fix NPE in CdiTestRunner
txs rsandtner for the report!
> use of ContextControl in CdiTestRunner blows up with NullPointerException
> -
>
> Key: DELTASPIKE-1230
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1230
> Project: DeltaSpike
> Issue Type: Bug
> Components: TestControl
>Affects Versions: 1.7.0, 1.7.1, 1.7.2
>Reporter: Reinhard Sandtner
> Attachments: deltaspike-test-sample.zip
>
>
> i'm trying to implement a base test class with the annotation
> {{@RunWith(CdiTestRunner.class)}} and provide some utility methods for tests.
> to start a new request in a test method i'm using {{ContextControl}} to stop
> and start {{RequestContext}} and {{SessionContext}}.
> here are my cdi-ctrl dependencies
> {code}
>
> org.apache.deltaspike.cdictrl
> deltaspike-cdictrl-openejb
> ${deltaspike.version}
> test
>
>
> org.apache.tomee
> openejb-core
> 7.0.2
> test
>
> {code}
> with one test everything works fine but as soon as i've more the call to
> {{contextControl.stopContext(RequestScoped.class)}} (or any other scope)
> blows up with an NPE
> {noformat}
> java.lang.NullPointerException
> at
> java.util.Collections$UnmodifiableCollection.(Collections.java:1026)
> at java.util.Collections$UnmodifiableList.(Collections.java:1302)
> at java.util.Collections.unmodifiableList(Collections.java:1287)
> at
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.getActiveExternalContainers(CdiTestRunner.java:838)
> at
> org.apache.deltaspike.testcontrol.impl.request.ContextControlDecorator.stopContext(ContextControlDecorator.java:108)
> 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:497)
> at
> org.apache.webbeans.intercept.DecoratorHandler.invoke(DecoratorHandler.java:96)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl$$OwbInterceptProxy0.stopContext(org/apache/deltaspike/cdise/owb/OpenWebBeansContextControl.java)
> 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:497)
> at
> org.apache.webbeans.intercept.AbstractInvocationContext.directProceed(AbstractInvocationContext.java:113)
> at
> org.apache.webbeans.intercept.AbstractInvocationContext.proceed(AbstractInvocationContext.java:106)
> at
> org.apache.webbeans.intercept.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:67)
> at
> org.apache.webbeans.intercept.DefaultInterceptorHandler.invoke(DefaultInterceptorHandler.java:139)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl$$OwbInterceptProxy0.stopContext(org/apache/deltaspike/cdise/owb/OpenWebBeansContextControl.java)
> at
> at.rsandtner.sample.deltaspike.test.ContainerTest.cleanInstances(ContainerTest.java:40)
> at
> at.rsandtner.sample.deltaspike.test.TestTwo.testSomething(TestTwo.java:50)
> 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:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner$ContainerAwareMethodInvoker.invokeMethod(CdiTestRunner.java:346)
> at
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner$ContainerAwareMethodInvoker.evaluate(CdiTestRunner.java:318)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners
[jira] [Commented] (DELTASPIKE-1231) Update the Weld3 Profile for DS 1.8
[ https://issues.apache.org/jira/browse/DELTASPIKE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831729#comment-15831729 ] ASF subversion and git services commented on DELTASPIKE-1231: - Commit 9c811f2e74c542bdceedec83af089034267705ae in deltaspike's branch refs/heads/master from [~johndament] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=9c811f2 ] DELTASPIKE-1231 Update build profile for Weld3. > Update the Weld3 Profile for DS 1.8 > --- > > Key: DELTASPIKE-1231 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1231 > Project: DeltaSpike > Issue Type: New Feature > Components: Build >Reporter: John D. Ament >Assignee: John D. Ament > > Presently, DeltaSpike does not compile with CDI 2 on the classpath. When you > compile w/ CDI 2.0 the default methods on interfaces are not leverages. > For DS 1.8, the Weld 3 profile should get updated to: > - Point to latest beta > - Point to java compiler 1.8 (e.g. this build should fail on Java 7 and below) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-1232) Weld 3.0.0.CR1 package changes causing build failures
[ https://issues.apache.org/jira/browse/DELTASPIKE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834704#comment-15834704 ] ASF subversion and git services commented on DELTASPIKE-1232: - Commit b4126f708c8d163c660bac23230ca670a17e26c6 in deltaspike's branch refs/heads/master from [~manovotn] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b4126f7 ] DELTASPIKE-1232: WeldContextControl should use Weld API instead of having internal dependencies. > Weld 3.0.0.CR1 package changes causing build failures > - > > Key: DELTASPIKE-1232 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1232 > Project: DeltaSpike > Issue Type: Bug > Components: CdiControl >Affects Versions: 1.7.2 >Reporter: Matej Novotny >Assignee: Matej Novotny > > Using Weld 3.0.0.CR1, Weld-container control module fails to build. > The reason is the package change introduced as a part of Weld's JDK 9 early > adaptation (see [WELD-2305|https://issues.jboss.org/browse/WELD-2305]). This > was done to eliminate future package-clash problems. > It should be investigated whether DS can depend on Weld API instead of > internals to handle container control as depending on internals is a bad > practice anyway. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-1178) DS 1.7.0 introduced a transitive dependency to arquillian
[ https://issues.apache.org/jira/browse/DELTASPIKE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951047#comment-15951047 ] ASF subversion and git services commented on DELTASPIKE-1178: - Commit 853bd6ffca53f44d8bb482b1dbb330ec7b85c9b5 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=853bd6f ] DELTASPIKE-1178 remove transitive dependencies to Arquillian > DS 1.7.0 introduced a transitive dependency to arquillian > - > > Key: DELTASPIKE-1178 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1178 > Project: DeltaSpike > Issue Type: Bug > Components: TestControl >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > TestControl doesn't need any Arquillian dependency at all. No idea why this > got introduced... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1242) select distinct generates wrong JPQL
[
https://issues.apache.org/jira/browse/DELTASPIKE-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967818#comment-15967818
]
ASF subversion and git services commented on DELTASPIKE-1242:
-
Commit 4aa12e06536de2f5acc151844a9bdf26f7c28b49 in deltaspike's branch
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=4aa12e0 ]
DELTASPIKE-1242 only use CriteriaBuilder.select if 1 param
CriteriaBuilder.multiselect should only be used if multiple return values
are required. Using multiselect for everyting might cost performance and
trigger wrong execution paths in JPA providers.
> select distinct generates wrong JPQL
>
>
> Key: DELTASPIKE-1242
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1242
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>
> The Data module generateds brackets into a distinct JPQL statement
> Instead of
> {source}
> SELECT DISTINCT e.mycol from SomeEntity e
> {source}
> we currently generate:
> {source}
> SELECT DISTINCT(e.mycol) from SomeEntity e
> {source}
> But this is not correct according to the JPA spec. It also actually only
> works on Hibernate but fails on both EclipseLink (RI) and OpenJPA.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1246) Add support for TabularData in our @MBean implementation
[ https://issues.apache.org/jira/browse/DELTASPIKE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981008#comment-15981008 ] ASF subversion and git services commented on DELTASPIKE-1246: - Commit 7748876931635172a906808d550cd316342109ac in deltaspike's branch refs/heads/master from rmannibucau [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=7748876 ] DELTASPIKE-1246 add support for TabularData in @MBean > Add support for TabularData in our @MBean implementation > > > Key: DELTASPIKE-1246 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1246 > Project: DeltaSpike > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.8.0 > > > @JmxManaged(convertMapToTabularData=true) (true by default) converts > Map to a TabularData allowing to expose easily a map through JMX. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1240) [Config] add List support
[
https://issues.apache.org/jira/browse/DELTASPIKE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981058#comment-15981058
]
ASF subversion and git services commented on DELTASPIKE-1240:
-
Commit 83a93da2a5dd423fe26ef55447b51406c8a85ee3 in deltaspike's branch
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=83a93da ]
DELTASPIKE-1240 add list support for DeltaSpike config
> [Config] add List support
> -
>
> Key: DELTASPIKE-1240
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1240
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Configuration
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> Currently there is no built-in way to configure lists of values. This is
> useful if you think about e.g. something like
> {code}
> mycompany.myproj.batch.error.email=someone@mycomp,else@mycomp,ops@mycomp
> {code}
> Any ',' character inside the payload might get escaped via '\,' and a single
> backslash '\' itself with double-backslash '\\'
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1246) Add support for TabularData in our @MBean implementation
[ https://issues.apache.org/jira/browse/DELTASPIKE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981059#comment-15981059 ] ASF subversion and git services commented on DELTASPIKE-1246: - Commit 135c59f05a91b5d90c0554be385adc6b6cc219f9 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=135c59f ] DELTASPIKE-1246 fix javadoc formatting line was too long > Add support for TabularData in our @MBean implementation > > > Key: DELTASPIKE-1246 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1246 > Project: DeltaSpike > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.8.0 > > > @JmxManaged(convertMapToTabularData=true) (true by default) converts > Map to a TabularData allowing to expose easily a map through JMX. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1245) [Config] expose config via JMX bean
[ https://issues.apache.org/jira/browse/DELTASPIKE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994586#comment-15994586 ] ASF subversion and git services commented on DELTASPIKE-1245: - Commit 0a8160f7b721493db8f6728182fab252ce2916c6 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=0a8160f ] DELTASPIKE-1245 expose config via JMX bean initial version - needs review > [Config] expose config via JMX bean > --- > > Key: DELTASPIKE-1245 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1245 > Project: DeltaSpike > Issue Type: New Feature >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > It would be nice if the Configuration of an application could be exposed via > JMX bean. > Currently there is no easy way to have the Ops team look how an application > is configured. > This is not about checking a single configured value but the whole > configuration system! > I've built a JSF page for a customer which gets copied around from one > project to the other. > But it would be much better to expose those values via JMX by default. That > way we would not need any user interface part, not much security (JMX is > secured anyway), no JSF, etc. > What information does get exposed? > 1.) The list of all picked up ConfigSources + their ordinals. Of course > already sorted > 2.) All configured values. > - their key > - their 'native' value (without variables, etc) > - the ConfigSource from which the value effectively got picked up > - Map of all the ConfigSources containing the key + the values which got > resolved on each level. > With this information the Ops team can perform the right tweaks much more > easily. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1245) [Config] expose config via JMX bean
[ https://issues.apache.org/jira/browse/DELTASPIKE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994588#comment-15994588 ] ASF subversion and git services commented on DELTASPIKE-1245: - Commit 5c04cec3b4c381f78a5de9888ab81f7f0c701ed9 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=5c04cec ] DELTASPIKE-1245 add ConfigEntry listing > [Config] expose config via JMX bean > --- > > Key: DELTASPIKE-1245 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1245 > Project: DeltaSpike > Issue Type: New Feature >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > It would be nice if the Configuration of an application could be exposed via > JMX bean. > Currently there is no easy way to have the Ops team look how an application > is configured. > This is not about checking a single configured value but the whole > configuration system! > I've built a JSF page for a customer which gets copied around from one > project to the other. > But it would be much better to expose those values via JMX by default. That > way we would not need any user interface part, not much security (JMX is > secured anyway), no JSF, etc. > What information does get exposed? > 1.) The list of all picked up ConfigSources + their ordinals. Of course > already sorted > 2.) All configured values. > - their key > - their 'native' value (without variables, etc) > - the ConfigSource from which the value effectively got picked up > - Map of all the ConfigSources containing the key + the values which got > resolved on each level. > With this information the Ops team can perform the right tweaks much more > easily. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1245) [Config] expose config via JMX bean
[ https://issues.apache.org/jira/browse/DELTASPIKE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994587#comment-15994587 ] ASF subversion and git services commented on DELTASPIKE-1245: - Commit d64cab49570a26094a8caaa7698d9a1c7fdce624 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d64cab4 ] DELTASPIKE-1245 improve MBean handling > [Config] expose config via JMX bean > --- > > Key: DELTASPIKE-1245 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1245 > Project: DeltaSpike > Issue Type: New Feature >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > It would be nice if the Configuration of an application could be exposed via > JMX bean. > Currently there is no easy way to have the Ops team look how an application > is configured. > This is not about checking a single configured value but the whole > configuration system! > I've built a JSF page for a customer which gets copied around from one > project to the other. > But it would be much better to expose those values via JMX by default. That > way we would not need any user interface part, not much security (JMX is > secured anyway), no JSF, etc. > What information does get exposed? > 1.) The list of all picked up ConfigSources + their ordinals. Of course > already sorted > 2.) All configured values. > - their key > - their 'native' value (without variables, etc) > - the ConfigSource from which the value effectively got picked up > - Map of all the ConfigSources containing the key + the values which got > resolved on each level. > With this information the Ops team can perform the right tweaks much more > easily. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1251) Make PersistenceConfigurationProvider pick up information from the config subsystem
[ https://issues.apache.org/jira/browse/DELTASPIKE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000500#comment-16000500 ] ASF subversion and git services commented on DELTASPIKE-1251: - Commit f5ba10bb78465ac044664eba524d1bbc2bedee39 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=f5ba10b ] DELTASPIKE-1251 pick up EMF config via ConfigResolver. Currently PersistenceConfigurationProvider only looks for files named persistence-persistenceUnitName.properties. It would be great to also be able to pick up EntityManagerFactory configuration via our standard ConfigResolver system. For a PersistenceUnit named 'MyUnit' we could e.g. pick up persitence-MyUnit.properties plus all config values which start with 'deltaspike.persistence.config.MyUnit.' A config value 'deltaspike.persistence.config.MyUnit.javax.persistence.password=bla' Would end up as javax.persistence.password=bla configuration entry > Make PersistenceConfigurationProvider pick up information from the config > subsystem > --- > > Key: DELTASPIKE-1251 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1251 > Project: DeltaSpike > Issue Type: New Feature > Components: JPA-Module >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Currently PersistenceConfigurationProvider only looks for files named > persistence-persistenceUnitName.properties. > It would be great to also be able to pick up EntityManagerFactory > configuration via our standard ConfigResolver system. > For a PersistenceUnit named 'MyUnit' we could e.g. pick up > persitence-MyUnit.properties plus all config values which start with > 'deltaspike.persistence.config.MyUnit.' > A config value > 'deltaspike.persistence.config.MyUnit.javax.persistence.password=bla' > Would end up as javax.persistence.password=bla configuration entry -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system
[ https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002318#comment-16002318 ] ASF subversion and git services commented on DELTASPIKE-1253: - Commit 270f3d0bbbc8e4e5ea8328cd23e56101bef9a4a7 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=270f3d0 ] DELTASPIKE-1253 support file:// for PropertyFileConfig A PropertyFileConfig can now also pick up other URLs than from the classpath. By returning a "file:///var/opt/myapp/my.properties" you might now load properties from a file on the classpath. > allow PropertyFileConfig to also pick up property files from the file system > > > Key: DELTASPIKE-1253 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Currently PropertyFileConfig only picks up properties with a given name from > the classpath. > It should also be allowed to use other URLs like file:// or http:// to pick > up configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system
[ https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002342#comment-16002342 ] ASF subversion and git services commented on DELTASPIKE-1253: - Commit e7fce70c2d70ed3825119d6852110ef0dc8f4ad9 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=e7fce70 ] DELTASPIKE-1253 add new features to our documentation > allow PropertyFileConfig to also pick up property files from the file system > > > Key: DELTASPIKE-1253 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Currently PropertyFileConfig only picks up properties with a given name from > the classpath. > It should also be allowed to use other URLs like file:// or http:// to pick > up configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system
[ https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002350#comment-16002350 ] ASF subversion and git services commented on DELTASPIKE-1253: - Commit e2b54d4db684582e563aaaf5aa09c00cee42e6f7 in deltaspike's branch refs/heads/master from rmannibucau [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=e2b54d4 ] DELTASPIKE-1253 handling file path too > allow PropertyFileConfig to also pick up property files from the file system > > > Key: DELTASPIKE-1253 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Currently PropertyFileConfig only picks up properties with a given name from > the classpath. > It should also be allowed to use other URLs like file:// or http:// to pick > up configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1252) data-documentation missing Optional return value
[
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002533#comment-16002533
]
ASF subversion and git services commented on DELTASPIKE-1252:
-
Commit d1e4739e3b25fc93e4206344d61ddb24dc1a1391 in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d1e4739 ]
DELTASPIKE-1252 - Adding Java 8 semantics to EBNF-like form.
> data-documentation missing Optional return value
>
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List)
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional
> or a list of entities.
> • It must start with the findBy prefix ..."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1250) create a master/client encryption handling
[ https://issues.apache.org/jira/browse/DELTASPIKE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009249#comment-16009249 ] ASF subversion and git services commented on DELTASPIKE-1250: - Commit ebcac8257f3a170d5dcb2e8244e476830ade4c43 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=ebcac82 ] DELTASPIKE-1250 add CLI client and switch to sha256 > create a master/client encryption handling > -- > > Key: DELTASPIKE-1250 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1250 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > For storing passwords in our configuration I'd like to implement a 2 stage > approach to symmetric encryption. > The current ideas is to have an encrypted hash derived from a master password > and machine specific information (MAC, IP, expiry date, etc). > This encrypted sequence is different on every box. But the decrypted hash is > not. > > With this hash we can encode a user password, which is then ofc the same on > different boxes. > Of course all that is just security by obscurity, but it's still much better > than plaintext and even close to Hashicorp Vault. > After all, the only really secure way is using a hardware crypto box plus the > user has to manually provide a password and not using static passwords but > 1-time consumable tokens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1250) create a master/client encryption handling
[ https://issues.apache.org/jira/browse/DELTASPIKE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009248#comment-16009248 ] ASF subversion and git services commented on DELTASPIKE-1250: - Commit a57fbcfa7e924fa65c167daedf7e523a5c4169c5 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=a57fbcf ] DELTASPIKE-1250 CipherService for encrypting/decrypting with secrets > create a master/client encryption handling > -- > > Key: DELTASPIKE-1250 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1250 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > For storing passwords in our configuration I'd like to implement a 2 stage > approach to symmetric encryption. > The current ideas is to have an encrypted hash derived from a master password > and machine specific information (MAC, IP, expiry date, etc). > This encrypted sequence is different on every box. But the decrypted hash is > not. > > With this hash we can encode a user password, which is then ofc the same on > different boxes. > Of course all that is just security by obscurity, but it's still much better > than plaintext and even close to Hashicorp Vault. > After all, the only really secure way is using a hardware crypto box plus the > user has to manually provide a password and not using static passwords but > 1-time consumable tokens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1254) print full configuration on bootstrap
[ https://issues.apache.org/jira/browse/DELTASPIKE-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010049#comment-16010049 ] ASF subversion and git services commented on DELTASPIKE-1254: - Commit f767c80c845d8b5643d23af49eb7d23d67d1752f in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=f767c80 ] DELTASPIKE-1254 pring full configuration on bootstrap This feature needs to be enabled via the configuration entry 'deltaspike.configuration.log=true' > print full configuration on bootstrap > - > > Key: DELTASPIKE-1254 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1254 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Colleague asked for printing out all the ConfigSources + all configured > values during boot. Basically the same information we now provide via JMX, > but just in the log. > Of course this option should be off by default but might get enabled by a > config property. > Technically this might get implemented in the ConfigExtension as easy as > having a step in AfterDeploymentValidation which just collects the info and > logs it out. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1249) Pick up ~/.deltaspike/apache-deltaspike.properties from user.home folder
[ https://issues.apache.org/jira/browse/DELTASPIKE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012019#comment-16012019 ] ASF subversion and git services commented on DELTASPIKE-1249: - Commit 842c84bd1767905a19e2af01bdfe88d416d1b2da in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=842c84b ] DELTASPIKE-1249 pick up configuration from usrer home folder The location which will be looked for is ~/.deltaspike/apache-deltaspike.properties A ConfigSource for it will only be added if this file exists. > Pick up ~/.deltaspike/apache-deltaspike.properties from user.home folder > > > Key: DELTASPIKE-1249 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1249 > Project: DeltaSpike > Issue Type: Bug > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > It might be very useful to pick up a property file from the users home > folder. > If it is not there it simply does not do anything. > If available it will get picked up. > A sensitive default for the ordinal might be 250, but this value can of > course be tweaked with the usual mechanism. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1250) create a master/client encryption handling
[ https://issues.apache.org/jira/browse/DELTASPIKE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012091#comment-16012091 ] ASF subversion and git services commented on DELTASPIKE-1250: - Commit 0cdede08c07b0ed791b9018e1ea5281b690728ae in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=0cdede0 ] DELTASPIKE-1250 only log out the master.hash index key not the hash itself > create a master/client encryption handling > -- > > Key: DELTASPIKE-1250 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1250 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > For storing passwords in our configuration I'd like to implement a 2 stage > approach to symmetric encryption. > The current ideas is to have an encrypted hash derived from a master password > and machine specific information (MAC, IP, expiry date, etc). > This encrypted sequence is different on every box. But the decrypted hash is > not. > > With this hash we can encode a user password, which is then ofc the same on > different boxes. > Of course all that is just security by obscurity, but it's still much better > than plaintext and even close to Hashicorp Vault. > After all, the only really secure way is using a hardware crypto box plus the > user has to manually provide a password and not using static passwords but > 1-time consumable tokens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1251) Make PersistenceConfigurationProvider pick up information from the config subsystem
[ https://issues.apache.org/jira/browse/DELTASPIKE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014721#comment-16014721 ] ASF subversion and git services commented on DELTASPIKE-1251: - Commit 301ff1b4e73a547b1e1be5410ebbb5ff881b67c1 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=301ff1b ] DELTASPIKE-1251 apply ConfigFilter to PersistenceConfiguration values > Make PersistenceConfigurationProvider pick up information from the config > subsystem > --- > > Key: DELTASPIKE-1251 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1251 > Project: DeltaSpike > Issue Type: New Feature > Components: JPA-Module >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Currently PersistenceConfigurationProvider only looks for files named > persistence-persistenceUnitName.properties. > It would be great to also be able to pick up EntityManagerFactory > configuration via our standard ConfigResolver system. > For a PersistenceUnit named 'MyUnit' we could e.g. pick up > persitence-MyUnit.properties plus all config values which start with > 'deltaspike.persistence.config.MyUnit.' > A config value > 'deltaspike.persistence.config.MyUnit.javax.persistence.password=bla' > Would end up as javax.persistence.password=bla configuration entry -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1256) CdiTestRunner ProjectStage setting doesn't work on Config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014720#comment-16014720 ] ASF subversion and git services commented on DELTASPIKE-1256: - Commit 84f956f6663c3604af0f0d07d2cfb2b8d857eafd in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=84f956f ] DELTASPIKE-1256 remove local ProjectStage cache from ConfigResolver After profiling and doing some performance tests it became clear that the performance impact is really low. Probably because JIT optimises it anyway. By going to ProjectStageProducer every time we can more easily invalidate a ProjectStage at runtime. This is especially important for unit testing scenarios. > CdiTestRunner ProjectStage setting doesn't work on Config > - > > Key: DELTASPIKE-1256 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1256 > Project: DeltaSpike > Issue Type: Bug > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > If you try to use different ProjectStages with CdiTestRunner, then only the > first one gets used for ConfigResolver. > So this ends up with ProjectStage.Production most of the times. > The reason is that the current ProjectStage gets 'cached' inside > ConfigResolver. > We should do some performance tests to check whether we can get rid of that. > Because the ProjectStageProducer already uses a cache anyway. So the JIT > might level out this method call after a few seconds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1254) print full configuration on bootstrap
[ https://issues.apache.org/jira/browse/DELTASPIKE-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017221#comment-16017221 ] ASF subversion and git services commented on DELTASPIKE-1254: - Commit a9dd74e3924da4258ab551e25b4f382514bc7ec2 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=a9dd74e ] DELTASPIKE-1254 filter value for logging before printing it Otherwise we might print cleartext passwords > print full configuration on bootstrap > - > > Key: DELTASPIKE-1254 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1254 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Colleague asked for printing out all the ConfigSources + all configured > values during boot. Basically the same information we now provide via JMX, > but just in the log. > Of course this option should be off by default but might get enabled by a > config property. > Technically this might get implemented in the ConfigExtension as easy as > having a step in AfterDeploymentValidation which just collects the info and > logs it out. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1250) create a master/client encryption handling
[ https://issues.apache.org/jira/browse/DELTASPIKE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021241#comment-16021241 ] ASF subversion and git services commented on DELTASPIKE-1250: - Commit d1cc650d68686d02656f53a4f532a2acb911bc6d in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d1cc650 ] DELTASPIKE-1250 add documentation and improve JavaDocs > create a master/client encryption handling > -- > > Key: DELTASPIKE-1250 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1250 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > For storing passwords in our configuration I'd like to implement a 2 stage > approach to symmetric encryption. > The current ideas is to have an encrypted hash derived from a master password > and machine specific information (MAC, IP, expiry date, etc). > This encrypted sequence is different on every box. But the decrypted hash is > not. > > With this hash we can encode a user password, which is then ofc the same on > different boxes. > Of course all that is just security by obscurity, but it's still much better > than plaintext and even close to Hashicorp Vault. > After all, the only really secure way is using a hardware crypto box plus the > user has to manually provide a password and not using static passwords but > 1-time consumable tokens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system
[ https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021240#comment-16021240 ] ASF subversion and git services commented on DELTASPIKE-1253: - Commit 63ee99e36a4a9676a1e477d3d898a206fde21a8e in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=63ee99e ] DELTASPIKE-1253 fix broken unit test on windows > allow PropertyFileConfig to also pick up property files from the file system > > > Key: DELTASPIKE-1253 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > Currently PropertyFileConfig only picks up properties with a given name from > the classpath. > It should also be allowed to use other URLs like file:// or http:// to pick > up configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1250) create a master/client encryption handling
[ https://issues.apache.org/jira/browse/DELTASPIKE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021537#comment-16021537 ] ASF subversion and git services commented on DELTASPIKE-1250: - Commit 98d4c2ab2ea2ce15cfe60c637a3792c3843b49f4 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=98d4c2a ] DELTASPIKE-1250 adding documentation for encryption > create a master/client encryption handling > -- > > Key: DELTASPIKE-1250 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1250 > Project: DeltaSpike > Issue Type: New Feature > Components: Configuration >Affects Versions: 1.7.2 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > For storing passwords in our configuration I'd like to implement a 2 stage > approach to symmetric encryption. > The current ideas is to have an encrypted hash derived from a master password > and machine specific information (MAC, IP, expiry date, etc). > This encrypted sequence is different on every box. But the decrypted hash is > not. > > With this hash we can encode a user password, which is then ofc the same on > different boxes. > Of course all that is just security by obscurity, but it's still much better > than plaintext and even close to Hashicorp Vault. > After all, the only really secure way is using a hardware crypto box plus the > user has to manually provide a password and not using static passwords but > 1-time consumable tokens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1258) skip flush with one EntityManager
[ https://issues.apache.org/jira/browse/DELTASPIKE-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033014#comment-16033014 ] ASF subversion and git services commented on DELTASPIKE-1258: - Commit e6b119c708bd684c7800faa5c86c1aafb110d723 in deltaspike's branch refs/heads/master from [~gpetracek] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=e6b119c ] DELTASPIKE-1258 skip #flush before #commit with one active EntityManager > skip flush with one EntityManager > - > > Key: DELTASPIKE-1258 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1258 > Project: DeltaSpike > Issue Type: Improvement > Components: JPA-Module >Affects Versions: 1.8.0 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek > Fix For: 1.8.1 > > > if there is just one active EntityManager, we don't need a #flush before the > #commit. some persistence-providers don't optimize the #commit if there was > no change after #flush. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1259) upgraded version numbers
[ https://issues.apache.org/jira/browse/DELTASPIKE-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035947#comment-16035947 ] ASF subversion and git services commented on DELTASPIKE-1259: - Commit b1276fcd3c5ff296674b8dd5f5432c549c996d04 in deltaspike's branch refs/heads/master from [~gpetracek] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b1276fc ] DELTASPIKE-1259 upgraded version numbers > upgraded version numbers > > > Key: DELTASPIKE-1259 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1259 > Project: DeltaSpike > Issue Type: Task > Components: Build >Affects Versions: 1.8.0 >Reporter: Gerhard Petracek > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1252) data-documentation missing Optional return value
[
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035971#comment-16035971
]
ASF subversion and git services commented on DELTASPIKE-1252:
-
Commit fbf62e3bbc17310ff2c8eccd096f19764e02d4c1 in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=fbf62e3 ]
DELTASPIKE-1252 - Clarifying text for what can be returned.
> data-documentation missing Optional return value
>
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.1
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List)
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional
> or a list of entities.
> • It must start with the findBy prefix ..."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1070) Refactor RepositoryComponent/s
[ https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036121#comment-16036121 ] ASF subversion and git services commented on DELTASPIKE-1070: - Commit 46a3b6759fabb55fd2b913b9f7b4635687d0c5d7 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=46a3b67 ] DELTASPIKE-1070 Refactor RepositoryComponent/s > Refactor RepositoryComponent/s > -- > > Key: DELTASPIKE-1070 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1070 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > Currently a RepositoryComponent is initialized during PAT. Therefore > RepositoryComponent requires a lazyInit. > If we move the actual creation of the RepositoryComponent's to > AfterBeanDiscovery, we don't need such lazy init "hacks". > IMO we should also split the RepositoryComponent into a data object and a > initializer as it currently feels very unstructured. > Same applies for the RepositoryMethod and RepositoryEntity. > We could also allign the naming a little bit: > RepositoryComponents -> something MetadataStore or MetadataManager > RepositoryComponent -> RepositoryMetadata > RepositoryMethod -> RepositoryMethodMetadata > RepositoryEntity -> EntityMetadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1070) Refactor RepositoryComponent/s
[ https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036218#comment-16036218 ] ASF subversion and git services commented on DELTASPIKE-1070: - Commit 3e39a2c4c4701f18cffc0d311bd972a79640463f in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=3e39a2c ] DELTASPIKE-1070 cosmetics > Refactor RepositoryComponent/s > -- > > Key: DELTASPIKE-1070 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1070 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > Currently a RepositoryComponent is initialized during PAT. Therefore > RepositoryComponent requires a lazyInit. > If we move the actual creation of the RepositoryComponent's to > AfterBeanDiscovery, we don't need such lazy init "hacks". > IMO we should also split the RepositoryComponent into a data object and a > initializer as it currently feels very unstructured. > Same applies for the RepositoryMethod and RepositoryEntity. > We could also allign the naming a little bit: > RepositoryComponents -> something MetadataStore or MetadataManager > RepositoryComponent -> RepositoryMetadata > RepositoryMethod -> RepositoryMethodMetadata > RepositoryEntity -> EntityMetadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1070) Refactor RepositoryComponent/s
[ https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036217#comment-16036217 ] ASF subversion and git services commented on DELTASPIKE-1070: - Commit 96c6ba2af7a16368c66a8326e0a474e9d1ded2c0 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=96c6ba2 ] DELTASPIKE-1070 removed unused class > Refactor RepositoryComponent/s > -- > > Key: DELTASPIKE-1070 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1070 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > Currently a RepositoryComponent is initialized during PAT. Therefore > RepositoryComponent requires a lazyInit. > If we move the actual creation of the RepositoryComponent's to > AfterBeanDiscovery, we don't need such lazy init "hacks". > IMO we should also split the RepositoryComponent into a data object and a > initializer as it currently feels very unstructured. > Same applies for the RepositoryMethod and RepositoryEntity. > We could also allign the naming a little bit: > RepositoryComponents -> something MetadataStore or MetadataManager > RepositoryComponent -> RepositoryMetadata > RepositoryMethod -> RepositoryMethodMetadata > RepositoryEntity -> EntityMetadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1070) Refactor RepositoryComponent/s
[ https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036997#comment-16036997 ] ASF subversion and git services commented on DELTASPIKE-1070: - Commit 3451eb32f593ed839c73d0e37dd545877ba99e15 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=3451eb3 ] DELTASPIKE-1070 Removed unused class > Refactor RepositoryComponent/s > -- > > Key: DELTASPIKE-1070 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1070 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > Currently a RepositoryComponent is initialized during PAT. Therefore > RepositoryComponent requires a lazyInit. > If we move the actual creation of the RepositoryComponent's to > AfterBeanDiscovery, we don't need such lazy init "hacks". > IMO we should also split the RepositoryComponent into a data object and a > initializer as it currently feels very unstructured. > Same applies for the RepositoryMethod and RepositoryEntity. > We could also allign the naming a little bit: > RepositoryComponents -> something MetadataStore or MetadataManager > RepositoryComponent -> RepositoryMetadata > RepositoryMethod -> RepositoryMethodMetadata > RepositoryEntity -> EntityMetadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1070) Refactor RepositoryComponent/s
[ https://issues.apache.org/jira/browse/DELTASPIKE-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040552#comment-16040552 ] ASF subversion and git services commented on DELTASPIKE-1070: - Commit 80d672bf06b88fd2e1f501cf48fefe8d588acd7f in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=80d672b ] DELTASPIKE-1070 cosmetics > Refactor RepositoryComponent/s > -- > > Key: DELTASPIKE-1070 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1070 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > Currently a RepositoryComponent is initialized during PAT. Therefore > RepositoryComponent requires a lazyInit. > If we move the actual creation of the RepositoryComponent's to > AfterBeanDiscovery, we don't need such lazy init "hacks". > IMO we should also split the RepositoryComponent into a data object and a > initializer as it currently feels very unstructured. > Same applies for the RepositoryMethod and RepositoryEntity. > We could also allign the naming a little bit: > RepositoryComponents -> something MetadataStore or MetadataManager > RepositoryComponent -> RepositoryMetadata > RepositoryMethod -> RepositoryMethodMetadata > RepositoryEntity -> EntityMetadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1267) Remove second factory mechanism of QueryBuilder's
[ https://issues.apache.org/jira/browse/DELTASPIKE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040777#comment-16040777 ] ASF subversion and git services commented on DELTASPIKE-1267: - Commit 442366998715112497f6b18391bbee33dfa31a71 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=4423669 ] DELTASPIKE-1267 Remove second factory mechanism of QueryBuilder's > Remove second factory mechanism of QueryBuilder's > - > > Key: DELTASPIKE-1267 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1267 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > We don't need that "second layer" factory mechanism > currently we have a > - interface QueryBuilder > - QueryBuilderFactory > - 3 implementations of QueryBuilder > - QueryInvocation ( + QueryInvocationLiteral) > - A QueryInvocation on each QueryBuilder > the factory is actually enough to decide which QueryBuilder should be used - > there is no QueryInvocation etc. required > The performance will be better, too -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1267) Remove second factory mechanism of QueryBuilder's
[ https://issues.apache.org/jira/browse/DELTASPIKE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040779#comment-16040779 ] ASF subversion and git services commented on DELTASPIKE-1267: - Commit 73a4969dd8a826b5e0d00a9deb432899faa6c817 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=73a4969 ] DELTASPIKE-1267 Remove second factory mechanism of QueryBuilder's > Remove second factory mechanism of QueryBuilder's > - > > Key: DELTASPIKE-1267 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1267 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > We don't need that "second layer" factory mechanism > currently we have a > - interface QueryBuilder > - QueryBuilderFactory > - 3 implementations of QueryBuilder > - QueryInvocation ( + QueryInvocationLiteral) > - A QueryInvocation on each QueryBuilder > the factory is actually enough to decide which QueryBuilder should be used - > there is no QueryInvocation etc. required > The performance will be better, too -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1267) Remove second factory mechanism of QueryBuilder's
[ https://issues.apache.org/jira/browse/DELTASPIKE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040847#comment-16040847 ] ASF subversion and git services commented on DELTASPIKE-1267: - Commit b48416ae6a33c80c6a2c9c7e763abd157d580014 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b48416a ] DELTASPIKE-1267 Remove second factory mechanism of QueryBuilder's > Remove second factory mechanism of QueryBuilder's > - > > Key: DELTASPIKE-1267 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1267 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > We don't need that "second layer" factory mechanism > currently we have a > - interface QueryBuilder > - QueryBuilderFactory > - 3 implementations of QueryBuilder > - QueryInvocation ( + QueryInvocationLiteral) > - A QueryInvocation on each QueryBuilder > the factory is actually enough to decide which QueryBuilder should be used - > there is no QueryInvocation etc. required > The performance will be better, too -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1268) QueryProcessorFactory should be a bean
[ https://issues.apache.org/jira/browse/DELTASPIKE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041006#comment-16041006 ] ASF subversion and git services commented on DELTASPIKE-1268: - Commit d9b1acb2b54b87d5ba66bba4305d2723318d869a in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d9b1acb ] DELTASPIKE-1268 QueryProcessorFactory should be a bean > QueryProcessorFactory should be a bean > -- > > Key: DELTASPIKE-1268 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1268 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > similar to QueryBuilderFactory -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1269) [perf] Cache singleResultType per method
[ https://issues.apache.org/jira/browse/DELTASPIKE-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041032#comment-16041032 ] ASF subversion and git services commented on DELTASPIKE-1269: - Commit 762d3a53b4d029e5bdff5e7b3824e3686af19bfe in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=762d3a5 ] DELTASPIKE-1269 [perf] Cache singleResultType per method > [perf] Cache singleResultType per method > > > Key: DELTASPIKE-1269 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1269 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > Currently it's evaluated each time > we can just enhance our metadata -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1270) [perf] cache requiresTransaction per method
[ https://issues.apache.org/jira/browse/DELTASPIKE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041666#comment-16041666 ] ASF subversion and git services commented on DELTASPIKE-1270: - Commit a551978c2510be4397fae94a9c97056c5be2d5f9 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=a551978 ] DELTASPIKE-1270 [perf] cache requiresTransaction per method > [perf] cache requiresTransaction per method > --- > > Key: DELTASPIKE-1270 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1270 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1270) [perf] cache requiresTransaction per method
[ https://issues.apache.org/jira/browse/DELTASPIKE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042824#comment-16042824 ] ASF subversion and git services commented on DELTASPIKE-1270: - Commit dbd437ea0b267ae7badddeb2ae76133cd61a9be2 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=dbd437e ] DELTASPIKE-1270 refactored > [perf] cache requiresTransaction per method > --- > > Key: DELTASPIKE-1270 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1270 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1270) [perf] cache requiresTransaction per method
[ https://issues.apache.org/jira/browse/DELTASPIKE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042822#comment-16042822 ] ASF subversion and git services commented on DELTASPIKE-1270: - Commit 82ba8c0dd898288101f7ed36072deb426b8e8984 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=82ba8c0 ] DELTASPIKE-1270 refactored > [perf] cache requiresTransaction per method > --- > > Key: DELTASPIKE-1270 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1270 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1270) [perf] cache requiresTransaction per method
[ https://issues.apache.org/jira/browse/DELTASPIKE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042851#comment-16042851 ] ASF subversion and git services commented on DELTASPIKE-1270: - Commit 4965c176758672e32579d2af00bc0c458b828a9e in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=4965c17 ] DELTASPIKE-1270 [perf] cache Transactional per method > [perf] cache requiresTransaction per method > --- > > Key: DELTASPIKE-1270 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1270 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1270) [perf] cache requiresTransaction per method
[ https://issues.apache.org/jira/browse/DELTASPIKE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042878#comment-16042878 ] ASF subversion and git services commented on DELTASPIKE-1270: - Commit bdcbd2098c386b37514118506ec7fdc60988951b in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=bdcbd20 ] DELTASPIKE-1270 [perf] cache Transactional per method > [perf] cache requiresTransaction per method > --- > > Key: DELTASPIKE-1270 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1270 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1273) Test against OWB 2
[ https://issues.apache.org/jira/browse/DELTASPIKE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053182#comment-16053182 ] ASF subversion and git services commented on DELTASPIKE-1273: - Commit 82cd29fba2368363ad23f97288fd1e2235d3730a in deltaspike's branch refs/heads/master from [~johndament] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=82cd29f ] DELTASPIKE-1273 - Add testing against OWB2, minor fix for the weld3 profile to use latest stable by default. > Test against OWB 2 > -- > > Key: DELTASPIKE-1273 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1273 > Project: DeltaSpike > Issue Type: Test >Reporter: John D. Ament >Assignee: John D. Ament > Fix For: 1.8.1 > > > Add tests against OWB 2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1273) Test against OWB 2
[ https://issues.apache.org/jira/browse/DELTASPIKE-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053385#comment-16053385 ] ASF subversion and git services commented on DELTASPIKE-1273: - Commit 764545c2d0f902cd15b42a47a82e724f409557fe in deltaspike's branch refs/heads/master from [~johndament] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=764545c ] DELTASPIKE-1273 - Adding OWB2 profile for cdictrl > Test against OWB 2 > -- > > Key: DELTASPIKE-1273 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1273 > Project: DeltaSpike > Issue Type: Test >Reporter: John D. Ament >Assignee: John D. Ament > Fix For: 1.8.1 > > > Add tests against OWB 2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers
[
https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062177#comment-16062177
]
ASF subversion and git services commented on DELTASPIKE-940:
Commit 256431539ca8b01aa237d33f5bcb723e292f8893 in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=2564315 ]
DELTASPIKE-940 - First step in merging support for qualifiers and entity
manager resolvers in data and JPA modules.
> @Transactional and @EntityManagerConfig each use a different method to
> resolve EntityManagers
> -
>
> Key: DELTASPIKE-940
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module, JPA-Module
>Reporter: Xavier Dury
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.1
>
> Attachments: ds940.patch
>
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to
> specify which one(s) should be used. Currently, {{@Transactional}} and
> {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its
> {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}}
> ({{@EntityManagerConfig(entityManagerResolver =
> MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which
> {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks
> better and should be applied to {{@EntityManagerConfig}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1275) Build fails on Linux because Testclass filenames are to long
[ https://issues.apache.org/jira/browse/DELTASPIKE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063495#comment-16063495 ] ASF subversion and git services commented on DELTASPIKE-1275: - Commit cdb86507f29fcae21ca8ccb65571cb7e5aeb49e8 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=cdb8650 ] DELTASPIKE-1275 > Build fails on Linux because Testclass filenames are to long > > > Key: DELTASPIKE-1275 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1275 > Project: DeltaSpike > Issue Type: Bug > Components: JPA-Module >Affects Versions: 1.8.0 >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1274) Refactor proxy-module / improve performance
[ https://issues.apache.org/jira/browse/DELTASPIKE-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063543#comment-16063543 ] ASF subversion and git services commented on DELTASPIKE-1274: - Commit b4c2ed26341a732f475db440c1b16f6a77115617 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b4c2ed2 ] DELTASPIKE-1274 Refactor proxy-module / improve performance > Refactor proxy-module / improve performance > --- > > Key: DELTASPIKE-1274 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1274 > Project: DeltaSpike > Issue Type: Improvement > Components: Proxy-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > > Currently on each proxy method invocation, a dynamic lookup of the > InvocationHandler wrappers happens via BeanProvider. > We can simple refactor the proxy to pass the bean reference on proxy creation. > Also we can move the interceptor handling to the api - this is not only > required for ASM. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1279) SimpleSecurityViolation needs equals/hashcode
[ https://issues.apache.org/jira/browse/DELTASPIKE-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076972#comment-16076972 ] ASF subversion and git services commented on DELTASPIKE-1279: - Commit 02067752c9d4e32262791b9c210763990063bbf9 in deltaspike's branch refs/heads/master from [~rdebusscher] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=0206775 ] DELTASPIKE-1279: equals/hashcode for SimpleSecurityViolation > SimpleSecurityViolation needs equals/hashcode > - > > Key: DELTASPIKE-1279 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1279 > Project: DeltaSpike > Issue Type: Improvement > Components: Core >Reporter: Rudy De Busscher >Assignee: Rudy De Busscher > Fix For: 1.8.1 > > > SimpleSecurityViolation can be used to add violations to the Set of > violations when writing a custom voter. > Creation of the instance can be done by > org.apache.deltaspike.security.api.authorization.AbstractDecisionVoter#newSecurityViolation > But since the class SimpleSecurityViolation has no equals/hashcode, adding 2 > or more violations with the same reason results in multiple entries within > the Set. > A simple equals/hashcode based on the reason String property solves this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1282) DeltaSpikeFacesContextWrapper leaks on TomEE
[ https://issues.apache.org/jira/browse/DELTASPIKE-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089933#comment-16089933 ] ASF subversion and git services commented on DELTASPIKE-1282: - Commit a4998790afe24bde62ae3aa37e6a0c5728c81004 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=a499879 ] DELTASPIKE-1282 DeltaSpikeFacesContextWrapper leaks on TomEE > DeltaSpikeFacesContextWrapper leaks on TomEE > > > Key: DELTASPIKE-1282 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1282 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.8.0 >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers
[
https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124650#comment-16124650
]
ASF subversion and git services commented on DELTASPIKE-940:
Commit 28bcefc88dc38c27ad6acfe28a46f1810af81c56 in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=28bcefc ]
DELTASPIKE-940 - Avoid reading transactional annotation.
> @Transactional and @EntityManagerConfig each use a different method to
> resolve EntityManagers
> -
>
> Key: DELTASPIKE-940
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module, JPA-Module
>Reporter: Xavier Dury
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.1
>
> Attachments: ds940.patch
>
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to
> specify which one(s) should be used. Currently, {{@Transactional}} and
> {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its
> {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}}
> ({{@EntityManagerConfig(entityManagerResolver =
> MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which
> {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks
> better and should be applied to {{@EntityManagerConfig}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers
[
https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124721#comment-16124721
]
ASF subversion and git services commented on DELTASPIKE-940:
Commit 56d56989d4aa3f34e4353da42bca428f6a6751d2 in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=56d5698 ]
DELTASPIKE-940 - Introduce an SPI based defualt resolver based on qualifiers.
Adding note to not use the deprecated classes.
> @Transactional and @EntityManagerConfig each use a different method to
> resolve EntityManagers
> -
>
> Key: DELTASPIKE-940
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module, JPA-Module
>Reporter: Xavier Dury
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.1
>
> Attachments: ds940.patch
>
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to
> specify which one(s) should be used. Currently, {{@Transactional}} and
> {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its
> {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}}
> ({{@EntityManagerConfig(entityManagerResolver =
> MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which
> {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks
> better and should be applied to {{@EntityManagerConfig}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1281) Deltaspike does not pass BeanManager to persistenf factory config using "javax.persistence.bean.manager"
[
https://issues.apache.org/jira/browse/DELTASPIKE-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124722#comment-16124722
]
ASF subversion and git services commented on DELTASPIKE-1281:
-
Commit 7594ba6e36ccdf2bd0ea0e32926745b42c0eba63 in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=7594ba6 ]
DELTASPIKE-1281 - Add JPA Expected attribute for BeanManager.
> Deltaspike does not pass BeanManager to persistenf factory config using
> "javax.persistence.bean.manager"
>
>
> Key: DELTASPIKE-1281
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1281
> Project: DeltaSpike
> Issue Type: Bug
> Components: JPA-Module
>Affects Versions: 1.8.0
> Environment: Deltaspike 1.8, Weld 3.0, Java 8 (JSE) JPA with
> HIbernate 5.2.10
>Reporter: Alex Roytman
>Assignee: John D. Ament
> Fix For: 1.8.1
>
>
> As the result no injections were working in JPA listeners.
> Per specs Persistence UnitFactory expects BeanManager in
> javax.persistence.bean.manager property passed when instantiate it but
> org.apache.deltaspike.jpa.impl.entitymanager.PersistenceConfigurationProviderImpl
> does not pass it
> this simple override took care of it but I should not need to do it:
> {code:java}
> @ApplicationScoped
> @Alternative
> @Priority(Interceptor.Priority.APPLICATION + 10)
> public class CdiAwarePersistenceConfigurationProviderImpl extends
> PersistenceConfigurationProviderImpl implements
> PersistenceConfigurationProvider {
> @Inject BeanManager beanManager;
> @Override public Properties getEntityManagerFactoryConfiguration(String
> persistenceUnitName) {
> final Properties conf =
> super.getEntityManagerFactoryConfiguration(persistenceUnitName);
> conf.put("javax.persistence.bean.manager", beanManager);
> return conf;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1278) PropertyFileConfig does not respect optional on external resources
[
https://issues.apache.org/jira/browse/DELTASPIKE-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124732#comment-16124732
]
ASF subversion and git services commented on DELTASPIKE-1278:
-
Commit 6befd1231ca07059d8d02158c91c6ddf9ffa481d in deltaspike's branch
refs/heads/master from [~dennis.rippinger]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=6befd12 ]
DELTASPIKE-1278: Added an additonal check to ensure local resources do exist to
respect optional flag.
> PropertyFileConfig does not respect optional on external resources
> --
>
> Key: DELTASPIKE-1278
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1278
> Project: DeltaSpike
> Issue Type: Bug
> Components: Configuration
>Affects Versions: 1.8.0
>Reporter: Dennis Rippinger
>
> Adding a property file from an external location (e.g. local file system)
> marked as optional is not respected by {{PropertyFileUtils}}. It creates a
> list of possible resource URLs, but does not check for their existence in all
> branches of its logic. This results in a list of possible nonexistent
> resources which could be optional, leading to an IllegalStateException.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1278) PropertyFileConfig does not respect optional on external resources
[
https://issues.apache.org/jira/browse/DELTASPIKE-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124733#comment-16124733
]
ASF subversion and git services commented on DELTASPIKE-1278:
-
Commit c7b5471c2912b68775ae887ab99d3e6cac57a053 in deltaspike's branch
refs/heads/master from [~dennis.rippinger]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=c7b5471 ]
DELTASPIKE-1278: Added an additonal check to ensure local resources do exist to
respect optional flag.
This closes #74
> PropertyFileConfig does not respect optional on external resources
> --
>
> Key: DELTASPIKE-1278
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1278
> Project: DeltaSpike
> Issue Type: Bug
> Components: Configuration
>Affects Versions: 1.8.0
>Reporter: Dennis Rippinger
>
> Adding a property file from an external location (e.g. local file system)
> marked as optional is not respected by {{PropertyFileUtils}}. It creates a
> list of possible resource URLs, but does not check for their existence in all
> branches of its logic. This results in a list of possible nonexistent
> resources which could be optional, leading to an IllegalStateException.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1281) Deltaspike does not pass BeanManager to persistenf factory config using "javax.persistence.bean.manager"
[
https://issues.apache.org/jira/browse/DELTASPIKE-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124740#comment-16124740
]
ASF subversion and git services commented on DELTASPIKE-1281:
-
Commit 618dd99b6861c80250d2724208e77807c14b5f32 in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=618dd99 ]
DELTASPIKE-1281 - Updating test.
> Deltaspike does not pass BeanManager to persistenf factory config using
> "javax.persistence.bean.manager"
>
>
> Key: DELTASPIKE-1281
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1281
> Project: DeltaSpike
> Issue Type: Bug
> Components: JPA-Module
>Affects Versions: 1.8.0
> Environment: Deltaspike 1.8, Weld 3.0, Java 8 (JSE) JPA with
> HIbernate 5.2.10
>Reporter: Alex Roytman
>Assignee: John D. Ament
> Fix For: 1.8.1
>
>
> As the result no injections were working in JPA listeners.
> Per specs Persistence UnitFactory expects BeanManager in
> javax.persistence.bean.manager property passed when instantiate it but
> org.apache.deltaspike.jpa.impl.entitymanager.PersistenceConfigurationProviderImpl
> does not pass it
> this simple override took care of it but I should not need to do it:
> {code:java}
> @ApplicationScoped
> @Alternative
> @Priority(Interceptor.Priority.APPLICATION + 10)
> public class CdiAwarePersistenceConfigurationProviderImpl extends
> PersistenceConfigurationProviderImpl implements
> PersistenceConfigurationProvider {
> @Inject BeanManager beanManager;
> @Override public Properties getEntityManagerFactoryConfiguration(String
> persistenceUnitName) {
> final Properties conf =
> super.getEntityManagerFactoryConfiguration(persistenceUnitName);
> conf.put("javax.persistence.bean.manager", beanManager);
> return conf;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1287) asList() getValue() fails with a NPE if no configured value exists
[ https://issues.apache.org/jira/browse/DELTASPIKE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145383#comment-16145383 ] ASF subversion and git services commented on DELTASPIKE-1287: - Commit 651c9a56937f8da2f92859bf5720362459bc3202 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=651c9a5 ] DELTASPIKE-1287 fix NullPointer in asList() handling > asList() getValue() fails with a NPE if no configured value exists > -- > > Key: DELTASPIKE-1287 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1287 > Project: DeltaSpike > Issue Type: Bug > Components: Configuration >Affects Versions: 1.8.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.1 > > > We currently blow up with a NullPointerException if a List gets resolved and > no value was actually configured. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1289) GlobalInterceptorExtension could reuse BeanManager
[ https://issues.apache.org/jira/browse/DELTASPIKE-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146804#comment-16146804 ] ASF subversion and git services commented on DELTASPIKE-1289: - Commit edeff80a283f124b395b19698b3bbf20db56c559 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=edeff80 ] DELTASPIKE-1289 move BeanManager injection to BeforeBeanDiscovery Slightly improves the performance to not need to resolve the BM for every annotated type. > GlobalInterceptorExtension could reuse BeanManager > -- > > Key: DELTASPIKE-1289 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1289 > Project: DeltaSpike > Issue Type: Improvement > Components: Core >Affects Versions: 1.8.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.1 > > > Currently the GlobalInterceptorExtension injects the BeanManager as part of > PAT. > That means that this injection point has to be resolved for every scanned > type. > We could as well store the BM away in BeforeBeanDiscovery and use that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1297) add test with a customized DynamicMockManager
[ https://issues.apache.org/jira/browse/DELTASPIKE-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227277#comment-16227277 ] ASF subversion and git services commented on DELTASPIKE-1297: - Commit 38bc9c3d340b17410b4fc2a1ce45d77981b366e5 in deltaspike's branch refs/heads/master from [~gpetracek] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=38bc9c3 ] DELTASPIKE-1297 added test with a customized DynamicMockManager > add test with a customized DynamicMockManager > - > > Key: DELTASPIKE-1297 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1297 > Project: DeltaSpike > Issue Type: Task > Components: TestControl >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1298) document customization of a DynamicMockManager
[ https://issues.apache.org/jira/browse/DELTASPIKE-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227310#comment-16227310 ] ASF subversion and git services commented on DELTASPIKE-1298: - Commit a95c0bc6f4b202648a7d9c87ca28a36ad3084e88 in deltaspike's branch refs/heads/master from [~gpetracek] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=a95c0bc ] DELTASPIKE-1298 initial hints about MockFilter and customizing the DynamicMockManager > document customization of a DynamicMockManager > -- > > Key: DELTASPIKE-1298 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1298 > Project: DeltaSpike > Issue Type: Task >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Minor > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1297) add test with a customized DynamicMockManager
[ https://issues.apache.org/jira/browse/DELTASPIKE-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227641#comment-16227641 ] ASF subversion and git services commented on DELTASPIKE-1297: - Commit d1316e517f743526c280c0dbd592f04310dfab10 in deltaspike's branch refs/heads/master from [~gpetracek] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d1316e5 ] DELTASPIKE-1297 added license header > add test with a customized DynamicMockManager > - > > Key: DELTASPIKE-1297 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1297 > Project: DeltaSpike > Issue Type: Task > Components: TestControl >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1302) ThreadPoolManager: ExecutorService map is always empty
[ https://issues.apache.org/jira/browse/DELTASPIKE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266020#comment-16266020 ] ASF subversion and git services commented on DELTASPIKE-1302: - Commit c4006cc3b5fda1eea5551fee5a0a7e15c19264d9 in deltaspike's branch refs/heads/fb/DELTASPIKE-1302_ThreadPoolManager-configuration from [~rmannibucau] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=c4006cc ] DELTASPIKE-1302 configuration for ThreadPoolManager > ThreadPoolManager: ExecutorService map is always empty > -- > > Key: DELTASPIKE-1302 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1302 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.0 >Reporter: Alonso Gonzalez >Priority: Minor > > ThreadPoolManager contains a ConcurrentHashMap that maps from a pool name to > an ExecutorService. Unfortunately the map never gets populated. It's always > empty. > I need this because I want to use a specific ExecutorService with @Futureable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1302) ThreadPoolManager: ExecutorService map is always empty
[ https://issues.apache.org/jira/browse/DELTASPIKE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266079#comment-16266079 ] ASF subversion and git services commented on DELTASPIKE-1302: - Commit c4006cc3b5fda1eea5551fee5a0a7e15c19264d9 in deltaspike's branch refs/heads/master from [~rmannibucau] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=c4006cc ] DELTASPIKE-1302 configuration for ThreadPoolManager > ThreadPoolManager: ExecutorService map is always empty > -- > > Key: DELTASPIKE-1302 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1302 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.0 >Reporter: Alonso Gonzalez >Priority: Minor > > ThreadPoolManager contains a ConcurrentHashMap that maps from a pool name to > an ExecutorService. Unfortunately the map never gets populated. It's always > empty. > I need this because I want to use a specific ExecutorService with @Futureable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1272) ConfigResolver asList breaks if no value is found
[
https://issues.apache.org/jira/browse/DELTASPIKE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266609#comment-16266609
]
ASF subversion and git services commented on DELTASPIKE-1272:
-
Commit 1174922e4fa438948bada8c9afe86952933fafc2 in deltaspike's branch
refs/heads/master from [~elexx]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=1174922 ]
DELTASPIKE-1272 / 1287: make defaultValues work
Signed-off-by: Mark Struberg
> ConfigResolver asList breaks if no value is found
> -
>
> Key: DELTASPIKE-1272
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1272
> Project: DeltaSpike
> Issue Type: Bug
> Components: Configuration
>Affects Versions: 1.8.0
>Reporter: Alexander Falb
>Assignee: Mark Struberg
> Fix For: 1.8.1
>
> Attachments: deltaspike.patch
>
>
> When calling
> {code:java}
> ConfigResolver.resolve("notexisting").as(Integer.class).asList().getValue();
> {code}
> a NullPointerException is thrown:
> {code}
> java.lang.NullPointerException
> at
> org.apache.deltaspike.core.api.config.ConfigResolver$PropertyBuilder.splitAndConvertListValue(ConfigResolver.java:1020)
> at
> org.apache.deltaspike.core.api.config.ConfigResolver$PropertyBuilder.getValue(ConfigResolver.java:988)
> {code}
> I created and attached a patch (including a few unit tests) to fix this
> issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1294) Secured Stereotypes are not applied to inherited methods
[
https://issues.apache.org/jira/browse/DELTASPIKE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266762#comment-16266762
]
ASF subversion and git services commented on DELTASPIKE-1294:
-
Commit b1903c2b3463dfa368d0fe973c72f2055c838bf6 in deltaspike's branch
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b1903c2 ]
DELTASPIKE-1294 fix SecurityBinding extraction
> Secured Stereotypes are not applied to inherited methods
>
>
> Key: DELTASPIKE-1294
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1294
> Project: DeltaSpike
> Issue Type: Bug
> Components: Security-Module
>Affects Versions: 1.8.0
>Reporter: Andrew Schmidt
>
> I have a @Secured @Stereotype annotation
> {code:java}
> @Retention( RUNTIME )
> @Stereotype
> @Inherited
> @Secured( CustomAccessDecisionVoter.class )
> @Target( { ElementType.TYPE, ElementType.METHOD } )
> public @interface Permission {
> }
> {code}
> And my decision voter:
> {code:java}
> @ApplicationScoped
> public class CustomAccessDecisionVoter extends AbstractAccessDecisionVoter {
> @Override
> protected void checkPermission( AccessDecisionVoterContext voterContext,
> Set violations )
> {
> System.out.println( "Checking permission for " +
> voterContext. getSource().getMethod().getName() );
> }
> }
> {code}
> And now a bean that inherits from another class
> {code:java}
> public class Animal
> {
> public String getParentName()
> {
> return "parent";
> }
> }
> {code}
> {code:java}
> @Named
> @Permission
> public class Dog extends Animal
> {
> public String getChildName()
> {
> return "dog";
> }
> }
> {code}
> In JSF dogName:
> {code}#{dog.childName}{code} will invoke the checkPermission whereas
> {code}#{dog.parentName}{code} will not
> This is in contrast to the @SecurityBindingType
> {code:java}
> @Retention( value = RetentionPolicy.RUNTIME )
> @Target( { ElementType.TYPE, ElementType.METHOD } )
> @Documented
> @SecurityBindingType
> public @interface UserLoggedIn {
> }
> {code}
> {code:java}
> @ApplicationScoped
> public class LoginAuthorizer
> {
> @Secures
> @UserLoggedIn
> public boolean doSecuredCheck( InvocationContext invocationContext )
> throws Exception
> {
> System.out.println( "doSecuredCheck called for: " +
> invocationContext.getMethod().getName() );
> return true;
> }
> }
> {code}
> Now applying @UserLoggedIn to the Dog class will cause the doSecuredCheck to
> fire for both getChildName and getParentName
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1296) PropertyFileConfig doesn't work with internal extensions
[ https://issues.apache.org/jira/browse/DELTASPIKE-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266915#comment-16266915 ] ASF subversion and git services commented on DELTASPIKE-1296: - Commit f0d56be8f4867908c39c1937fdf25fa8d8524c07 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=f0d56be ] DELTASPIKE-1296 move ConfigSource registration we now register PropertyFileConfig ConfigSources already in AfterBeanDiscovery and not in AfterDeploymentValidation. As requested by Romain > PropertyFileConfig doesn't work with internal extensions > > > Key: DELTASPIKE-1296 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1296 > Project: DeltaSpike > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Romain Manni-Bucau >Assignee: Mark Struberg > > We register PropertyFileConfig in AfterDeploymentValidation hook but > extensions potentially already read the config entries. Technically there is > probably no blocker to do it earlier and we should probably ensure all our > extensions read keys in AfterDeploymentValidation. > My use case was a configured cron expression in the scheduler usage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1278) PropertyFileConfig does not respect optional on external resources
[
https://issues.apache.org/jira/browse/DELTASPIKE-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266914#comment-16266914
]
ASF subversion and git services commented on DELTASPIKE-1278:
-
Commit 717771b275f406ce7ce43cd528be44d6053b7d2b in deltaspike's branch
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=717771b ]
DELTASPIKE-1278 avoid signature change
previously we did not throw the URISyntaxException which
is a checked Exception. So this change did require to catch
that exception in user code.
Now handling this issue internally.
> PropertyFileConfig does not respect optional on external resources
> --
>
> Key: DELTASPIKE-1278
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1278
> Project: DeltaSpike
> Issue Type: Bug
> Components: Configuration
>Affects Versions: 1.8.0
>Reporter: Dennis Rippinger
>Assignee: John D. Ament
> Fix For: 1.8.1
>
>
> Adding a property file from an external location (e.g. local file system)
> marked as optional is not respected by {{PropertyFileUtils}}. It creates a
> list of possible resource URLs, but does not check for their existence in all
> branches of its logic. This results in a list of possible nonexistent
> resources which could be optional, leading to an IllegalStateException.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1282) DeltaSpikeFacesContextWrapper leaks on TomEE
[ https://issues.apache.org/jira/browse/DELTASPIKE-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266913#comment-16266913 ] ASF subversion and git services commented on DELTASPIKE-1282: - Commit 77fa4b8653c525d631e462d148c3af5b368f8361 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=77fa4b8 ] DELTASPIKE-1282 support variables 4 String default > DeltaSpikeFacesContextWrapper leaks on TomEE > > > Key: DELTASPIKE-1282 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1282 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.8.0 >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1296) PropertyFileConfig doesn't work with internal extensions
[ https://issues.apache.org/jira/browse/DELTASPIKE-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270512#comment-16270512 ] ASF subversion and git services commented on DELTASPIKE-1296: - Commit 5685edbf58e42baa285198f9b6244d88b82ff7bf in deltaspike's branch refs/heads/master from [~rmannibucau] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=5685edb ] DELTASPIKE-1296 fixing configuration extension lifecycle > PropertyFileConfig doesn't work with internal extensions > > > Key: DELTASPIKE-1296 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1296 > Project: DeltaSpike > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Romain Manni-Bucau >Assignee: Mark Struberg > > We register PropertyFileConfig in AfterDeploymentValidation hook but > extensions potentially already read the config entries. Technically there is > probably no blocker to do it earlier and we should probably ensure all our > extensions read keys in AfterDeploymentValidation. > My use case was a configured cron expression in the scheduler usage. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1303) @Configuration proxies should support List without converters
[ https://issues.apache.org/jira/browse/DELTASPIKE-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270556#comment-16270556 ] ASF subversion and git services commented on DELTASPIKE-1303: - Commit 7b55ff21da633b11ac84a6526fce0b64473ca669 in deltaspike's branch refs/heads/master from [~rmannibucau] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=7b55ff2 ] DELTASPIKE-1303 List/Set support for @Configuration proxy based interfaces > @Configuration proxies should support List without converters > - > > Key: DELTASPIKE-1303 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1303 > Project: DeltaSpike > Issue Type: Bug >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1294) Secured Stereotypes are not applied to inherited methods
[
https://issues.apache.org/jira/browse/DELTASPIKE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271009#comment-16271009
]
ASF subversion and git services commented on DELTASPIKE-1294:
-
Commit 126362e4f049976b6b14a8cd627add1029321148 in deltaspike's branch
refs/heads/master from [~gpetracek]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=126362e ]
DELTASPIKE-1294 improvements in view of proxies and extensibility
> Secured Stereotypes are not applied to inherited methods
>
>
> Key: DELTASPIKE-1294
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1294
> Project: DeltaSpike
> Issue Type: Bug
> Components: Security-Module
>Affects Versions: 1.8.0
>Reporter: Andrew Schmidt
>Assignee: Mark Struberg
> Fix For: 1.8.1
>
>
> I have a @Secured @Stereotype annotation
> {code:java}
> @Retention( RUNTIME )
> @Stereotype
> @Inherited
> @Secured( CustomAccessDecisionVoter.class )
> @Target( { ElementType.TYPE, ElementType.METHOD } )
> public @interface Permission {
> }
> {code}
> And my decision voter:
> {code:java}
> @ApplicationScoped
> public class CustomAccessDecisionVoter extends AbstractAccessDecisionVoter {
> @Override
> protected void checkPermission( AccessDecisionVoterContext voterContext,
> Set violations )
> {
> System.out.println( "Checking permission for " +
> voterContext. getSource().getMethod().getName() );
> }
> }
> {code}
> And now a bean that inherits from another class
> {code:java}
> public class Animal
> {
> public String getParentName()
> {
> return "parent";
> }
> }
> {code}
> {code:java}
> @Named
> @Permission
> public class Dog extends Animal
> {
> public String getChildName()
> {
> return "dog";
> }
> }
> {code}
> In JSF dogName:
> {code}#{dog.childName}{code} will invoke the checkPermission whereas
> {code}#{dog.parentName}{code} will not
> This is in contrast to the @SecurityBindingType
> {code:java}
> @Retention( value = RetentionPolicy.RUNTIME )
> @Target( { ElementType.TYPE, ElementType.METHOD } )
> @Documented
> @SecurityBindingType
> public @interface UserLoggedIn {
> }
> {code}
> {code:java}
> @ApplicationScoped
> public class LoginAuthorizer
> {
> @Secures
> @UserLoggedIn
> public boolean doSecuredCheck( InvocationContext invocationContext )
> throws Exception
> {
> System.out.println( "doSecuredCheck called for: " +
> invocationContext.getMethod().getName() );
> return true;
> }
> }
> {code}
> Now applying @UserLoggedIn to the Dog class will cause the doSecuredCheck to
> fire for both getChildName and getParentName
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1304) Make CdiTestRunner use "flat" deployment on Weld by default
[
https://issues.apache.org/jira/browse/DELTASPIKE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272433#comment-16272433
]
ASF subversion and git services commented on DELTASPIKE-1304:
-
Commit 390d270cca6b300ab3f617ba4e61a69029952227 in deltaspike's branch
refs/heads/master from [~manovotn]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=390d270 ]
DELTASPIKE-1304 CdiTestRunner will not use flat deployment for Weld.
> Make CdiTestRunner use "flat" deployment on Weld by default
> ---
>
> Key: DELTASPIKE-1304
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1304
> Project: DeltaSpike
> Issue Type: Improvement
>Reporter: Matej Novotny
>Assignee: Matej Novotny
> Fix For: 1.8.1
>
>
> In Weld 1 this was a default behaviour, with Weld 2 and onwards, this changed
> but is still configurable.
> Since DS depends on Weld 1.x API, there is no option to configure this via
> {{org.jboss.weld.environment.se.Weld}}, but it can still be done via system
> property.
> Flat deployment would eliminate some test problems as, for instance, custom
> {{MockManager}}. Namely
> [{{CustomMockManager}}|https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/impl/src/test/java/org/apache/deltaspike/test/testcontrol/CustomMockManager.java]
> and the test linked to it which breaks all tests in that module for Weld.
> The reason is that it uses {{beans.xml}} to enable alternatives, which in
> Weld only works for given bean archive (e.g. this leads to eternal Holy Bean
> Archive War between Weld and OWB interpretations :) ).
> Swapping the test runner behaviour with Weld shouldn't cause any harm as this
> is unit test level and the "flatness" doesn't really matter there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1302) ThreadPoolManager: ExecutorService map is always empty
[ https://issues.apache.org/jira/browse/DELTASPIKE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272712#comment-16272712 ] ASF subversion and git services commented on DELTASPIKE-1302: - Commit e10e8863afcaeafc37c0d1184fb6d8058a68d081 in deltaspike's branch refs/heads/master from [~manovotn] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=e10e886 ] DELTASPIKE-1302 Fix test deployment archive. > ThreadPoolManager: ExecutorService map is always empty > -- > > Key: DELTASPIKE-1302 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1302 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.0 >Reporter: Alonso Gonzalez >Priority: Minor > > ThreadPoolManager contains a ConcurrentHashMap that maps from a pool name to > an ExecutorService. Unfortunately the map never gets populated. It's always > empty. > I need this because I want to use a specific ExecutorService with @Futureable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers
[
https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274489#comment-16274489
]
ASF subversion and git services commented on DELTASPIKE-940:
Commit 51eceaec9ccd7993bda8ebb7f92a4ef19417733a in deltaspike's branch
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=51eceae ]
DELTASPIKE-940 - Fixed missing third case of default resolution. Ensure that
the entity manager is resolved.
> @Transactional and @EntityManagerConfig each use a different method to
> resolve EntityManagers
> -
>
> Key: DELTASPIKE-940
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module, JPA-Module
>Reporter: Xavier Dury
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.1
>
> Attachments: ds940.patch
>
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to
> specify which one(s) should be used. Currently, {{@Transactional}} and
> {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its
> {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}}
> ({{@EntityManagerConfig(entityManagerResolver =
> MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which
> {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks
> better and should be applied to {{@EntityManagerConfig}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1305) Multiple ds:windowId leads to multiple redirects
[ https://issues.apache.org/jira/browse/DELTASPIKE-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296514#comment-16296514 ] ASF subversion and git services commented on DELTASPIKE-1305: - Commit 1509247730cbe639bdf51e0d886823f7bba90cf5 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=1509247 ] DELTASPIKE-1305, DELTASPIKE-1306: improved window handling on IE and avoid multiple init > Multiple ds:windowId leads to multiple redirects > > > Key: DELTASPIKE-1305 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1305 > Project: DeltaSpike > Issue Type: Bug >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1306) IE sometimes doesn't set window.name correctly
[ https://issues.apache.org/jira/browse/DELTASPIKE-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296515#comment-16296515 ] ASF subversion and git services commented on DELTASPIKE-1306: - Commit 1509247730cbe639bdf51e0d886823f7bba90cf5 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=1509247 ] DELTASPIKE-1305, DELTASPIKE-1306: improved window handling on IE and avoid multiple init > IE sometimes doesn't set window.name correctly > -- > > Key: DELTASPIKE-1306 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1306 > Project: DeltaSpike > Issue Type: Bug >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1307) Deltaspike JSF: XSS WindowIdHtmlRenderer.java
[ https://issues.apache.org/jira/browse/DELTASPIKE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299078#comment-16299078 ] ASF subversion and git services commented on DELTASPIKE-1307: - Commit 4e2502358526b944fc5514c206d306e97ff271bb in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=4e25023 ] DELTASPIKE-1307 escape windowId txs to md for the catch! > Deltaspike JSF: XSS WindowIdHtmlRenderer.java > - > > Key: DELTASPIKE-1307 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1307 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.8.0 > Environment: any >Reporter: md >Assignee: Mark Struberg >Priority: Blocker > Labels: security > > 10 chars ough to be enough for XSS. > Try escaping your variables. > https://github.com/apache/deltaspike/blob/master/deltaspike/modules/jsf/impl/src/main/java/org/apache/deltaspike/jsf/impl/component/window/WindowIdHtmlRenderer.java > Line 80 > PoC > dswid='-open()-' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1307) Deltaspike JSF: XSS WindowIdHtmlRenderer.java
[ https://issues.apache.org/jira/browse/DELTASPIKE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299906#comment-16299906 ] ASF subversion and git services commented on DELTASPIKE-1307: - Commit 72e607f3be66c30c72b32c24b44e9deaa8e54608 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=72e607f ] DELTASPIKE-1307 sanitise windowId against JavaScript injection > Deltaspike JSF: XSS WindowIdHtmlRenderer.java > - > > Key: DELTASPIKE-1307 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1307 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.8.0 > Environment: any >Reporter: md >Assignee: Mark Struberg >Priority: Blocker > Labels: security > > 10 chars ough to be enough for XSS. > Try escaping your variables. > https://github.com/apache/deltaspike/blob/master/deltaspike/modules/jsf/impl/src/main/java/org/apache/deltaspike/jsf/impl/component/window/WindowIdHtmlRenderer.java > Line 80 > PoC > dswid='-open()-' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1307) Deltaspike JSF: XSS WindowIdHtmlRenderer.java
[ https://issues.apache.org/jira/browse/DELTASPIKE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306701#comment-16306701 ] ASF subversion and git services commented on DELTASPIKE-1307: - Commit d95abe8c01d256da2ce0a5a88f4593138156a4e5 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d95abe8 ] DELTASPIKE-1307 improve sanitise windowId Also guard against html injection > Deltaspike JSF: XSS WindowIdHtmlRenderer.java > - > > Key: DELTASPIKE-1307 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1307 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 1.8.0 > Environment: any >Reporter: md >Assignee: Mark Struberg >Priority: Blocker > Labels: security > > 10 chars ough to be enough for XSS. > Try escaping your variables. > https://github.com/apache/deltaspike/blob/master/deltaspike/modules/jsf/impl/src/main/java/org/apache/deltaspike/jsf/impl/component/window/WindowIdHtmlRenderer.java > Line 80 > PoC > dswid='-open()-' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1299) Order by items are applied in alphabetic order
[
https://issues.apache.org/jira/browse/DELTASPIKE-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306860#comment-16306860
]
ASF subversion and git services commented on DELTASPIKE-1299:
-
Commit 2c4c80d65984648437dcd602f2ba57f9deca91f6 in deltaspike's branch
refs/heads/master from [~Mobe]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=2c4c80d ]
DELTASPIKE-1299: fixed orderby item order
> Order by items are applied in alphabetic order
> --
>
> Key: DELTASPIKE-1299
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1299
> Project: DeltaSpike
> Issue Type: Bug
> Components: Data-Module
>Affects Versions: 1.8.0
>Reporter: Moritz Becker
> Fix For: 1.8.1
>
>
> DeltaSpike data applies the order bys in parsed methods in alphabetic order
> which leads to semantically incorrect queries.
> For example, the method {{findAllOrderByNameAscIdDesc}} produces the
> following query:
> {code:sql}
> select * from ... order by id desc, name asc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1310) Please use https (SSL) for links to KEYS, hashes, sigs
[ https://issues.apache.org/jira/browse/DELTASPIKE-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311375#comment-16311375 ] ASF subversion and git services commented on DELTASPIKE-1310: - Commit 21caa8c901080335a0ef849c55192f129d2c2dad in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=21caa8c ] DELTASPIKE-1310 use https only and fix gpg usage sample txs to sebb for the report! > Please use https (SSL) for links to KEYS, hashes, sigs > --- > > Key: DELTASPIKE-1310 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1310 > Project: DeltaSpike > Issue Type: Bug > Environment: https://deltaspike.apache.org/download.html >Reporter: Sebb > > As the subject says: Please use https (SSL) for links to KEYS, hashes, sigs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1310) Please use https (SSL) for links to KEYS, hashes, sigs
[ https://issues.apache.org/jira/browse/DELTASPIKE-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311382#comment-16311382 ] ASF subversion and git services commented on DELTASPIKE-1310: - Commit 5e0ab99fcc10c2c4fbd1bdb29cbddbe0b2a5fe09 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=5e0ab99 ] DELTASPIKE-1310 also add link to ASF check signature page txs to sebb again! > Please use https (SSL) for links to KEYS, hashes, sigs > --- > > Key: DELTASPIKE-1310 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1310 > Project: DeltaSpike > Issue Type: Bug > Environment: https://deltaspike.apache.org/download.html >Reporter: Sebb > > As the subject says: Please use https (SSL) for links to KEYS, hashes, sigs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1312) Upgrade to quartz-2.3.0
[ https://issues.apache.org/jira/browse/DELTASPIKE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313763#comment-16313763 ] ASF subversion and git services commented on DELTASPIKE-1312: - Commit fc8b80bd0adb6ba46c8ae6f40a20bc08e2adacff in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=fc8b80b ] DELTASPIKE-1312 update Quartz to 2.3.0 to disable the http phoning-home which is now opt-in > Upgrade to quartz-2.3.0 > --- > > Key: DELTASPIKE-1312 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1312 > Project: DeltaSpike > Issue Type: Task > Components: Scheduler >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.2 > > > Quartz-2.2.1 automatially performs http calls to look for updates. This is > quite nasty. > In 2.3.0 they changed this to an opt-in mechanism. > So we should really update to this version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1313) DeltaSpikeProxyInterceptorLookup fails on WAS
[ https://issues.apache.org/jira/browse/DELTASPIKE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319068#comment-16319068 ] ASF subversion and git services commented on DELTASPIKE-1313: - Commit 83053ca9af909a05114b1c1c51df005785daee52 in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=83053ca ] DELTASPIKE-1313 DeltaSpikeProxyInterceptorLookup fails on WAS > DeltaSpikeProxyInterceptorLookup fails on WAS > - > > Key: DELTASPIKE-1313 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1313 > Project: DeltaSpike > Issue Type: Bug > Components: Data-Module, PartialBean >Affects Versions: 1.8.1 >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.2 > > > as it's package private -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1309) Upgrade ASM
[ https://issues.apache.org/jira/browse/DELTASPIKE-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319116#comment-16319116 ] ASF subversion and git services commented on DELTASPIKE-1309: - Commit 028ec5bf37a6122f9c93a93141dba043f6c1875e in deltaspike's branch refs/heads/master from [~tandraschko] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=028ec5b ] DELTASPIKE-1309 Upgrade ASM + renamed directories > Upgrade ASM > --- > > Key: DELTASPIKE-1309 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1309 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module, PartialBean, Proxy-Module >Reporter: Thomas Andraschko >Assignee: Thomas Andraschko > Fix For: 1.8.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358974#comment-16358974 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit 2c185bd5f02ea842b9d2f4628a7204c0453eec0d in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=2c185bd ] DELTASPIKE-1316 add InterDynExtension this allows to configurably add annotations to classes identified via a regexp. > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358977#comment-16358977 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit 0a914ba3cd05f9a74ce19c7843f56445fa2a932c in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=0a914ba ] DELTASPIKE-1316 activate InterDynExtension > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358976#comment-16358976 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit 9423d7466d9507bc243ca3e7bea5a97986bd3bb6 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=9423d74 ] DELTASPIKE-1316 add @InvocationMonitored wip, still misses tests > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358975#comment-16358975 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit 8cc2a7f6853c32e49d7aa93176b667502ce74f7c in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=8cc2a7f ] DELTASPIKE-1316 skip interdyn with empty match or class config > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358978#comment-16358978 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit 3734100febf7895923028a5ef836027eed2015c0 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=3734100 ] DELTASPIKE-1316 add unit test and enable interceptor > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374194#comment-16374194 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit 1f19c0e210dc3d22c5429b09985b2d6deb9f3340 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=1f19c0e ] DELTASPIKE-1316 skip non-proxyable classes from being annotated. > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1317) AnnotatedCallableImpl blows up with ArrayOutofBounds when parsing enums
[ https://issues.apache.org/jira/browse/DELTASPIKE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374193#comment-16374193 ] ASF subversion and git services commented on DELTASPIKE-1317: - Commit b5f94113b15716e7fed81ea643f3948040079422 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b5f9411 ] DELTASPIKE-1317 workaround for getGenericParameter returning wrong amount of params This happens in rare situations. Still not sure whether this is by spec, whether it is a JVM bug or whether it is simply an undefined edge case. We need to investigate further. At least ne now don't blow up anymore > AnnotatedCallableImpl blows up with ArrayOutofBounds when parsing enums > --- > > Key: DELTASPIKE-1317 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1317 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > It seems like constructor#getParameterTypes() and getGenericParameterTypes() > return a different number of parameters for enums. > > There is already a rudimentary workaround in place, but that seems not to be > enough. > > We need to dig deeper why this happens. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374195#comment-16374195 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit 1c3a16be161eb2e994df5454f7de3335c3ca1246 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=1c3a16b ] DELTASPIKE-1316 only perform the proxaable check for interceptor annotations > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1319) labeled alternatives
[ https://issues.apache.org/jira/browse/DELTASPIKE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379196#comment-16379196 ] ASF subversion and git services commented on DELTASPIKE-1319: - Commit 036c8e95e36e57f0fd5c7b4c6a1946ad27f1367a in deltaspike's branch refs/heads/master from [~gpetracek] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=036c8e9 ] DELTASPIKE-1319 labeled alternatives > labeled alternatives > > > Key: DELTASPIKE-1319 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1319 > Project: DeltaSpike > Issue Type: New Feature > Components: Core, TestControl >Affects Versions: 1.8.1 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > Fix For: 1.8.2 > > Attachments: DELTASPIKE_1319_first_draft__without_spi_.patch > > > target setup: ds-testcontrol as well as containers like meecrowave which > support one instance per test-class, but deploy the whole application. > in several cases it's essential to bind alternative beans only to a subset of > all tests. > currently we just support that partially via the mock-support (which is very > limited in several cases). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1320) global alternative spi to support custom (type-safe) mechanisms
[ https://issues.apache.org/jira/browse/DELTASPIKE-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379197#comment-16379197 ] ASF subversion and git services commented on DELTASPIKE-1320: - Commit 7177eda1fa84d3e2db4119c74d470e5c344133bf in deltaspike's branch refs/heads/master from [~gpetracek] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=7177eda ] DELTASPIKE-1320 spi for global-alternatives > global alternative spi to support custom (type-safe) mechanisms > --- > > Key: DELTASPIKE-1320 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1320 > Project: DeltaSpike > Issue Type: New Feature > Components: Core >Affects Versions: 1.8.1 >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > Fix For: 1.8.2 > > Attachments: DELTASPIKE_1320_first_draft.patch > > > in combination with DELTASPIKE-1319 it should be possible to implement e.g. > type-safe labels based on binding-annotations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1316) add dynamic annotations feature, configurable via config
[ https://issues.apache.org/jira/browse/DELTASPIKE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381535#comment-16381535 ] ASF subversion and git services commented on DELTASPIKE-1316: - Commit f06a78939a6c448717856db21c8a33565d450402 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=f06a789 ] DELTASPIKE-1316 fix broken test on Wildfly9 > add dynamic annotations feature, configurable via config > > > Key: DELTASPIKE-1316 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1316 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.8.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.8.2 > > > A long time ago I created a CDI Extension which can dynamically add > annotations to classes identified via a regular expression. > The Extension is called InterDyn (Interceptor Dynamics) and is hosted at > github. > [https://github.com/struberg/InterDyn] > > I'm the sole originary author, so I have all the IP. > The project actually consists of two parts: InterDyn for dynamic interceptors > and InvoMon, an invocation monitor interceptor. Kind of small man profiler. > The InterDyn part is actually not restricted to add interceptor annotations, > but really could be anything. But adding interceptors obviously makes the > most sense. This should go into ds-core-impl. It doesn't even need any api > changes. > > The 2nd part (the performance InvocationMonitor. Might become either part of > core, or a separate module. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1321) Upgrade DeltaSpike to require Java8 as minimum version
[ https://issues.apache.org/jira/browse/DELTASPIKE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381605#comment-16381605 ] ASF subversion and git services commented on DELTASPIKE-1321: - Commit b76cc1c64b511955b1adde53e446fb769e739a5b in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b76cc1c ] DELTASPIKE-1321 upping to 1.9.x version range > Upgrade DeltaSpike to require Java8 as minimum version > -- > > Key: DELTASPIKE-1321 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1321 > Project: DeltaSpike > Issue Type: New Feature > Components: Build >Affects Versions: 1.9.0 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.0 > > > We will update our build to require Java8 as minimum. > This happens starting with DeltaSpike-1.9.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DELTASPIKE-1321) Upgrade DeltaSpike to require Java8 as minimum version
[ https://issues.apache.org/jira/browse/DELTASPIKE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381606#comment-16381606 ] ASF subversion and git services commented on DELTASPIKE-1321: - Commit b8bac26e9eff1d912ee79b831eee2b8094005c1f in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=b8bac26 ] DELTASPIKE-1321 upgrade to Java8 as minimum version > Upgrade DeltaSpike to require Java8 as minimum version > -- > > Key: DELTASPIKE-1321 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1321 > Project: DeltaSpike > Issue Type: New Feature > Components: Build >Affects Versions: 1.9.0 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.0 > > > We will update our build to require Java8 as minimum. > This happens starting with DeltaSpike-1.9.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
