[jira] [Updated] (DELTASPIKE-1264) Remove portions of BeanProvider/BeanManagerProvider
[ https://issues.apache.org/jira/browse/DELTASPIKE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated DELTASPIKE-1264: -- Fix Version/s: 2.0.1 (was: 2.0.0) > Remove portions of BeanProvider/BeanManagerProvider > --- > > Key: DELTASPIKE-1264 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1264 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.1 > > > These internal utilities may not be needed based on CDI.current() from CDI > 1.1. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1206) support for CDI 2.0 feature
[ https://issues.apache.org/jira/browse/DELTASPIKE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1206. --- Resolution: Fixed Finally activated the feature in our beans.xml in DS 2.0.0. This will speed up class parsing and bring down mem consumption a bit. > support for CDI 2.0 feature > --- > > Key: DELTASPIKE-1206 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1206 > Project: DeltaSpike > Issue Type: Test >Affects Versions: 1.7.1 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.0 > > > CDI 2.0 will add support for only picking up beans with an explicit scope > annotation. This reduced the memory footprint while also speeding up the > bootstrapping. > See https://issues.jboss.org/browse/CDI-420 > We should add this annotation to our beans.xml and verify that we still work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DELTASPIKE-1457) Improve Config Interface
[
https://issues.apache.org/jira/browse/DELTASPIKE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated DELTASPIKE-1457:
--
Fix Version/s: 2.0.1
(was: 2.0.0)
> Improve Config Interface
>
>
> Key: DELTASPIKE-1457
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1457
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.6
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0.1
>
>
> We should gradually improve our Config Interface, e.g. move
> {{getAllProperties}} over, introduce more type handling, automatic (implicit)
> Converters, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
[ https://issues.apache.org/jira/browse/DELTASPIKE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1437. --- Assignee: Mark Struberg Resolution: Fixed > DeltaSpike-2.0 umbrella ticket > -- > > Key: DELTASPIKE-1437 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.0 > > > This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DELTASPIKE-1455) Allow to pass properties to Weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated DELTASPIKE-1455: -- Fix Version/s: 2.0.0 (was: 1.9.7) > Allow to pass properties to Weld > > > Key: DELTASPIKE-1455 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: CdiControl >Affects Versions: 1.9.6 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 2.0.0 > > > See PR > https://github.com/apache/deltaspike/pull/129 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1460) Move outdated APIs
[ https://issues.apache.org/jira/browse/DELTASPIKE-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1460. --- Resolution: Fixed > Move outdated APIs > -- > > Key: DELTASPIKE-1460 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1460 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Gerhard Petracek >Assignee: Gerhard Petracek >Priority: Major > Fix For: 2.0.0 > > > some parts of the api aren't needed with cdi 2.0+ > therefore that parts should be moved until they get removed completely. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DELTASPIKE-1456) Introduce default methods for some functions in ConfigSource
[
https://issues.apache.org/jira/browse/DELTASPIKE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated DELTASPIKE-1456:
--
Fix Version/s: 2.0.0
(was: 1.9.7)
> Introduce default methods for some functions in ConfigSource
>
>
> Key: DELTASPIKE-1456
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1456
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.6
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0.0
>
>
> Right now our {{ConfigSource}} interface is still mostly an old Java6
> interface. We already use a default method for the onChange callback
> registration. We could also provide some other default methods, e.g. for
> {{getOrdinal()}} and {{isScannable().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DELTASPIKE-1457) Improve Config Interface
[
https://issues.apache.org/jira/browse/DELTASPIKE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated DELTASPIKE-1457:
--
Fix Version/s: 2.0.0
(was: 1.9.7)
> Improve Config Interface
>
>
> Key: DELTASPIKE-1457
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1457
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.6
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0.0
>
>
> We should gradually improve our Config Interface, e.g. move
> {{getAllProperties}} over, introduce more type handling, automatic (implicit)
> Converters, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (DELTASPIKE-1458) DefaultConfigSourceProvider cannot be instantiated
[
https://issues.apache.org/jira/browse/DELTASPIKE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated DELTASPIKE-1458:
--
Fix Version/s: 2.0.0
(was: 1.9.7)
> DefaultConfigSourceProvider cannot be instantiated
> --
>
> Key: DELTASPIKE-1458
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1458
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
>Reporter: Michael Heydemann
>Priority: Major
> Fix For: 2.0.0
>
>
> Hello,
> I am trying to use the deltaspike test module (CdiTestRunner) in a Jakarta
> environment. Therefore for some of the dependencies I added the jakarta
> classifier. The test then fails with an exception. For demonstration purose I
> reduced the project to the necessary:
> I get this stack trace during test execution:
> {code:java}
> java.util.ServiceConfigurationError:
> org.apache.deltaspike.core.spi.config.ConfigSourceProvider: Provider
> org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider could not
> be instantiated
> at java.util.ServiceLoader.fail(ServiceLoader.java:232)
> at java.util.ServiceLoader.access$100(ServiceLoader.java:185)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:384)
> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
> at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
> at
> org.apache.deltaspike.core.util.ServiceUtils.loadServiceImplementations(ServiceUtils.java:81)
> at org.apache.deltaspike.core.impl.config.ConfigImpl.init(ConfigImpl.java:80)
> at
> org.apache.deltaspike.core.impl.config.ConfigProviderImpl.getConfig(ConfigProviderImpl.java:53)
> at
> org.apache.deltaspike.core.impl.config.ConfigProviderImpl.getConfig(ConfigProviderImpl.java:43)
> at
> org.apache.deltaspike.core.api.config.ConfigResolver.resolve(ConfigResolver.java:655)
> at
> org.apache.deltaspike.testcontrol.api.junit.TestBaseConfig$ContainerIntegration.(TestBaseConfig.java:29)
> at
> org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.(CdiTestRunner.java:89)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> Caused by: java.lang.NoClassDefFoundError: jakarta/naming/NamingException
> at
> org.apache.deltaspike.core.impl.config.LocalJndiConfigSource.getPropertyValue(LocalJndiConfigSource.java:53)
> at
> org.apache.deltaspike.core.impl.config.BaseConfigSource.initOrdinal(BaseConfigSource.java:54)
> at
> org.apache.deltaspike.core.impl.config.LocalJndiConfigSource.(LocalJndiConfigSource.java:39)
> at
> org.apache.deltaspike.core.impl.config.DefaultConfigSourceProvider.(DefaultConfigSourceProvider.java:59)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380)
> ... 26 more
> Caused by: java.lang.ClassNotFoundException: jakarta.naming.NamingException
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> ... 36 more{code}
>
> Here the pom.xml:
> {code:java}
>xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;
> xmlns="http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
> 4.0.0
> org.example.cdi.test
> cdi-test
> 1.0.0-SNAPSHOT
> jar
>
> 1.9.6
>
>
>
> org.apache.deltaspike.modules
> deltaspike-test-control-module-api
> ${deltaspike.version}
> jakarta
> test
>
>
> org.apache.deltaspike.modules
> deltaspike-test-control-module-impl
> ${deltaspike.version}
> jakarta
> test
>
>
> org.apache.deltaspike.cdictrl
> deltaspike-cdictrl-weld
> ${deltaspike.version}
> jakarta
> test
>
>
> org.jboss.weld.se
> weld-se-core
> 4.0.0.Alpha3
> test
>
>
> junit
> junit
> 4.12
> test
>
>
>
> {code}
>
> And the empty test I would like to execute:
> {code:java}
> import org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner;
> import org.junit.Test;
> import org.junit.runner.RunWith;
> @RunWith(CdiTestRunner.class)
> public class CdiTest {
> @Test
> public void test() {}
> }
> {code}
>
> I hope you can help me with this.
> Best Regrads,
> Michael
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1456) Introduce default methods for some functions in ConfigSource
[
https://issues.apache.org/jira/browse/DELTASPIKE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1456.
---
Resolution: Fixed
> Introduce default methods for some functions in ConfigSource
>
>
> Key: DELTASPIKE-1456
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1456
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.6
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.7
>
>
> Right now our {{ConfigSource}} interface is still mostly an old Java6
> interface. We already use a default method for the onChange callback
> registration. We could also provide some other default methods, e.g. for
> {{getOrdinal()}} and {{isScannable().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1466) move beans.xml to CDI-3.0 style
[
https://issues.apache.org/jira/browse/DELTASPIKE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1466.
---
Resolution: Fixed
> move beans.xml to CDI-3.0 style
> ---
>
> Key: DELTASPIKE-1466
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1466
> Project: DeltaSpike
> Issue Type: Sub-task
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 2.0
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0
>
>
> Since we now target EE9 at least we also have to update our beans.xml.
> This has mainly to do with CDI-4.0 in JakartaEE10 re-defined the behaviour of
> empty beans.xml files from bean-discovery-mode "all" to "annotated", breaking
> tons of existing code.
> To prevent any behaviour changes for DeltaSpike users we now explicitly
> define a {{bean-discovery-mode}} ourselfs. And we also leverage the
> {{}} modus of CDI-2.0.
> bean-discovery-mode "all" + has the effect that all classes which are
> CDI candidates get scanned and a {{ProcessAnnotatedType}} event gets fired.
> But with the mode we ONLY create beans for AnnotatedTypes which are
> explicitly defined. This is a good compromise between being able to scan all
> classes via CDI Extensions but still not getting any superfluous CDI beans as
> automatically {{@Dependent}} scoped beans
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (DELTASPIKE-1466) move beans.xml to CDI-3.0 style
Mark Struberg created DELTASPIKE-1466:
-
Summary: move beans.xml to CDI-3.0 style
Key: DELTASPIKE-1466
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1466
Project: DeltaSpike
Issue Type: Sub-task
Security Level: public (Regular issues)
Components: Core
Affects Versions: 2.0
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 2.0
Since we now target EE9 at least we also have to update our beans.xml.
This has mainly to do with CDI-4.0 in JakartaEE10 re-defined the behaviour of
empty beans.xml files from bean-discovery-mode "all" to "annotated", breaking
tons of existing code.
To prevent any behaviour changes for DeltaSpike users we now explicitly define
a {{bean-discovery-mode}} ourselfs. And we also leverage the {{}} modus
of CDI-2.0.
bean-discovery-mode "all" + has the effect that all classes which are
CDI candidates get scanned and a {{ProcessAnnotatedType}} event gets fired. But
with the mode we ONLY create beans for AnnotatedTypes which are
explicitly defined. This is a good compromise between being able to scan all
classes via CDI Extensions but still not getting any superfluous CDI beans as
automatically {{@Dependent}} scoped beans
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1465) print ConfigSource of the values for deltaspike.config.log
[
https://issues.apache.org/jira/browse/DELTASPIKE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1465.
---
Resolution: Fixed
> print ConfigSource of the values for deltaspike.config.log
> --
>
> Key: DELTASPIKE-1465
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1465
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 2.0
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 2.0
>
>
> When using the configuration {code}deltaspike.config.log=true{code}
> DeltaSpike prints the resolved configuraiton at startup. Right now this
> contains the list of ConfigSources and all configured keys plus their values.
> This could be further enhanced by also printing the ConfigSource from which
> the value finally got picked up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (DELTASPIKE-1465) print ConfigSource of the values for deltaspike.config.log
Mark Struberg created DELTASPIKE-1465:
-
Summary: print ConfigSource of the values for deltaspike.config.log
Key: DELTASPIKE-1465
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1465
Project: DeltaSpike
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Configuration
Affects Versions: 2.0
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 2.0
When using the configuration {code}deltaspike.config.log=true{code} DeltaSpike
prints the resolved configuraiton at startup. Right now this contains the list
of ConfigSources and all configured keys plus their values.
This could be further enhanced by also printing the ConfigSource from which the
value finally got picked up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681449#comment-17681449 ] Mark Struberg commented on DELTASPIKE-1434: --- Romain is correct. Right now I'm investigating this. Eclipse Jakarta rules actually forbid such changes. Some of them nonetheless sneaked into the CDI-4.0 specification. Otoh there are a few APIs which were deprecated in older CDI versions already and now got pruned. Those changes are fine and we need to update our code To your last question [~mcollovati] : yes, we plan to do a Jakarta10 version. Think this is really worth it to be the target for our next major release. Btw this has nothing to do with OpenWebBeans. OWB-4.0.x is CDI-4.0 as well. > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1448) Deltaspike fails with weld 3.1.7+
[ https://issues.apache.org/jira/browse/DELTASPIKE-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573467#comment-17573467 ] Mark Struberg commented on DELTASPIKE-1448: --- Cool, thank you, looking forward to it! > Deltaspike fails with weld 3.1.7+ > - > > Key: DELTASPIKE-1448 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1448 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Jeremy Landis >Assignee: Mark Struberg >Priority: Major > > See [https://issues.redhat.com/browse/WELD-2669] > > Since weld 3.1.7, proxy changed. deltaspike does not work. Using jdk 11 and > now jdk 17. Projects without deltaspike work fine. This issue presents > itself only with deltaspike usage. Please confirm that deltaspike works with > recent version as weld keeps moving but deltaspike seems tuck in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DELTASPIKE-1457) Improve Config Interface
Mark Struberg created DELTASPIKE-1457:
-
Summary: Improve Config Interface
Key: DELTASPIKE-1457
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1457
Project: DeltaSpike
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Configuration
Affects Versions: 1.9.6
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 1.9.7
We should gradually improve our Config Interface, e.g. move
{{getAllProperties}} over, introduce more type handling, automatic (implicit)
Converters, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (DELTASPIKE-1448) Deltaspike fails with weld 3.1.7+
[ https://issues.apache.org/jira/browse/DELTASPIKE-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572875#comment-17572875 ] Mark Struberg commented on DELTASPIKE-1448: --- Opps just saw this now. This should be fixed with your PR commit #7852b3076d7418e11fb9420ac27265a0c9ab4a07, right? Thanks again for your contributions! > Deltaspike fails with weld 3.1.7+ > - > > Key: DELTASPIKE-1448 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1448 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Jeremy Landis >Assignee: Mark Struberg >Priority: Major > > See [https://issues.redhat.com/browse/WELD-2669] > > Since weld 3.1.7, proxy changed. deltaspike does not work. Using jdk 11 and > now jdk 17. Projects without deltaspike work fine. This issue presents > itself only with deltaspike usage. Please confirm that deltaspike works with > recent version as weld keeps moving but deltaspike seems tuck in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1448) Deltaspike fails with weld 3.1.7+
[ https://issues.apache.org/jira/browse/DELTASPIKE-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1448. --- Resolution: Resolved > Deltaspike fails with weld 3.1.7+ > - > > Key: DELTASPIKE-1448 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1448 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Jeremy Landis >Assignee: Mark Struberg >Priority: Major > > See [https://issues.redhat.com/browse/WELD-2669] > > Since weld 3.1.7, proxy changed. deltaspike does not work. Using jdk 11 and > now jdk 17. Projects without deltaspike work fine. This issue presents > itself only with deltaspike usage. Please confirm that deltaspike works with > recent version as weld keeps moving but deltaspike seems tuck in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DELTASPIKE-1448) Deltaspike fails with weld 3.1.7+
[ https://issues.apache.org/jira/browse/DELTASPIKE-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned DELTASPIKE-1448: - Assignee: Mark Struberg > Deltaspike fails with weld 3.1.7+ > - > > Key: DELTASPIKE-1448 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1448 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Jeremy Landis >Assignee: Mark Struberg >Priority: Major > > See [https://issues.redhat.com/browse/WELD-2669] > > Since weld 3.1.7, proxy changed. deltaspike does not work. Using jdk 11 and > now jdk 17. Projects without deltaspike work fine. This issue presents > itself only with deltaspike usage. Please confirm that deltaspike works with > recent version as weld keeps moving but deltaspike seems tuck in time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1425) Download page links all broken
[ https://issues.apache.org/jira/browse/DELTASPIKE-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1425. --- Assignee: Mark Struberg Resolution: Fixed > Download page links all broken > -- > > Key: DELTASPIKE-1425 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1425 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Sebb >Assignee: Mark Struberg >Priority: Critical > > As the subject says. > The download page links to 1.9.4, however that was replaced by 1.9.5 today > To avoid this happening in future, the recommended approach is: > - publish the new release. Do not delete the previous one yet. > - wait a day or so for mirrors to catch up > - update the download page, and send announce emails > - remove any old releases -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DELTASPIKE-1456) Introduce default methods for some functions in ConfigSource
[
https://issues.apache.org/jira/browse/DELTASPIKE-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned DELTASPIKE-1456:
-
Assignee: Mark Struberg
> Introduce default methods for some functions in ConfigSource
>
>
> Key: DELTASPIKE-1456
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1456
> Project: DeltaSpike
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.6
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.7
>
>
> Right now our {{ConfigSource}} interface is still mostly an old Java6
> interface. We already use a default method for the onChange callback
> registration. We could also provide some other default methods, e.g. for
> {{getOrdinal()}} and {{isScannable().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (DELTASPIKE-1456) Introduce default methods for some functions in ConfigSource
Mark Struberg created DELTASPIKE-1456:
-
Summary: Introduce default methods for some functions in
ConfigSource
Key: DELTASPIKE-1456
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1456
Project: DeltaSpike
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Configuration
Affects Versions: 1.9.6
Reporter: Mark Struberg
Fix For: 1.9.7
Right now our {{ConfigSource}} interface is still mostly an old Java6
interface. We already use a default method for the onChange callback
registration. We could also provide some other default methods, e.g. for
{{getOrdinal()}} and {{isScannable().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1455) Allow to pass properties to Weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1455. --- Resolution: Fixed Thanks for the PR! applied and enhanced. > Allow to pass properties to Weld > > > Key: DELTASPIKE-1455 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: CdiControl >Affects Versions: 1.9.6 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.7 > > > See PR > https://github.com/apache/deltaspike/pull/129 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (DELTASPIKE-1455) Allow to pass properties to Weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned DELTASPIKE-1455: - Assignee: Mark Struberg > Allow to pass properties to Weld > > > Key: DELTASPIKE-1455 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: CdiControl >Affects Versions: 1.9.6 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.7 > > > See PR > https://github.com/apache/deltaspike/pull/129 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DELTASPIKE-1455) Allow to pass properties to Weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated DELTASPIKE-1455: -- Description: See PR Allow to pass properties to Weld > Allow to pass properties to Weld > > > Key: DELTASPIKE-1455 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: CdiControl >Affects Versions: 1.9.6 >Reporter: Mark Struberg >Priority: Major > Fix For: 1.9.7 > > > See PR > Allow to pass properties to Weld -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DELTASPIKE-1455) Allow to pass properties to Weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated DELTASPIKE-1455: -- Description: See PR https://github.com/apache/deltaspike/pull/129 was: See PR Allow to pass properties to Weld > Allow to pass properties to Weld > > > Key: DELTASPIKE-1455 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: CdiControl >Affects Versions: 1.9.6 >Reporter: Mark Struberg >Priority: Major > Fix For: 1.9.7 > > > See PR > https://github.com/apache/deltaspike/pull/129 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (DELTASPIKE-1455) Allow to pass properties to Weld
Mark Struberg created DELTASPIKE-1455: - Summary: Allow to pass properties to Weld Key: DELTASPIKE-1455 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1455 Project: DeltaSpike Issue Type: Improvement Security Level: public (Regular issues) Components: CdiControl Affects Versions: 1.9.6 Reporter: Mark Struberg Fix For: 1.9.7 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (DELTASPIKE-1454) Upgrade ASM to 9.3
[ https://issues.apache.org/jira/browse/DELTASPIKE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1454. --- Resolution: Fixed > Upgrade ASM to 9.3 > -- > > Key: DELTASPIKE-1454 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1454 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Proxy-Module >Affects Versions: 1.9.5 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.6 > > > Upgrade ASM to 9.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (DELTASPIKE-1454) Upgrade ASM to 9.3
Mark Struberg created DELTASPIKE-1454: - Summary: Upgrade ASM to 9.3 Key: DELTASPIKE-1454 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1454 Project: DeltaSpike Issue Type: Improvement Security Level: public (Regular issues) Components: Proxy-Module Affects Versions: 1.9.5 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.9.6 Upgrade ASM to 9.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1431) add easy way to disable InvocationResultLogger
[
https://issues.apache.org/jira/browse/DELTASPIKE-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1431.
---
Resolution: Fixed
`deltaspike.invocationresultlogger.enabled=false` can be used to disable the
built-in InvocationResultLogger
> add easy way to disable InvocationResultLogger
> --
>
> Key: DELTASPIKE-1431
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1431
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now {{InvocationResultLogger}} is always enabled. Thus whenever the
> {{InvocationMonitored}} mechanism is used we will always get the result loged
> out at the end of the request.
> But in many cases one wants to use a different output. E.g. if only
> statistics are to be used and logged out into a separate file every 5 minutes.
> For all those scenarios we should add a simple to use way to disable this
> Bean.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1433) EntityManagerFactoryProducer should also provide a @Disposes method
[
https://issues.apache.org/jira/browse/DELTASPIKE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1433.
---
Resolution: Fixed
> EntityManagerFactoryProducer should also provide a @Disposes method
> ---
>
> Key: DELTASPIKE-1433
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1433
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JPA-Module
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now our {{EntityManagerFactoryProducer}} does only create
> EntityManagerFactories but does not destroy them properly at shutdown.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1453) injecting config of Class got broken
[ https://issues.apache.org/jira/browse/DELTASPIKE-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1453. --- Resolution: Fixed > injecting config of Class got broken > > > Key: DELTASPIKE-1453 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1453 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Configuration >Affects Versions: 1.9.5 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.6 > > > In release 1.9.5 we broke injection of `@ConfigProperty Class someClass`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (DELTASPIKE-1453) injecting config of Class got broken
Mark Struberg created DELTASPIKE-1453: - Summary: injecting config of Class got broken Key: DELTASPIKE-1453 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1453 Project: DeltaSpike Issue Type: Bug Security Level: public (Regular issues) Components: Configuration Affects Versions: 1.9.5 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.9.6 In release 1.9.5 we broke injection of `@ConfigProperty Class someClass`. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1452) upgrade to apache-parent 25
[ https://issues.apache.org/jira/browse/DELTASPIKE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1452. --- Resolution: Fixed > upgrade to apache-parent 25 > --- > > Key: DELTASPIKE-1452 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1452 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) > Components: Build >Affects Versions: 1.9.5 >Reporter: Mark Struberg >Assignee: Mark Struberg >Priority: Major > Fix For: 1.9.6 > > > upgrade to apache-parent 25 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (DELTASPIKE-1452) upgrade to apache-parent 25
Mark Struberg created DELTASPIKE-1452: - Summary: upgrade to apache-parent 25 Key: DELTASPIKE-1452 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1452 Project: DeltaSpike Issue Type: Task Security Level: public (Regular issues) Components: Build Affects Versions: 1.9.5 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.9.6 upgrade to apache-parent 25 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-1212) Introduce a ConfigResolver.resolveAllProperties method
[
https://issues.apache.org/jira/browse/DELTASPIKE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-1212.
-
Assignee: Mark Struberg (was: John D. Ament)
Resolution: Won't Fix
closing since no patch got submitted for a long time
> Introduce a ConfigResolver.resolveAllProperties method
> --
>
> Key: DELTASPIKE-1212
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1212
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Configuration
>Affects Versions: 1.7.0
>Reporter: John D. Ament
>Assignee: Mark Struberg
>Priority: Major
>
> Invoking ConfigResolver.getAllProperties does not expand out any inlined
> variables. In addition, assume the following properties file and project
> stage = Development
> {code}
> some-service-url=${edge-server-url}/some-service
> edge-server-url=undefined
> edge-server-url.Development=http://development:8081
> edge-server-url.Staging=http://staging:8081
> edge-server-url.Production=http://prod:8081
> {code}
> calling {{getAllProperties}} returns the raw output of this file.
> Introducing a new {{resolveAllProperties}} method would only return back the
> active values. The expected result would be
> {code}
> some-service-url=http://development:8081/some-service
> edge-server-url=http://development:8081
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-1333) Support default methods in interface based configuration
[
https://issues.apache.org/jira/browse/DELTASPIKE-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-1333.
-
Resolution: Won't Fix
sadly problematic as java proxies don't support this properly across different
java versions.
> Support default methods in interface based configuration
>
>
> Key: DELTASPIKE-1333
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1333
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Configuration
>Affects Versions: 1.8.1
> Environment: Java 8, DeltaSpike 1.8.1
>Reporter: Niels Ull Harremoes
>Assignee: Mark Struberg
>Priority: Minor
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> I wanted to implement a default method in one of my configuration methods as
> a simple way to configure a Duration:
> {code:java}
> @Configuration
> interface CacheConfig {
> @ConfigProperty(name = "cache.lifetime", defaultValue = "P1D")
> String cacheLifetime();
> default Duration getCacheLifetimeDuration() {
> try {
> return Duration.parse(cacheLifetime());
> } catch (DateTimeParseException e) {
> ...
> }
> }
> {code}
> However, a runtime I get the error
> {quote}java.lang.UnsupportedOperationException: public default
> java.time.Duration com.example.CacheConfig.getLifetimeDuration() doesn't have
> @ConfigProperty and therefore is illegal
> {quote}
> It would be nice if default methods were not processed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-1084) Integrate configuration sources expressed as URLs.
[
https://issues.apache.org/jira/browse/DELTASPIKE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-1084.
-
Resolution: Won't Fix
closing due to no patch since a long time
> Integrate configuration sources expressed as URLs.
> --
>
> Key: DELTASPIKE-1084
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1084
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Configuration
>Reporter: Pablo Pita Leira
>Assignee: Mark Struberg
>Priority: Minor
>
> The PropertyFileUtils class can load the properties file as follows :
> {code}
> String root = System.getProperty("user.dir");
> String path = root + "/src/test/resources/myurlconfig.properties";
> String urlPath = "file:/" + path;
> URL propertyFileUrl = new URL(urlPath);
> Poperties p = PropertyFileUtils.loadProperties(propertyFileUrl);
> {code}
> Using the following code to incorporate the properties does not work:
> {code}
> public class MyUrlCustomPropertyFileConfig implements PropertyFileConfig
> {
>
> @Override
> public String getPropertyFileName()
> {
> String root = System.getProperty("user.dir");
> String path = root + "/src/test/resources/myurlconfig.properties";
> return "file:/" + path;
> }
> @Override
> public boolean isOptional()
> {
> return false;
> }
> }
> {code}
> I get an exception as follows:
> {code}
> java.lang.IllegalStateException: com.example.MyUrlCustomPropertyFileConfig
> points to an invalid file:
> 'file:/D:\Dev\GIT\example-test/src/test/resources/myurlconfig.properties'
> at
> org.apache.deltaspike.core.impl.config.ConfigurationExtension.createPropertyConfigSource(ConfigurationExtension.java:210)
> at
> org.apache.deltaspike.core.impl.config.ConfigurationExtension.registerUserConfigSources(ConfigurationExtension.java:135)
> at
> org.apache.deltaspike.core.impl.config.ConfigurationExtension$Proxy$_$$_WeldClientProxy.registerUserConfigSources(ConfigurationExtension$Proxy$_$$_WeldClientProxy.java)
> {code}
> By looking into the test code in DeltaSpike I do not see any usage of the URL
> mechanism as a property configuration source. This should be improved.
> There should be a way to integrate easily configuration sources expressed as
> URLs. As user, I would like that the way to integrate URL paths as
> configuration sources is also documented (including those starting with
> file:/).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-996) org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig fails for weblogic
[ https://issues.apache.org/jira/browse/DELTASPIKE-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-996. Resolution: Won't Fix closing due to no patch since a long time > org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig > fails for weblogic > - > > Key: DELTASPIKE-996 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-996 > Project: DeltaSpike > Issue Type: Bug > Components: Tests >Affects Versions: 1.5.0 >Reporter: JJ Snyder >Assignee: Mark Struberg >Priority: Major > > org.apache.deltaspike.test.core.api.config.propertyconfigsource.ConfigPropertyWARTest#testInjectConfig > fails when run against weblogic. This is failing because > ConfigResolver.configSources is getting populated during deployment using the > Thread's context class loader. At runtime the current Thread's context class > loader is used to access configSources. The problem is that the context > class loaders are not the same. Afaict there is nothing in the specs that > says the context class loaders must be the same. So I think the test is bad > and needs to be written differently. If I force the class loader to be the > same in a debugger then I can make the test pass. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-591) Add a ProjectStage aware resource Servlet
[ https://issues.apache.org/jira/browse/DELTASPIKE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-591. Resolution: Won't Fix > Add a ProjectStage aware resource Servlet > - > > Key: DELTASPIKE-591 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-591 > Project: DeltaSpike > Issue Type: New Feature > Components: Servlet-Module >Reporter: Daniel Sachse >Assignee: Romain Manni-Bucau >Priority: Major > Attachments: DELTASPIKE-591.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (DELTASPIKE-591) Add a ProjectStage aware resource Servlet
[ https://issues.apache.org/jira/browse/DELTASPIKE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened DELTASPIKE-591: -- > Add a ProjectStage aware resource Servlet > - > > Key: DELTASPIKE-591 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-591 > Project: DeltaSpike > Issue Type: New Feature > Components: Servlet-Module >Reporter: Daniel Sachse >Assignee: Romain Manni-Bucau >Priority: Major > Attachments: DELTASPIKE-591.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-858) @Exclude usage of != operator in onExpression should match when the property is not defined
[ https://issues.apache.org/jira/browse/DELTASPIKE-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-858. Resolution: Won't Fix > @Exclude usage of != operator in onExpression should match when the property > is not defined > --- > > Key: DELTASPIKE-858 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-858 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.3.0 > Environment: weld-se >Reporter: Arrault >Priority: Minor > Attachments: ExcludeOnAbsentPropertyTest.java > > > When using @Exclude(onExpression="property!=value"), > I expect the bean to be excluded if the "property" is not defined which is > not the case the current implementation -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (DELTASPIKE-858) @Exclude usage of != operator in onExpression should match when the property is not defined
[ https://issues.apache.org/jira/browse/DELTASPIKE-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened DELTASPIKE-858: -- > @Exclude usage of != operator in onExpression should match when the property > is not defined > --- > > Key: DELTASPIKE-858 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-858 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.3.0 > Environment: weld-se >Reporter: Arrault >Priority: Minor > Attachments: ExcludeOnAbsentPropertyTest.java > > > When using @Exclude(onExpression="property!=value"), > I expect the bean to be excluded if the "property" is not defined which is > not the case the current implementation -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-687) Let users disable Query Method Expressions
[ https://issues.apache.org/jira/browse/DELTASPIKE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-687. Resolution: Won't Fix > Let users disable Query Method Expressions > -- > > Key: DELTASPIKE-687 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-687 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Affects Versions: 1.0.1 >Reporter: Dominik Obermaier >Assignee: Daniel Cunha >Priority: Major > > While Query Method Expressions are very useful, it would be great to disable > this feature globally or on a per-method basis if this automatic > implementation is not desired. > The following approaches could be worth investigating: > - Disable the Query Method Expressions feature globally with the > apache-deltaspike.properties > - Introduce a new annotation to mark methods for getting ignored by the Query > Method Expression Parser -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (DELTASPIKE-687) Let users disable Query Method Expressions
[ https://issues.apache.org/jira/browse/DELTASPIKE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened DELTASPIKE-687: -- > Let users disable Query Method Expressions > -- > > Key: DELTASPIKE-687 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-687 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Affects Versions: 1.0.1 >Reporter: Dominik Obermaier >Assignee: Daniel Cunha >Priority: Major > > While Query Method Expressions are very useful, it would be great to disable > this feature globally or on a per-method basis if this automatic > implementation is not desired. > The following approaches could be worth investigating: > - Disable the Query Method Expressions feature globally with the > apache-deltaspike.properties > - Introduce a new annotation to mark methods for getting ignored by the Query > Method Expression Parser -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-844) Separate the concerns of context and container control
[ https://issues.apache.org/jira/browse/DELTASPIKE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-844. Resolution: Won't Fix > Separate the concerns of context and container control > -- > > Key: DELTASPIKE-844 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-844 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament >Priority: Major > > There are currently 3 modules which use some form of a context controller, to > start contexts in an interceptor. > Modules may optionally need to start scopes, but it shouldn't be required. > Allow these modules to have a separation of concern with context control. If > the context controller cannot be found add logs indicating that context > control is disabled due to missing classes. > Add a similar ability that these modules use in a central location in context > control. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (DELTASPIKE-844) Separate the concerns of context and container control
[ https://issues.apache.org/jira/browse/DELTASPIKE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened DELTASPIKE-844: -- > Separate the concerns of context and container control > -- > > Key: DELTASPIKE-844 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-844 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament >Priority: Major > > There are currently 3 modules which use some form of a context controller, to > start contexts in an interceptor. > Modules may optionally need to start scopes, but it shouldn't be required. > Allow these modules to have a separation of concern with context control. If > the context controller cannot be found add logs indicating that context > control is disabled due to missing classes. > Add a similar ability that these modules use in a central location in context > control. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-977) discuss handling of custom scope-annotations
[ https://issues.apache.org/jira/browse/DELTASPIKE-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-977. Resolution: Won't Fix closing due to no patch since a long time > discuss handling of custom scope-annotations > > > Key: DELTASPIKE-977 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-977 > Project: DeltaSpike > Issue Type: Task > Components: CdiControl >Affects Versions: 1.5.0 >Reporter: Gerhard Petracek >Assignee: Mark Struberg >Priority: Major > > e.g. we could introduce a deactivatable validator for the scope-annotations > passed to ContextControl#startContext and ContextControl#stopContext (similar > to what we have in the test-control module) to avoid wrong usages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-688) OSGi Support for DeltaSpike JSF and its dependencies
[ https://issues.apache.org/jira/browse/DELTASPIKE-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-688. Resolution: Won't Fix > OSGi Support for DeltaSpike JSF and its dependencies > > > Key: DELTASPIKE-688 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-688 > Project: DeltaSpike > Issue Type: New Feature > Components: JSF-Module, Security-Module >Affects Versions: 1.0.1 >Reporter: Harald Wellmann >Assignee: Harald Wellmann >Priority: Major > > Goal: > Users can work with DeltaSpike JSF in OSGi applications, using Pax CDI. > This includes adding OSGi support to DeltaSpike Security, a runtime > dependency of DeltaSpike JSF. > (Actually, I think this indicates the JSF module is not modular enough, but > that's a different story. JSF should not depend on security at all.) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (DELTASPIKE-688) OSGi Support for DeltaSpike JSF and its dependencies
[ https://issues.apache.org/jira/browse/DELTASPIKE-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reopened DELTASPIKE-688: -- > OSGi Support for DeltaSpike JSF and its dependencies > > > Key: DELTASPIKE-688 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-688 > Project: DeltaSpike > Issue Type: New Feature > Components: JSF-Module, Security-Module >Affects Versions: 1.0.1 >Reporter: Harald Wellmann >Assignee: Harald Wellmann >Priority: Major > > Goal: > Users can work with DeltaSpike JSF in OSGi applications, using Pax CDI. > This includes adding OSGi support to DeltaSpike Security, a runtime > dependency of DeltaSpike JSF. > (Actually, I think this indicates the JSF module is not modular enough, but > that's a different story. JSF should not depend on security at all.) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-921) OSGi support for Servlet Module
[ https://issues.apache.org/jira/browse/DELTASPIKE-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-921. Resolution: Fixed closing due to no patch since a long time > OSGi support for Servlet Module > --- > > Key: DELTASPIKE-921 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-921 > Project: DeltaSpike > Issue Type: New Feature > Components: Servlet-Module >Affects Versions: 1.4.0 >Reporter: Harald Wellmann >Assignee: Harald Wellmann >Priority: Major > > Goal: > Users can work with DeltaSpike Servlet in OSGi applications, using Pax CDI. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-936) OSGi capability cleanup
[
https://issues.apache.org/jira/browse/DELTASPIKE-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-936.
Resolution: Fixed
closing due to no patch since a long time
> OSGi capability cleanup
> ---
>
> Key: DELTASPIKE-936
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-936
> Project: DeltaSpike
> Issue Type: Improvement
>Affects Versions: 1.4.1
>Reporter: Harald Wellmann
>Assignee: Harald Wellmann
>Priority: Major
>
> OSGi capabilities and requirements are somewhat inconsistent at the moment.
> {noformat}
> osgi.extender; filter:="(osgi.extender=pax.cdi)"
> {noformat}
> must be required by all modules providing CDI beans.
> {noformat}
> org.ops4j.pax.cdi.extension; filter:="(extension=pax-cdi-extension)"
> {noformat}
> is not required, since DeltaSpike modules do not provide or consume OSGi
> services.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-687) Let users disable Query Method Expressions
[ https://issues.apache.org/jira/browse/DELTASPIKE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-687. Resolution: Fixed closing due to no patch since a long time > Let users disable Query Method Expressions > -- > > Key: DELTASPIKE-687 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-687 > Project: DeltaSpike > Issue Type: Improvement > Components: Data-Module >Affects Versions: 1.0.1 >Reporter: Dominik Obermaier >Assignee: Daniel Cunha >Priority: Major > > While Query Method Expressions are very useful, it would be great to disable > this feature globally or on a per-method basis if this automatic > implementation is not desired. > The following approaches could be worth investigating: > - Disable the Query Method Expressions feature globally with the > apache-deltaspike.properties > - Introduce a new annotation to mark methods for getting ignored by the Query > Method Expression Parser -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-688) OSGi Support for DeltaSpike JSF and its dependencies
[ https://issues.apache.org/jira/browse/DELTASPIKE-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-688. Resolution: Fixed closing due to no patch since a long time > OSGi Support for DeltaSpike JSF and its dependencies > > > Key: DELTASPIKE-688 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-688 > Project: DeltaSpike > Issue Type: New Feature > Components: JSF-Module, Security-Module >Affects Versions: 1.0.1 >Reporter: Harald Wellmann >Assignee: Harald Wellmann >Priority: Major > > Goal: > Users can work with DeltaSpike JSF in OSGi applications, using Pax CDI. > This includes adding OSGi support to DeltaSpike Security, a runtime > dependency of DeltaSpike JSF. > (Actually, I think this indicates the JSF module is not modular enough, but > that's a different story. JSF should not depend on security at all.) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-844) Separate the concerns of context and container control
[ https://issues.apache.org/jira/browse/DELTASPIKE-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-844. Resolution: Fixed closing due to no patch since a long time > Separate the concerns of context and container control > -- > > Key: DELTASPIKE-844 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-844 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament >Priority: Major > > There are currently 3 modules which use some form of a context controller, to > start contexts in an interceptor. > Modules may optionally need to start scopes, but it shouldn't be required. > Allow these modules to have a separation of concern with context control. If > the context controller cannot be found add logs indicating that context > control is disabled due to missing classes. > Add a similar ability that these modules use in a central location in context > control. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-858) @Exclude usage of != operator in onExpression should match when the property is not defined
[ https://issues.apache.org/jira/browse/DELTASPIKE-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-858. Resolution: Fixed closing due to no patch since a long time > @Exclude usage of != operator in onExpression should match when the property > is not defined > --- > > Key: DELTASPIKE-858 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-858 > Project: DeltaSpike > Issue Type: Bug > Components: Core >Affects Versions: 1.3.0 > Environment: weld-se >Reporter: Arrault >Priority: Minor > Attachments: ExcludeOnAbsentPropertyTest.java > > > When using @Exclude(onExpression="property!=value"), > I expect the bean to be excluded if the "property" is not defined which is > not the case the current implementation -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-591) Add a ProjectStage aware resource Servlet
[ https://issues.apache.org/jira/browse/DELTASPIKE-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-591. Resolution: Fixed closing due to no patch since a long time > Add a ProjectStage aware resource Servlet > - > > Key: DELTASPIKE-591 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-591 > Project: DeltaSpike > Issue Type: New Feature > Components: Servlet-Module >Reporter: Daniel Sachse >Assignee: Romain Manni-Bucau >Priority: Major > Attachments: DELTASPIKE-591.patch > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (DELTASPIKE-1200) Deltaspike unusable in OSGi
[
https://issues.apache.org/jira/browse/DELTASPIKE-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-1200.
-
Assignee: Mark Struberg (was: Harald Wellmann)
Resolution: Won't Fix
closing due to no patch since a long time
> Deltaspike unusable in OSGi
> ---
>
> Key: DELTASPIKE-1200
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1200
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.4.2
> Environment: OSGi, Pax-CDI
>Reporter: Guillaume Nodet
>Assignee: Mark Struberg
>Priority: Blocker
>
> Deltaspike is now quite unusable in modular environments, in particular OSGi
> due to static fields that are not supposed to be shared.
> This is particularly true for
> {{org.apache.deltaspike.core.api.config.base.CoreBaseConfig}} inner
> interfaces which causes lots of problems. In my scenario,
> {{deltaspike-core-api}} is loaded on itself as a CDI application, which cause
> the {{BeanManagerIntegration.BeanManagerIntegration.DELEGATE_LOOKUP}} field
> to be initialized, but this initialization fails because no config provider
> can be found (the {{deltaspike-core-impl}} jar is not available).
> Later on, when a real application is loaded, nothing works because the class
> has failed initialization and thus delta pike becomes completely unusable.
> Even if I can make the initialization work in my test by changing the order
> of the bundles and making sure the first time the classes are loaded, a
> config provider is available, I think this means that Deltaspike can't be
> shared at all, because those configuration bits are supposed to change from
> one CDI app to another.
> This seems to be all caused by
> https://github.com/apache/deltaspike/commit/25b2b8cc0c955a28743f9a84925c8e410f0d298d
> and DELTASPIKE-892.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1133) Don't override the log level
[ https://issues.apache.org/jira/browse/DELTASPIKE-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1133. --- Fix Version/s: 1.9.6 Resolution: Fixed > Don't override the log level > > > Key: DELTASPIKE-1133 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1133 > Project: DeltaSpike > Issue Type: Bug > Components: TestControl >Affects Versions: 1.6.0 >Reporter: John D. Ament >Assignee: John D. Ament >Priority: Major > Fix For: 1.9.6 > > Attachments: DELTASPIKE-1133-PATCHONE.patch > > > https://github.com/apache/deltaspike/blob/master/deltaspike/modules/test-control/api/src/main/java/org/apache/deltaspike/testcontrol/api/junit/CdiTestSuiteRunner.java#L155 > We override the logger level in place here, and reset it. We shouldn't do > that, as you may want to have no logging output. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (DELTASPIKE-1451) wrong docs links on https://deltaspike.apache.org/javadoc.html
[ https://issues.apache.org/jira/browse/DELTASPIKE-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned DELTASPIKE-1451: - Assignee: Mark Struberg > wrong docs links on https://deltaspike.apache.org/javadoc.html > -- > > Key: DELTASPIKE-1451 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1451 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) > Components: Documentation >Affects Versions: 1.9.5 >Reporter: Buddha Bas >Assignee: Mark Struberg >Priority: Major > Labels: JavaDoc, links > > wrong docs links on https://deltaspike.apache.org/javadoc.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1445) Dynamic Config injection via a Supplier
[
https://issues.apache.org/jira/browse/DELTASPIKE-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1445.
---
Resolution: Fixed
> Dynamic Config injection via a Supplier
> --
>
> Key: DELTASPIKE-1445
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1445
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> We should support injecting Configuration via {{Supplier}}.
> That way we can {{get()}} to access the current value.
> The code to use the feature might look like:
> {code}
> @Inject
> @ConfigProperty(name = "address.header.line", cacheFor = 10, cacheUnit =
> TimeUnit.MINUTES)
> private Supplier addressHeaderLine;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1444) Create POJO and Record based Config
[
https://issues.apache.org/jira/browse/DELTASPIKE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1444.
---
Resolution: Fixed
> Create POJO and Record based Config
> ---
>
> Key: DELTASPIKE-1444
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1444
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now we only support Interface based configuration with the
> {{@Configuration}} annotation. We could also support injecting POJOs directly
> and even Java14 Records.
> E.g. a class
> {code}
> public record Endpoint(String host, Integer port, String path){}
> {code}
> or with a parameter ct:
> {code}
> public class Endpoint {
> private final String host;
> ...
> public Endpoint(
> @ConfigProperty(name="host") String host,
> @ConfigProperty(name="port") Integer port,
> @ConfigProperty(name="path") String path){
> this.host = host;
>
> }
> }
> {code}
> Note that the {{@ConfigProperty}} annotation might get omitted if the class
> gets compiled with the {{javac -parameters}} option.
> or with a default ct and field parameters:
> {code}
> public class Endpoint {
> private String host;
> private Integer port;
> private String path;
> ...
> }
> {code}
> Resolving of all the required properties must be performed atomically.
> The solution might either be done via the built-in algorithms as shown above,
> in which case the following call might be used to denote that a bean should
> get resolved which consists of mulitple attributes:
> {code}
> ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class)
> .getValue();
> {code}
> or via an explicit Converter function:
> {code}
> final ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class, (cfg, key) -> new
> ServerEndpointPojoWithCt(
> cfg.resolve(key + ".host").getValue(),
> cfg.resolve(key + ".port").as(Integer.class).getValue(),
> cfg.resolve(key + ".path").getValue());)
> .getValue();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (DELTASPIKE-1445) Dynamic Config injection via a Supplier
Mark Struberg created DELTASPIKE-1445:
-
Summary: Dynamic Config injection via a Supplier
Key: DELTASPIKE-1445
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1445
Project: DeltaSpike
Issue Type: New Feature
Security Level: public (Regular issues)
Components: Configuration
Affects Versions: 1.9.5
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 1.9.6
We should support injecting Configuration via {{Supplier}}.
That way we can {{get()}} to access the current value.
The code to use the feature might look like:
{code}
@Inject
@ConfigProperty(name = "address.header.line", cacheFor = 10, cacheUnit =
TimeUnit.MINUTES)
private Supplier addressHeaderLine;
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DELTASPIKE-1444) Create POJO and Record based Config
[
https://issues.apache.org/jira/browse/DELTASPIKE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17454832#comment-17454832
]
Mark Struberg commented on DELTASPIKE-1444:
---
Pull request for review is up here
https://github.com/struberg/deltaspike/tree/DELTASPIKE-1444
> Create POJO and Record based Config
> ---
>
> Key: DELTASPIKE-1444
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1444
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now we only support Interface based configuration with the
> {{@Configuration}} annotation. We could also support injecting POJOs directly
> and even Java14 Records.
> E.g. a class
> {code}
> public record Endpoint(String host, Integer port, String path){}
> {code}
> or with a parameter ct:
> {code}
> public class Endpoint {
> private final String host;
> ...
> public Endpoint(
> @ConfigProperty(name="host") String host,
> @ConfigProperty(name="port") Integer port,
> @ConfigProperty(name="path") String path){
> this.host = host;
>
> }
> }
> {code}
> Note that the {{@ConfigProperty}} annotation might get omitted if the class
> gets compiled with the {{javac -parameters}} option.
> or with a default ct and field parameters:
> {code}
> public class Endpoint {
> private String host;
> private Integer port;
> private String path;
> ...
> }
> {code}
> Resolving of all the required properties must be performed atomically.
> The solution might either be done via the built-in algorithms as shown above,
> in which case the following call might be used to denote that a bean should
> get resolved which consists of mulitple attributes:
> {code}
> ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class)
> .getValue();
> {code}
> or via an explicit Converter function:
> {code}
> final ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class, (cfg, key) -> new
> ServerEndpointPojoWithCt(
> cfg.resolve(key + ".host").getValue(),
> cfg.resolve(key + ".port").as(Integer.class).getValue(),
> cfg.resolve(key + ".path").getValue());)
> .getValue();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (DELTASPIKE-1444) Create POJO and Recors based Config
Mark Struberg created DELTASPIKE-1444:
-
Summary: Create POJO and Recors based Config
Key: DELTASPIKE-1444
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1444
Project: DeltaSpike
Issue Type: New Feature
Security Level: public (Regular issues)
Components: Configuration
Affects Versions: 1.9.5
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 1.9.6
Right now we only support Interface based configuration with the
{{@Configuration}} annotation. We could also support injecting POJOs directly
and even Java14 Records.
E.g. a class
{code}
public record Endpoint(String host, Integer port, String path){}
{code}
or with a parameter ct:
{code}
public class Endpoint {
private final String host;
...
public Endpoint(
@ConfigProperty(name="host") String host,
@ConfigProperty(name="port") Integer port,
@ConfigProperty(name="path") String path){
this.host = host;
}
}
{code}
Note that the {{@ConfigProperty}} annotation might get omitted if the class
gets compiled with the {{javac -parameters}} option.
or with a default ct and field parameters:
{code}
public class Endpoint {
private String host;
private Integer port;
private String path;
...
}
{code}
Resolving of all the required properties must be performed atomically.
The solution might either be done via the built-in algorithms as shown above,
in which case the following call might be used to denote that a bean should get
resolved which consists of mulitple attributes:
{code}
ServerEndpointPojoWithCt someServer =
ConfigResolver.resolve("myapp.some.server")
.asBean(ServerEndpointPojoWithCt.class)
.getValue();
{code}
or via an explicit Converter function:
{code}
final ServerEndpointPojoWithCt someServer =
ConfigResolver.resolve("myapp.some.server")
.asBean(ServerEndpointPojoWithCt.class, (cfg, key) -> new
ServerEndpointPojoWithCt(
cfg.resolve(key + ".host").getValue(),
cfg.resolve(key + ".port").as(Integer.class).getValue(),
cfg.resolve(key + ".path").getValue());)
.getValue();
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (DELTASPIKE-1444) Create POJO and Record based Config
[
https://issues.apache.org/jira/browse/DELTASPIKE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated DELTASPIKE-1444:
--
Summary: Create POJO and Record based Config (was: Create POJO and Recors
based Config)
> Create POJO and Record based Config
> ---
>
> Key: DELTASPIKE-1444
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1444
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Configuration
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> Right now we only support Interface based configuration with the
> {{@Configuration}} annotation. We could also support injecting POJOs directly
> and even Java14 Records.
> E.g. a class
> {code}
> public record Endpoint(String host, Integer port, String path){}
> {code}
> or with a parameter ct:
> {code}
> public class Endpoint {
> private final String host;
> ...
> public Endpoint(
> @ConfigProperty(name="host") String host,
> @ConfigProperty(name="port") Integer port,
> @ConfigProperty(name="path") String path){
> this.host = host;
>
> }
> }
> {code}
> Note that the {{@ConfigProperty}} annotation might get omitted if the class
> gets compiled with the {{javac -parameters}} option.
> or with a default ct and field parameters:
> {code}
> public class Endpoint {
> private String host;
> private Integer port;
> private String path;
> ...
> }
> {code}
> Resolving of all the required properties must be performed atomically.
> The solution might either be done via the built-in algorithms as shown above,
> in which case the following call might be used to denote that a bean should
> get resolved which consists of mulitple attributes:
> {code}
> ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class)
> .getValue();
> {code}
> or via an explicit Converter function:
> {code}
> final ServerEndpointPojoWithCt someServer =
> ConfigResolver.resolve("myapp.some.server")
> .asBean(ServerEndpointPojoWithCt.class, (cfg, key) -> new
> ServerEndpointPojoWithCt(
> cfg.resolve(key + ".host").getValue(),
> cfg.resolve(key + ".port").as(Integer.class).getValue(),
> cfg.resolve(key + ".path").getValue());)
> .getValue();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (DELTASPIKE-1441) ConfigProperty support for maps
[
https://issues.apache.org/jira/browse/DELTASPIKE-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned DELTASPIKE-1441:
-
Assignee: Mark Struberg
> ConfigProperty support for maps
> ---
>
> Key: DELTASPIKE-1441
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1441
> Project: DeltaSpike
> Issue Type: Wish
> Security Level: public(Regular issues)
>Reporter: Andrew Marinchuk
>Assignee: Mark Struberg
>Priority: Major
>
> Let's assume that we have the following configuration:{code}my.param.a=1
> my.param.b=2
> my.param.c=3
> ...{code}
> And we want to load all the {{my.param.*}} parameters into the {{Map Integer>}}.
> With the current configuration api there two ways to load such config:
> # add parameter {{my.param.all=a,b,c,...}} with complete list of
> {{my.param.*}} parameters, add an {{@Inject}}'ed {{List}} field with
> {{@ConfigProperty}} annotation to read this parameter and then fill the map
> values by reading value by each of the provided keys.
> # iterate through ConfigResolver.getAllProperties() by code like
> [filterPropsByPrefix
> function|https://issues.apache.org/jira/browse/DELTASPIKE-1212?focusedCommentId=16986128=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16986128]
> and fill the Map with it
> But I think that loading such config shouldn't be a user problem, library
> should be capable of loading it. Of course, user can introduce the
> {{@ApplicationScoped}} bean which will inherits the
> {{org.apache.deltaspike.core.spi.config.BaseConfigPropertyProducer}} and
> introduce the {{@Producer}} methods for {{Map}} analog for
> producers introduced in
> org.apache.deltaspike.core.impl.config.DefaultConfigPropertyProducer. But it
> should be a library code.
> Another use case which should be covered is loading Map where
> Intf - interface with {{@Configuration}} annotation, i.e.:
> {code}datasources.one.url=jdbc://...
> datasources.one.user=myuser
> datasources.one.password=pass
> datasources.two.url=jdbc://
> datasources.two.user=myuser2
> datasources.two.password=pass2
> ...{code}
> Currently we use code from [this
> comment|https://issues.apache.org/jira/browse/DELTASPIKE-1212?focusedCommentId=16986128=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16986128]
> to load such configuration, but it could be much simpler if deltaspike had
> ConfigProperty support for maps with ability to use @Configuration interfaces
> as values.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (DELTASPIKE-1440) Remove Metadata Builders
[ https://issues.apache.org/jira/browse/DELTASPIKE-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1440. --- Resolution: Fixed > Remove Metadata Builders > > > Key: DELTASPIKE-1440 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1440 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Core >Affects Versions: 2.0 >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > CDI-2.0 did introduce a 'Configuration' API for CDI events. This feature in > the spec is almost a clone of what we did provide in DeltaSpike since years. > Ir is really easy for users to migrate to the classes which are now part of > the spec as even most methods have the same name and semantics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1440) Remove Metadata Builders
Mark Struberg created DELTASPIKE-1440: - Summary: Remove Metadata Builders Key: DELTASPIKE-1440 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1440 Project: DeltaSpike Issue Type: Sub-task Security Level: public (Regular issues) Components: Core Affects Versions: 2.0 Reporter: Mark Struberg Fix For: 2.0 CDI-2.0 did introduce a 'Configuration' API for CDI events. This feature in the spec is almost a clone of what we did provide in DeltaSpike since years. Ir is really easy for users to migrate to the classes which are now part of the spec as even most methods have the same name and semantics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-1438) Remove EAR support
[ https://issues.apache.org/jira/browse/DELTASPIKE-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1438. --- Resolution: Fixed > Remove EAR support > --- > > Key: DELTASPIKE-1438 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1438 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > CDI iin EARs is broken on most containers alltogether. There is just old > Glassfish EE6, WebSphere 8.0 and 8..5 and TomEE where EAR do work without > leaking classes or creating mem leaks. Thus we can likely also drop our EAR > support as it is a very time intense task to support it. > Plus EARs are rarely used in these times. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-1439) Remove Global Alternatives
[ https://issues.apache.org/jira/browse/DELTASPIKE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1439. --- Resolution: Fixed > Remove Global Alternatives > -- > > Key: DELTASPIKE-1439 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1439 > Project: DeltaSpike > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: Core >Affects Versions: 2.0 >Reporter: Mark Struberg >Priority: Major > Fix For: 2.0 > > > 'Global Alternatives' has been a way to fix a nasty design decision in CDI > 1.0 (see https://issues.redhat.com/browse/CDI-18) in a backward compatible > way. > Nowadays we can ask people to just use`@Priority` and be done. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1439) Remove Global Alternatives
Mark Struberg created DELTASPIKE-1439: - Summary: Remove Global Alternatives Key: DELTASPIKE-1439 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1439 Project: DeltaSpike Issue Type: Sub-task Security Level: public (Regular issues) Components: Core Affects Versions: 2.0 Reporter: Mark Struberg Fix For: 2.0 'Global Alternatives' has been a way to fix a nasty design decision in CDI 1.0 (see https://issues.redhat.com/browse/CDI-18) in a backward compatible way. Nowadays we can ask people to just use`@Priority` and be done. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1438) Remove EAR support
Mark Struberg created DELTASPIKE-1438: - Summary: Remove EAR support Key: DELTASPIKE-1438 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1438 Project: DeltaSpike Issue Type: Sub-task Security Level: public (Regular issues) Reporter: Mark Struberg Fix For: 2.0 CDI iin EARs is broken on most containers alltogether. There is just old Glassfish EE6, WebSphere 8.0 and 8..5 and TomEE where EAR do work without leaking classes or creating mem leaks. Thus we can likely also drop our EAR support as it is a very time intense task to support it. Plus EARs are rarely used in these times. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1437) DeltaSpike-2.0 umbrella ticket
Mark Struberg created DELTASPIKE-1437: - Summary: DeltaSpike-2.0 umbrella ticket Key: DELTASPIKE-1437 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1437 Project: DeltaSpike Issue Type: Task Security Level: public (Regular issues) Reporter: Mark Struberg Fix For: 2.0 This is an umbrella ticket for various DeltaSpike 2.0 tasks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406662#comment-17406662 ] Mark Struberg commented on DELTASPIKE-1434: --- Hi [~roytmana] It's deployed to the ASF repository https://repository.apache.org/content/groups/snapshots/ e.g. https://repository.apache.org/content/groups/snapshots/org/apache/deltaspike/core/deltaspike-core-impl/1.9.6-SNAPSHOT/ > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406662#comment-17406662 ] Mark Struberg edited comment on DELTASPIKE-1434 at 8/30/21, 10:02 AM: -- Hi [~roytmana] It's deployed to the ASF repository https://repository.apache.org/content/groups/snapshots/ e.g. https://repository.apache.org/content/groups/snapshots/org/apache/deltaspike/core/deltaspike-core-impl/1.9.6-SNAPSHOT/ And of course building from source is just running a mvn install was (Author: struberg): Hi [~roytmana] It's deployed to the ASF repository https://repository.apache.org/content/groups/snapshots/ e.g. https://repository.apache.org/content/groups/snapshots/org/apache/deltaspike/core/deltaspike-core-impl/1.9.6-SNAPSHOT/ > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406031#comment-17406031 ] Mark Struberg commented on DELTASPIKE-1434: --- Hi [~mgrigorov] and [~roytmana], I've just added shading for additional attached artifacts with qualifier 'jakarta'. Could you please give it a try and report back? Txs a lot! > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned DELTASPIKE-1434: - Assignee: Mark Struberg > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Assignee: Mark Struberg >Priority: Major > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1434) Namespace change javax to jakarta
[ https://issues.apache.org/jira/browse/DELTASPIKE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373247#comment-17373247 ] Mark Struberg commented on DELTASPIKE-1434: --- We will create a shaded version of DeltaSpike with a quallifier. Supporting both specs that way. Happy for a PR if you want to give it a try? > Namespace change javax to jakarta > - > > Key: DELTASPIKE-1434 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1434 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Core >Affects Versions: 1.9.5 >Reporter: John Smith >Priority: Major > > Is there a plan to make the namespace change from javax to jakartaee. Seems > to be required to use deltaspike in the future. > https://jakarta.ee/compatibility/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1433) EntityManagerFactoryProducer should also provide a @Disposes method
Mark Struberg created DELTASPIKE-1433:
-
Summary: EntityManagerFactoryProducer should also provide a
@Disposes method
Key: DELTASPIKE-1433
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1433
Project: DeltaSpike
Issue Type: Bug
Security Level: public (Regular issues)
Components: JPA-Module
Affects Versions: 1.9.5
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 1.9.6
Right now our {{EntityManagerFactoryProducer}} does only create
EntityManagerFactories but does not destroy them properly at shutdown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1431) add easy way to disable InvocationResultLogger
Mark Struberg created DELTASPIKE-1431:
-
Summary: add easy way to disable InvocationResultLogger
Key: DELTASPIKE-1431
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1431
Project: DeltaSpike
Issue Type: New Feature
Security Level: public (Regular issues)
Affects Versions: 1.9.5
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 1.9.6
Right now {{InvocationResultLogger}} is always enabled. Thus whenever the
{{InvocationMonitored}} mechanism is used we will always get the result loged
out at the end of the request.
But in many cases one wants to use a different output. E.g. if only statistics
are to be used and logged out into a separate file every 5 minutes.
For all those scenarios we should add a simple to use way to disable this Bean.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1430) Migrate to Jakarta EE
[ https://issues.apache.org/jira/browse/DELTASPIKE-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339561#comment-17339561 ] Mark Struberg commented on DELTASPIKE-1430: --- Yes, we should evaluate adding a shade with a classifier. > Migrate to Jakarta EE > - > > Key: DELTASPIKE-1430 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1430 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Martin Tzvetanov Grigorov >Assignee: Mark Struberg >Priority: Major > > Please provide version of DeltaSpike that depends on Jakarta EE APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DELTASPIKE-1430) Migrate to Jakarta EE
[ https://issues.apache.org/jira/browse/DELTASPIKE-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned DELTASPIKE-1430: - Assignee: Mark Struberg > Migrate to Jakarta EE > - > > Key: DELTASPIKE-1430 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1430 > Project: DeltaSpike > Issue Type: Task > Security Level: public(Regular issues) >Reporter: Martin Tzvetanov Grigorov >Assignee: Mark Struberg >Priority: Major > > Please provide version of DeltaSpike that depends on Jakarta EE APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1425) Download page links all broken
[ https://issues.apache.org/jira/browse/DELTASPIKE-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17316326#comment-17316326 ] Mark Struberg commented on DELTASPIKE-1425: --- sebb, the problem is that the infra page handling is/was broken. We can fix this once INFRA-21554 is done. We already published the correct site as stated in the ticket. > Download page links all broken > -- > > Key: DELTASPIKE-1425 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1425 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Sebb >Priority: Critical > > As the subject says. > The download page links to 1.9.4, however that was replaced by 1.9.5 today > To avoid this happening in future, the recommended approach is: > - publish the new release. Do not delete the previous one yet. > - wait a day or so for mirrors to catch up > - update the download page, and send announce emails > - remove any old releases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-1427) JUL Logging with {} as param leeds to NumberFormatException
[
https://issues.apache.org/jira/browse/DELTASPIKE-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1427.
---
Resolution: Fixed
> JUL Logging with {} as param leeds to NumberFormatException
> ---
>
> Key: DELTASPIKE-1427
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1427
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
>Affects Versions: 1.9.5
>Reporter: Mark Struberg
>Assignee: Mark Struberg
>Priority: Major
> Fix For: 1.9.6
>
>
> We sometimes log with {} which results in weird logging errors. Should use
> {0} instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (DELTASPIKE-1427) JUL Logging with {} as param leeds to NumberFormatException
Mark Struberg created DELTASPIKE-1427:
-
Summary: JUL Logging with {} as param leeds to
NumberFormatException
Key: DELTASPIKE-1427
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1427
Project: DeltaSpike
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 1.9.5
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 1.9.6
We sometimes log with {} which results in weird logging errors. Should use {0}
instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-1399) Md5 and SHA1 are deprecated
[ https://issues.apache.org/jira/browse/DELTASPIKE-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1399. --- Resolution: Fixed Hi Sebastian! we already use sha512 since quite some time. We do keep sha1 because some mechanism still support it for validation and cannot cope with sha512. > Md5 and SHA1 are deprecated > --- > > Key: DELTASPIKE-1399 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1399 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Sebb >Assignee: Mark Struberg >Priority: Major > > MD5 and SHA1 were deprecated as hash methods quite some time ago. > They should no longer be used. > Please update your releases to use SHA256 or SHA512 and remove/update any > references to MD5 and SHA1 in download documentation. > https://www.apache.org/dev/release-distribution#sigs-and-sums -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1424) BeanProvider.getContextualReference Failing After Upgrading to v1.9.2
[
https://issues.apache.org/jira/browse/DELTASPIKE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297698#comment-17297698
]
Mark Struberg commented on DELTASPIKE-1424:
---
Glad it worked! Regarding bug fix: you have to ask Wildfly guys to fix it, as
it's not a bug in DeltaSpike.
A quick explanation: Long before CDI introduced CDI.current() we already had
our BeanManagerProvider/BeanProvider couple (the later internally uses the
former). This observes BeforeBeanDiscovery and also has an injection of
BeanManager. This bm gets stored away in the Extension. This works very robust,
but might create mem leaks in very seldom cases where some Containers (afair
WLS) do not fire the BeforeShutdown for all ClassLoaders which got triggered
with BeforeBeanDiscovery. That was the initial reason to switch to using
{{CDI.current()}} via Reflection. This works perfectly fine in all WAR
scenarios and many containers with EARs as well. But on some Containers this
leads to a nasty bug as you did encounter yourself. Using this magic flag
should do the trick though.
> BeanProvider.getContextualReference Failing After Upgrading to v1.9.2
> -
>
> Key: DELTASPIKE-1424
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1424
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.2, 1.9.3, 1.9.4
> Environment: Ubuntu 18.04
> Java 1.8
> Jboss Wildfly 18.0.1
>Reporter: Patrick Buchheit
>Priority: Major
>
> I have been using deltaspike successfully to do injection of my entity
> manager into a non-bean class. Recently, I decided to upgrade from version
> 1.5.1 to the current version 1.9.4 to get access to variables in the
> apache-deltaspike.properties file. As soon as I made the change, I started
> seeing errors like this:
>
> {code:java}
> Caused by: java.lang.IllegalStateException: Could not find beans for
> Type=interface javax.persistence.EntityManager and
> qualifiers:[@com.tura.common.service.qualifier.EntityManagerQualifier()]Caused
> by: java.lang.IllegalStateException: Could not find beans for Type=interface
> javax.persistence.EntityManager and
> qualifiers:[@com.tura.common.service.qualifier.EntityManagerQualifier()] at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:154)
> at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:121)
> at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:100)
> at
> com.tura.product.service.test.Test.testUploadFrameImages(Test.java:9702){code}
>
> Nothing in my code has changed; the only alteration I have made is to change
> the deltaspike version in my pom. Just to make sure, I tried rolling back to
> an earlier version of deltaspike. Versions 1.9.1 and earlier all work fine.
> As soon as I change to 1.9.2 or earlier I get an error. I couldn't find
> anything in the patch notes indicating changes I would need to make to
> migrate to a newer version. Is this a bug, or is there some change I need to
> make to my code to make it compatible again?
>
> Some code snippets:
>
> *entity manager lookup-*
> {code:java}
> EntityManager entityManager =
> BeanProvider.getContextualReference(EntityManager.class, new
> EntityManagerQualifierLiteral());{code}
>
> *Producer Bean*
>
> {code:java}
> @Alternative
> public class TestCDIModule
> {
> @PersistenceContext(unitName = "TestProductPersistenceUnit")
> private EntityManager entityManager;
>
> @Produces
> @EntityManagerQualifier
> public EntityManager getEntityManager()
> {
> return this.entityManager;
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-1424) BeanProvider.getContextualReference Failing After Upgrading to v1.9.2
[
https://issues.apache.org/jira/browse/DELTASPIKE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1424.
---
Assignee: Mark Struberg
Resolution: Not A Bug
> BeanProvider.getContextualReference Failing After Upgrading to v1.9.2
> -
>
> Key: DELTASPIKE-1424
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1424
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.2, 1.9.3, 1.9.4
> Environment: Ubuntu 18.04
> Java 1.8
> Jboss Wildfly 18.0.1
>Reporter: Patrick Buchheit
>Assignee: Mark Struberg
>Priority: Major
>
> I have been using deltaspike successfully to do injection of my entity
> manager into a non-bean class. Recently, I decided to upgrade from version
> 1.5.1 to the current version 1.9.4 to get access to variables in the
> apache-deltaspike.properties file. As soon as I made the change, I started
> seeing errors like this:
>
> {code:java}
> Caused by: java.lang.IllegalStateException: Could not find beans for
> Type=interface javax.persistence.EntityManager and
> qualifiers:[@com.tura.common.service.qualifier.EntityManagerQualifier()]Caused
> by: java.lang.IllegalStateException: Could not find beans for Type=interface
> javax.persistence.EntityManager and
> qualifiers:[@com.tura.common.service.qualifier.EntityManagerQualifier()] at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:154)
> at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:121)
> at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:100)
> at
> com.tura.product.service.test.Test.testUploadFrameImages(Test.java:9702){code}
>
> Nothing in my code has changed; the only alteration I have made is to change
> the deltaspike version in my pom. Just to make sure, I tried rolling back to
> an earlier version of deltaspike. Versions 1.9.1 and earlier all work fine.
> As soon as I change to 1.9.2 or earlier I get an error. I couldn't find
> anything in the patch notes indicating changes I would need to make to
> migrate to a newer version. Is this a bug, or is there some change I need to
> make to my code to make it compatible again?
>
> Some code snippets:
>
> *entity manager lookup-*
> {code:java}
> EntityManager entityManager =
> BeanProvider.getContextualReference(EntityManager.class, new
> EntityManagerQualifierLiteral());{code}
>
> *Producer Bean*
>
> {code:java}
> @Alternative
> public class TestCDIModule
> {
> @PersistenceContext(unitName = "TestProductPersistenceUnit")
> private EntityManager entityManager;
>
> @Produces
> @EntityManagerQualifier
> public EntityManager getEntityManager()
> {
> return this.entityManager;
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1424) BeanProvider.getContextualReference Failing After Upgrading to v1.9.2
[
https://issues.apache.org/jira/browse/DELTASPIKE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297492#comment-17297492
]
Mark Struberg commented on DELTASPIKE-1424:
---
+1 Do you have an EAR scenario? In which case it is a known bug in some newer
Containers. Using the option Thomas mentioned switches back to the old CDI-1.0
mechanism we still have around in DeltaSpike.
> BeanProvider.getContextualReference Failing After Upgrading to v1.9.2
> -
>
> Key: DELTASPIKE-1424
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1424
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.2, 1.9.3, 1.9.4
> Environment: Ubuntu 18.04
> Java 1.8
> Jboss Wildfly 18.0.1
>Reporter: Patrick Buchheit
>Priority: Major
>
> I have been using deltaspike successfully to do injection of my entity
> manager into a non-bean class. Recently, I decided to upgrade from version
> 1.5.1 to the current version 1.9.4 to get access to variables in the
> apache-deltaspike.properties file. As soon as I made the change, I started
> seeing errors like this:
>
> {code:java}
> Caused by: java.lang.IllegalStateException: Could not find beans for
> Type=interface javax.persistence.EntityManager and
> qualifiers:[@com.tura.common.service.qualifier.EntityManagerQualifier()]Caused
> by: java.lang.IllegalStateException: Could not find beans for Type=interface
> javax.persistence.EntityManager and
> qualifiers:[@com.tura.common.service.qualifier.EntityManagerQualifier()] at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:154)
> at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:121)
> at
> org.apache.deltaspike.core.api.provider.BeanProvider.getContextualReference(BeanProvider.java:100)
> at
> com.tura.product.service.test.Test.testUploadFrameImages(Test.java:9702){code}
>
> Nothing in my code has changed; the only alteration I have made is to change
> the deltaspike version in my pom. Just to make sure, I tried rolling back to
> an earlier version of deltaspike. Versions 1.9.1 and earlier all work fine.
> As soon as I change to 1.9.2 or earlier I get an error. I couldn't find
> anything in the patch notes indicating changes I would need to make to
> migrate to a newer version. Is this a bug, or is there some change I need to
> make to my code to make it compatible again?
>
> Some code snippets:
>
> *entity manager lookup-*
> {code:java}
> EntityManager entityManager =
> BeanProvider.getContextualReference(EntityManager.class, new
> EntityManagerQualifierLiteral());{code}
>
> *Producer Bean*
>
> {code:java}
> @Alternative
> public class TestCDIModule
> {
> @PersistenceContext(unitName = "TestProductPersistenceUnit")
> private EntityManager entityManager;
>
> @Produces
> @EntityManagerQualifier
> public EntityManager getEntityManager()
> {
> return this.entityManager;
> }
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-1413) dsrwid cookie should not be set to sameSite="None"
[ https://issues.apache.org/jira/browse/DELTASPIKE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1413. --- Fix Version/s: 1.9.5 Resolution: Fixed txs for the report! > dsrwid cookie should not be set to sameSite="None" > -- > > Key: DELTASPIKE-1413 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1413 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Matthias Walliczek >Assignee: Mark Struberg >Priority: Critical > Fix For: 1.9.5 > > > Currently the dsrwid cookie set by the lazy window handler is set to > secure=false and sameSite=None. > This combination will not be allowed by Firefox in the future. See > [https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite.|https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite] > Instead sameSite should be set to "lax", which is default in modern browsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1413) dsrwid cookie should not be set to sameSite="None"
[
https://issues.apache.org/jira/browse/DELTASPIKE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295617#comment-17295617
]
Mark Struberg commented on DELTASPIKE-1413:
---
{color:#00}I'll set the cookie to SameSite=Strict.{color}
{color:#00}I had to do a little trickery as Java's Cookie class does not
support that attribute. Now it should work though.{color}
> dsrwid cookie should not be set to sameSite="None"
> --
>
> Key: DELTASPIKE-1413
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1413
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
>Reporter: Matthias Walliczek
>Assignee: Mark Struberg
>Priority: Critical
>
> Currently the dsrwid cookie set by the lazy window handler is set to
> secure=false and sameSite=None.
> This combination will not be allowed by Firefox in the future. See
> [https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite.|https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite]
> Instead sameSite should be set to "lax", which is default in modern browsers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (DELTASPIKE-1413) dsrwid cookie should not be set to sameSite="None"
[ https://issues.apache.org/jira/browse/DELTASPIKE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned DELTASPIKE-1413: - Assignee: Mark Struberg > dsrwid cookie should not be set to sameSite="None" > -- > > Key: DELTASPIKE-1413 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1413 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Matthias Walliczek >Assignee: Mark Struberg >Priority: Critical > > Currently the dsrwid cookie set by the lazy window handler is set to > secure=false and sameSite=None. > This combination will not be allowed by Firefox in the future. See > [https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite.|https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite] > Instead sameSite should be set to "lax", which is default in modern browsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (DELTASPIKE-1413) dsrwid cookie should not be set to sameSite="None"
[ https://issues.apache.org/jira/browse/DELTASPIKE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated DELTASPIKE-1413: -- Comment: was deleted (was: I'll set the cookie to SameSite=Strict.) > dsrwid cookie should not be set to sameSite="None" > -- > > Key: DELTASPIKE-1413 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1413 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Matthias Walliczek >Priority: Critical > > Currently the dsrwid cookie set by the lazy window handler is set to > secure=false and sameSite=None. > This combination will not be allowed by Firefox in the future. See > [https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite.|https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite] > Instead sameSite should be set to "lax", which is default in modern browsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1413) dsrwid cookie should not be set to sameSite="None"
[ https://issues.apache.org/jira/browse/DELTASPIKE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295600#comment-17295600 ] Mark Struberg commented on DELTASPIKE-1413: --- I'll set the cookie to SameSite=Strict. > dsrwid cookie should not be set to sameSite="None" > -- > > Key: DELTASPIKE-1413 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1413 > Project: DeltaSpike > Issue Type: Bug > Security Level: public(Regular issues) >Reporter: Matthias Walliczek >Priority: Critical > > Currently the dsrwid cookie set by the lazy window handler is set to > secure=false and sameSite=None. > This combination will not be allowed by Firefox in the future. See > [https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite.|https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie/SameSite] > Instead sameSite should be set to "lax", which is default in modern browsers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (DELTASPIKE-1416) deltaspike-core-impl.jar does not contain the Main class to execute in your Manifest.MF to Crypto
[
https://issues.apache.org/jira/browse/DELTASPIKE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1416.
---
Resolution: Fixed
Thanks a lot Daniel, changes applied!
> deltaspike-core-impl.jar does not contain the Main class to execute in your
> Manifest.MF to Crypto
> -
>
> Key: DELTASPIKE-1416
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1416
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.4
>Reporter: Daniel Dias
>Assignee: Mark Struberg
>Priority: Minor
> Fix For: 1.9.5
>
> Attachments: DELTASPIKE-1416.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [https://deltaspike.apache.org/documentation/encryption.html]
> demo how to run java -jar deltaspike-core-impl.jar encode -masterPassword
> myMasterPassword -masterSalt myMasterSalt
> more in your MANIFEST.MF does not contain the Main-Class that is in META-INF
> of the Core:
> [https://github.com/apache/deltaspike/blob/master/deltaspike/core/impl/src/main/resources/META-INF/MANIFEST.MF]
>
> to resolve, you must include a plugin:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> src/main/resources/META-INF/MANIFEST.MF
>
>
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DELTASPIKE-1420) Update ASM to 9.1
[ https://issues.apache.org/jira/browse/DELTASPIKE-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295594#comment-17295594 ] Mark Struberg commented on DELTASPIKE-1420: --- even upgraded to ASM-9.1 now. > Update ASM to 9.1 > - > > Key: DELTASPIKE-1420 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1420 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Proxy-Module >Affects Versions: 1.9.4 >Reporter: Christian Beikov >Assignee: Christian Beikov >Priority: Major > Fix For: 1.9.5 > > Time Spent: 20m > Remaining Estimate: 0h > > We need a new release with ASM 9.0 to be able to test against Java 16. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DELTASPIKE-1420) Update ASM to 9.1
[ https://issues.apache.org/jira/browse/DELTASPIKE-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated DELTASPIKE-1420: -- Summary: Update ASM to 9.1 (was: Update ASM to 9.0) > Update ASM to 9.1 > - > > Key: DELTASPIKE-1420 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1420 > Project: DeltaSpike > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Proxy-Module >Affects Versions: 1.9.4 >Reporter: Christian Beikov >Assignee: Christian Beikov >Priority: Major > Fix For: 1.9.5 > > Time Spent: 20m > Remaining Estimate: 0h > > We need a new release with ASM 9.0 to be able to test against Java 16. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DELTASPIKE-1416) deltaspike-core-impl.jar does not contain the Main class to execute in your Manifest.MF to Crypto
[
https://issues.apache.org/jira/browse/DELTASPIKE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reassigned DELTASPIKE-1416:
-
Assignee: Mark Struberg
> deltaspike-core-impl.jar does not contain the Main class to execute in your
> Manifest.MF to Crypto
> -
>
> Key: DELTASPIKE-1416
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1416
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
>Affects Versions: 1.9.4
>Reporter: Daniel Dias
>Assignee: Mark Struberg
>Priority: Minor
> Fix For: 1.9.5
>
> Attachments: DELTASPIKE-1416.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [https://deltaspike.apache.org/documentation/encryption.html]
> demo how to run java -jar deltaspike-core-impl.jar encode -masterPassword
> myMasterPassword -masterSalt myMasterSalt
> more in your MANIFEST.MF does not contain the Main-Class that is in META-INF
> of the Core:
> [https://github.com/apache/deltaspike/blob/master/deltaspike/core/impl/src/main/resources/META-INF/MANIFEST.MF]
>
> to resolve, you must include a plugin:
> {code:java}
>
> org.apache.maven.plugins
> maven-jar-plugin
>
>
> src/main/resources/META-INF/MANIFEST.MF
>
>
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
