[jira] [Updated] (DELTASPIKE-873) show error-message on the same page
[ https://issues.apache.org/jira/browse/DELTASPIKE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-873: Attachment: (was: DELTASPIKE-873.patch) show error-message on the same page --- Key: DELTASPIKE-873 URL: https://issues.apache.org/jira/browse/DELTASPIKE-873 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module, Security-Module Affects Versions: 1.3.0 Reporter: Rafael Assignee: Gerhard Petracek Fix For: 1.3.1 currently it just works if a default-error-view is configured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-873) show error-message on the same page
[ https://issues.apache.org/jira/browse/DELTASPIKE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-873. - Resolution: Fixed show error-message on the same page --- Key: DELTASPIKE-873 URL: https://issues.apache.org/jira/browse/DELTASPIKE-873 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module, Security-Module Affects Versions: 1.3.0 Reporter: Rafael Assignee: Gerhard Petracek Fix For: 1.3.1 currently it just works if a default-error-view is configured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-888) Add support for delete a job from the Scheduler
[ https://issues.apache.org/jira/browse/DELTASPIKE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-888: Attachment: DELTASPIKE-888_2.patch Add support for delete a job from the Scheduler --- Key: DELTASPIKE-888 URL: https://issues.apache.org/jira/browse/DELTASPIKE-888 Project: DeltaSpike Issue Type: New Feature Components: Scheduler Reporter: Daniel Cunha (soro) Assignee: Gerhard Petracek Priority: Minor Attachments: DELTASPIKE-888.patch, DELTASPIKE-888_2.patch Delete the identified Job from the Scheduler - and any associated Triggers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-882) Create a new module for proxy
[ https://issues.apache.org/jira/browse/DELTASPIKE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523371#comment-14523371 ] Gerhard Petracek commented on DELTASPIKE-882: - the module is missing in: deltaspike/dist/pom.xml deltaspike/dist/bom/pom.xml deltaspike/dist/full/src/main/distribution/modules-module.xml imo we should move the content of org.apache.deltaspike.core.util.invocation as well. if we add a minimal api, we should use org.apache.deltaspike.proxy as package name imo. Create a new module for proxy - Key: DELTASPIKE-882 URL: https://issues.apache.org/jira/browse/DELTASPIKE-882 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 1.3.0, 1.3.1 Reporter: Rafael Benevides Assignee: Rafael Benevides Priority: Blocker Fix For: 1.4.0 We are now using asm to create our own proxies - with 1.3.0 that was added to the partial bean module - now We replace the optional proxies created in the JSF module for converters/validators with the same approach - the proxy code was moved to ds-core. that works but isn't nice and not that flexible - the goal is an own module side by side with core and all modules which need proxy stuff have core and that new proxy module as dep. (currently the partial-bean and JSF module).It allows to support different versions of asm once it's needed... (e.g. for diff. versions of java if the latest version drops e.g. backward compat. to and old version...) It's already discussed and agreed on the dev list so you can just create a ticket and just move the code + update the release poms so that the new module is part of the release as well... The new module should be called proxy-utils. GAV: org.apache.deltaspike.modules:deltaspike-proxy-module-api *don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't depend on asm and is valid for any proxy (weld-proxy, owb-proxy, javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you would move it ds-core would depend on the proxy-module (which shouldn't be the case). The goal is really that the proxy-module is just needed once you need the partial-bean module and/or the optional proxies in the JSF module so the proxy-module needs to be an optional dep. of the JSF module... but in case of the partial-bean module the proxy-api module is a compile dep. since it's required anyway That's currently the release blocker, because now ds-core has a dependency to a fixed version of asm and so far Core didn't introduce a 3rd party dep. So We need to move to the new module before the next release... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-889) ValidatorWrapper causes filtering of multiple custom validators in ValidatorTagHandler
[ https://issues.apache.org/jira/browse/DELTASPIKE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523249#comment-14523249 ] Gerhard Petracek commented on DELTASPIKE-889: - please add javassist as dependency to get proxied converters/validators (with v1.3.0). however, please also test your application with the latest snapshot of v1.3.1 (since we move to asm and custom proxies). we have arquillian-drone based tests which pass also on wildfly - there shouldn't be an issue. ValidatorWrapper causes filtering of multiple custom validators in ValidatorTagHandler -- Key: DELTASPIKE-889 URL: https://issues.apache.org/jira/browse/DELTASPIKE-889 Project: DeltaSpike Issue Type: Bug Components: JSF-Module Affects Versions: 1.3.0 Environment: JSF 2.2 / Wildfly 8.1 Reporter: Thomas Frühbeck Labels: custom, jsf, validator InjectionAwareApplicationWrapper wraps custom validators. In ValidatorTagHandlerDelegateImpl the check for class equality causes a unique constraint on validators, so effectively filtering all wrapped validators but the first: for (Validator validator : validators) { if (validator.getClass().equals(v.getClass())) { found = true; break; } } if (!found) { evh.addValidator(v); } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (DELTASPIKE-868) Bind Bean Manager to JNDI
[ https://issues.apache.org/jira/browse/DELTASPIKE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek closed DELTASPIKE-868. --- Bind Bean Manager to JNDI - Key: DELTASPIKE-868 URL: https://issues.apache.org/jira/browse/DELTASPIKE-868 Project: DeltaSpike Issue Type: Improvement Components: TestControl Reporter: Rafael Some libraries rely on standard JNDI to lookup BeanManager during its initialization, in such cases the test may fail. An example of that can be found at [1] where tests are failling because of Omnifaces BeanManager initialization. [1]https://github.com/rmpestano/ee6-ds-demo/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
The Alchemist created DELTASPIKE-890: Summary: deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final] at org.jboss.as.weld.WeldModuleResourceLoader.classForName(WeldModuleResourceLoader.java:68) [wildfly-weld-8.2.0.Final.jar:8.2.0.Final] at org.jboss.weld.bootstrap.AnnotatedTypeLoader.loadClass(AnnotatedTypeLoader.java:65) [weld-core-impl-2.2.6.Final.jar:2014-10-03 10:05]
[jira] [Updated] (DELTASPIKE-882) Create a new module for proxy
[ https://issues.apache.org/jira/browse/DELTASPIKE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-882: Affects Version/s: (was: 1.3.0) (was: 1.3.1) Create a new module for proxy - Key: DELTASPIKE-882 URL: https://issues.apache.org/jira/browse/DELTASPIKE-882 Project: DeltaSpike Issue Type: Improvement Components: Core Reporter: Rafael Benevides Assignee: Rafael Benevides Priority: Blocker Fix For: 1.3.1 We are now using asm to create our own proxies - with 1.3.0 that was added to the partial bean module - now We replace the optional proxies created in the JSF module for converters/validators with the same approach - the proxy code was moved to ds-core. that works but isn't nice and not that flexible - the goal is an own module side by side with core and all modules which need proxy stuff have core and that new proxy module as dep. (currently the partial-bean and JSF module).It allows to support different versions of asm once it's needed... (e.g. for diff. versions of java if the latest version drops e.g. backward compat. to and old version...) It's already discussed and agreed on the dev list so you can just create a ticket and just move the code + update the release poms so that the new module is part of the release as well... The new module should be called proxy-utils. GAV: org.apache.deltaspike.modules:deltaspike-proxy-module-api *don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't depend on asm and is valid for any proxy (weld-proxy, owb-proxy, javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you would move it ds-core would depend on the proxy-module (which shouldn't be the case). The goal is really that the proxy-module is just needed once you need the partial-bean module and/or the optional proxies in the JSF module so the proxy-module needs to be an optional dep. of the JSF module... but in case of the partial-bean module the proxy-api module is a compile dep. since it's required anyway That's currently the release blocker, because now ds-core has a dependency to a fixed version of asm and so far Core didn't introduce a 3rd party dep. So We need to move to the new module before the next release... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-882) Create a new module for proxy
[ https://issues.apache.org/jira/browse/DELTASPIKE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-882: Fix Version/s: (was: 1.4.0) 1.3.1 Create a new module for proxy - Key: DELTASPIKE-882 URL: https://issues.apache.org/jira/browse/DELTASPIKE-882 Project: DeltaSpike Issue Type: Improvement Components: Core Reporter: Rafael Benevides Assignee: Rafael Benevides Priority: Blocker Fix For: 1.3.1 We are now using asm to create our own proxies - with 1.3.0 that was added to the partial bean module - now We replace the optional proxies created in the JSF module for converters/validators with the same approach - the proxy code was moved to ds-core. that works but isn't nice and not that flexible - the goal is an own module side by side with core and all modules which need proxy stuff have core and that new proxy module as dep. (currently the partial-bean and JSF module).It allows to support different versions of asm once it's needed... (e.g. for diff. versions of java if the latest version drops e.g. backward compat. to and old version...) It's already discussed and agreed on the dev list so you can just create a ticket and just move the code + update the release poms so that the new module is part of the release as well... The new module should be called proxy-utils. GAV: org.apache.deltaspike.modules:deltaspike-proxy-module-api *don't* move org.apache.deltaspike.core.util.ProxyUtils - because it doesn't depend on asm and is valid for any proxy (weld-proxy, owb-proxy, javassist-proxy,...) We support at all + it's needed a lot in ds-core. If you would move it ds-core would depend on the proxy-module (which shouldn't be the case). The goal is really that the proxy-module is just needed once you need the partial-bean module and/or the optional proxies in the JSF module so the proxy-module needs to be an optional dep. of the JSF module... but in case of the partial-bean module the proxy-api module is a compile dep. since it's required anyway That's currently the release blocker, because now ds-core has a dependency to a fixed version of asm and so far Core didn't introduce a 3rd party dep. So We need to move to the new module before the next release... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Unify internal configuration
it's a bit more complex and we need an additional marker-interface to keep all benefits we had before, however, +1 for committing it (because it's closer to the base which gets extended). regards, gerhard 2015-04-30 15:31 GMT+02:00 Gerhard Petracek gerhard.petra...@gmail.com: i've to check some details, however, basically +1 regards, gerhard 2015-04-30 15:22 GMT+02:00 Ron Smeral rsme...@apache.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi again, here's my proposal for a solution to the slight conf. API mess: https://github.com/rsmeral/deltaspike/commit/d270ac0cb6d5ed47a5912365f95 9145b12da0e99 https://github.com/rsmeral/deltaspike/commit/d270ac0cb6d5ed47a5912365f959145b12da0e99 Main change: a new type-safe fluent API for typed config resolution Connection conn = ConfigResolver.resolve(db.connection) .as(Connection.class, new ConnectionConverter()) .parameterizedBy(db.vendor) .withCurrentProjectStage(true) .strictly() .withDefault(whatever) .getValue(); or simply String conn = ConfigResolver.resolve(db.connection).getValue(); This would obsolete TypedConfig since ConfigResolver would be implicitly type-aware and it brings the type conversion functions from DefaultConfigPropertyProducer and TypedConfig into ConfigResolver. We would also mark the dynamic configurations with some interface (currently DeltaSpikeConfig), mark the static ones with another (e.g. DeltaSpikeBaseConfig). Check out the commit (and also DELTASPIKE-885) for more details. Thanks for any comments, reviews and suggestions :) R. On 28.4.2015 12:33, Ron Smeral wrote: Thanks for the clarification. I'll try to answer my own question then, please comment if anything is not right: * why does PropertyFileConfig implement DeltaSpikeConfig? Doesn't make sense to me, given the purpose of DeltaSpikeConfig. I guess this was not intentional and is a bug. I'll file an issue for this. * is there any reason why the ones from the first category (TransactionConfig and JsfModuleConfig) couldn't be implemented using the second way (TypedConfig)? They couldn't, synce TypedConfig is for static boot-time configuration . * if none of the above is applicable, then: shouldn't the TypedConfig ones (CoreBaseConfig, ...) implement DeltaSpikeConfig as well? I understand that we'd like to keep DeltaSpikeConfig as the marker for all dynamic configuration, i.e. the way it's used now. Maybe we could introduce a new interface to expose the TypedConfig-based interfaces, sth. like DeltaSpikeBaseConfig. R. On 27.4.2015 21:36, Mark Struberg wrote: Hi! Sorry for brevity. Like to quickly sum up what we discussed on irc: .) DeltaSpikeConfig is merely a marker interface for interfaces/classes which can be used to define the behaviour of certain DeltaSpike features at runtimy. Since this is a class it can return different values for each invocation. This is e.g. useful for the LocaleResoler configuration (each user request could result in another Locale). Otoh this configuration mechanism is only available once the CDI container finally got booted. So it can NOT be used to e.g. configure CDI Extensions itself. .) ConfigResolver based configuration. The TypeConfig is basically a object which contains the config-key + code to access the value. This mechanism is purely JavaSE and thus can also be used to configure Extensions itself as well. It’s also more the kind of a ’static’ configuration. LieGrue, strub Am 27.04.2015 um 19:38 schrieb Ron Smeral rsme...@apache.org: Hi, DeltaSpike itself is currently configured in at least 2 different ways: * using interfaces extending DeltaSpikeConfig: ** org.apache.deltaspike.jpa.api.transaction.TransactionConfig ** org.apache.deltaspike.jsf.api.config.JsfModuleConfig (** PropertyFileConfig (Why? It does not configure just DS itself.)) * using interfaces with static TypedConfig instances: ** org.apache.deltaspike.testcontrol.impl.jsf.MyFacesTestBaseConfig ** org.apache.deltaspike.testcontrol.api.junit.TestBaseConfig ** org.apache.deltaspike.scheduler.impl.SchedulerBaseConfig ** org.apache.deltaspike.jsf.api.config.base.JsfBaseConfig ** org.apache.deltaspike.core.api.config.base.CoreBaseConfig My questions are: * why does PropertyFileConfig implement DeltaSpikeConfig? Doesn't make sense to me, given the purpose of DeltaSpikeConfig. * is there any reason why the ones from the first category (TransactionConfig and JsfModuleConfig) couldn't be implemented using the second way (TypedConfig)? * if none of the above is applicable, then: shouldn't the TypedConfig ones (CoreBaseConfig, ...) implement DeltaSpikeConfig as well? I hacked up a quick suggestion of how this could look: https://github.com/rsmeral/deltaspike/commit/b5be1c79b67d6a15b30036ed 9 0a 7b90fba9b5e00 Currently, having two ways
[jira] [Updated] (DELTASPIKE-873) show error-message on the same page
[ https://issues.apache.org/jira/browse/DELTASPIKE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-873: Attachment: DELTASPIKE-873_2.patch show error-message on the same page --- Key: DELTASPIKE-873 URL: https://issues.apache.org/jira/browse/DELTASPIKE-873 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module, Security-Module Affects Versions: 1.3.0 Reporter: Rafael Assignee: Gerhard Petracek Fix For: 1.3.1 Attachments: DELTASPIKE-873_2.patch currently it just works if a default-error-view is configured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-873) show error-message on the same page
[ https://issues.apache.org/jira/browse/DELTASPIKE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-873. - Resolution: Fixed show error-message on the same page --- Key: DELTASPIKE-873 URL: https://issues.apache.org/jira/browse/DELTASPIKE-873 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module, Security-Module Affects Versions: 1.3.0 Reporter: Rafael Assignee: Gerhard Petracek Fix For: 1.3.1 currently it just works if a default-error-view is configured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-873) show error-message on the same page
[ https://issues.apache.org/jira/browse/DELTASPIKE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-873: Attachment: (was: DELTASPIKE-873_2.patch) show error-message on the same page --- Key: DELTASPIKE-873 URL: https://issues.apache.org/jira/browse/DELTASPIKE-873 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module, Security-Module Affects Versions: 1.3.0 Reporter: Rafael Assignee: Gerhard Petracek Fix For: 1.3.1 currently it just works if a default-error-view is configured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-889) ValidatorWrapper causes filtering of multiple custom validators in ValidatorTagHandler
[ https://issues.apache.org/jira/browse/DELTASPIKE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-889: Labels: (was: custom jsf validator) ValidatorWrapper causes filtering of multiple custom validators in ValidatorTagHandler -- Key: DELTASPIKE-889 URL: https://issues.apache.org/jira/browse/DELTASPIKE-889 Project: DeltaSpike Issue Type: Bug Components: JSF-Module Affects Versions: 1.3.0 Environment: JSF 2.2 / Wildfly 8.1 Reporter: Thomas Frühbeck InjectionAwareApplicationWrapper wraps custom validators. In ValidatorTagHandlerDelegateImpl the check for class equality causes a unique constraint on validators, so effectively filtering all wrapped validators but the first: for (Validator validator : validators) { if (validator.getClass().equals(v.getClass())) { found = true; break; } } if (!found) { evh.addValidator(v); } -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-868) Bind Bean Manager to JNDI
[ https://issues.apache.org/jira/browse/DELTASPIKE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-868: Assignee: (was: Gerhard Petracek) Bind Bean Manager to JNDI - Key: DELTASPIKE-868 URL: https://issues.apache.org/jira/browse/DELTASPIKE-868 Project: DeltaSpike Issue Type: Improvement Components: TestControl Reporter: Rafael Some libraries rely on standard JNDI to lookup BeanManager during its initialization, in such cases the test may fail. An example of that can be found at [1] where tests are failling because of Omnifaces BeanManager initialization. [1]https://github.com/rmpestano/ee6-ds-demo/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-868) Bind Bean Manager to JNDI
[ https://issues.apache.org/jira/browse/DELTASPIKE-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-868. - Resolution: Won't Fix Fix Version/s: (was: 1.4.0) omnifaces2 does that check in a ServletContainerInitializer which doesn't allow a portable workaround provided by deltaspike and therefore users have to do the setup manually in the servlet-container they are using. Bind Bean Manager to JNDI - Key: DELTASPIKE-868 URL: https://issues.apache.org/jira/browse/DELTASPIKE-868 Project: DeltaSpike Issue Type: Improvement Components: TestControl Reporter: Rafael Assignee: Gerhard Petracek Some libraries rely on standard JNDI to lookup BeanManager during its initialization, in such cases the test may fail. An example of that can be found at [1] where tests are failling because of Omnifaces BeanManager initialization. [1]https://github.com/rmpestano/ee6-ds-demo/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-891) check for InvocationTargetException in ExecutableCallbackDescriptor
[ https://issues.apache.org/jira/browse/DELTASPIKE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-891. - Resolution: Fixed check for InvocationTargetException in ExecutableCallbackDescriptor --- Key: DELTASPIKE-891 URL: https://issues.apache.org/jira/browse/DELTASPIKE-891 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 1.3.0 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.3.1 Attachments: DELTASPIKE-891.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (DELTASPIKE-873) show error-message on the same page
[ https://issues.apache.org/jira/browse/DELTASPIKE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek reopened DELTASPIKE-873: - show error-message on the same page --- Key: DELTASPIKE-873 URL: https://issues.apache.org/jira/browse/DELTASPIKE-873 Project: DeltaSpike Issue Type: Improvement Components: JSF-Module, Security-Module Affects Versions: 1.3.0 Reporter: Rafael Assignee: Gerhard Petracek Fix For: 1.3.1 currently it just works if a default-error-view is configured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-891) check for InvocationTargetException in ExecutableCallbackDescriptor
[ https://issues.apache.org/jira/browse/DELTASPIKE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek updated DELTASPIKE-891: Attachment: DELTASPIKE-891.patch check for InvocationTargetException in ExecutableCallbackDescriptor --- Key: DELTASPIKE-891 URL: https://issues.apache.org/jira/browse/DELTASPIKE-891 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 1.3.0 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.3.1 Attachments: DELTASPIKE-891.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523546#comment-14523546 ] Daniel Cunha (soro) commented on DELTASPIKE-890: It seem some problem in your module configuration. The wildfly cannot loading the javax.faces.event.PhaseListener class. deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389)
[jira] [Created] (DELTASPIKE-891) check for InvocationTargetException in ExecutableCallbackDescriptor
Gerhard Petracek created DELTASPIKE-891: --- Summary: check for InvocationTargetException in ExecutableCallbackDescriptor Key: DELTASPIKE-891 URL: https://issues.apache.org/jira/browse/DELTASPIKE-891 Project: DeltaSpike Issue Type: Improvement Components: Core Affects Versions: 1.3.0 Reporter: Gerhard Petracek Assignee: Gerhard Petracek Fix For: 1.3.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-890. - Resolution: Won't Fix thx for reporting the issue, however, it's currently a known limitation of jboss-modules in wildfly (afaik the wildfly team is going to address it for the next release). deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389)
[jira] [Commented] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523581#comment-14523581 ] John D. Ament commented on DELTASPIKE-890: -- Agreed, there's an ambiguious install as module which needs to be clarified. deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at
[jira] [Comment Edited] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523546#comment-14523546 ] Daniel Cunha (soro) edited comment on DELTASPIKE-890 at 5/1/15 6:05 PM: It seem some problem in your module configuration. The wildfly cannot loading the javax.faces.* classes. was (Author: danielsoro): It seem some problem in your module configuration. The wildfly cannot loading the javax.faces.event.PhaseListener class. deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at
[jira] [Commented] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523588#comment-14523588 ] John D. Ament commented on DELTASPIKE-890: -- Is there some wildfly defect you can refer? deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at
[jira] [Commented] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523956#comment-14523956 ] The Alchemist commented on DELTASPIKE-890: -- Thanks, guys! I'm just using the module.xml that comes with the binary distribution. Is there a workaround that's recommended? deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]
[jira] [Commented] (DELTASPIKE-890) deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final
[ https://issues.apache.org/jira/browse/DELTASPIKE-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14523981#comment-14523981 ] Daniel Cunha (soro) commented on DELTASPIKE-890: [~the_alchemist], That will help you: http://deltaspike.apache.org/documentation/configure.html deployment errors for DeltaSpike 1.3.0 under Wildfly 8.2.0.Final Key: DELTASPIKE-890 URL: https://issues.apache.org/jira/browse/DELTASPIKE-890 Project: DeltaSpike Issue Type: Bug Affects Versions: 1.3.0 Environment: Wildfly 8.2.0.Final Java 8u45 DS 1.3.0 Reporter: The Alchemist h3. Stack Trace {noformat} 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-3) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$3 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-4) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$2 because of underlying class loading error: Type javax.faces.event.PhaseId from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,960 INFO [org.jboss.weld.Bootstrap] (weld-worker-5) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecycleBroadcaster$1 because of underlying class loading error: Type javax.faces.event.PhaseListener from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,961 INFO [org.jboss.weld.Bootstrap] (weld-worker-8) WELD-000119: Not generating any bean definitions from org.apache.deltaspike.jsf.impl.injection.ManagedArtifactResolver because of underlying class loading error: Type javax.faces.validator.Validator from [Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))] not found. If this is unexpected, enable DEBUG logging to see the full error. 17:46:46,954 WARN [org.jboss.modules] (weld-worker-7) Failed to define class org.apache.deltaspike.jsf.impl.listener.phase.JsfRequestLifecyclePhaseListener in Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base)): java.lang.LinkageError: Failed to link org/apache/deltaspike/jsf/impl/listener/phase/JsfRequestLifecyclePhaseListener (Module org.apache.deltaspike.modules:main from local module loader @4973813a (finder: local module finder @6321e813 (roots: /usr/local/wildfly-8.2.0.Final/modules,/usr/local/wildfly-8.2.0.Final/modules/system/layers/base))) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at
[jira] [Resolved] (DELTASPIKE-888) Add support for delete a job from the Scheduler
[ https://issues.apache.org/jira/browse/DELTASPIKE-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gerhard Petracek resolved DELTASPIKE-888. - Resolution: Fixed Add support for delete a job from the Scheduler --- Key: DELTASPIKE-888 URL: https://issues.apache.org/jira/browse/DELTASPIKE-888 Project: DeltaSpike Issue Type: New Feature Components: Scheduler Reporter: Daniel Cunha (soro) Assignee: Gerhard Petracek Priority: Minor Attachments: DELTASPIKE-888.patch, DELTASPIKE-888_2.patch Delete the identified Job from the Scheduler - and any associated Triggers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DELTASPIKE-889) ValidatorWrapper causes filtering of multiple custom validators in ValidatorTagHandler
Thomas Frühbeck created DELTASPIKE-889: -- Summary: ValidatorWrapper causes filtering of multiple custom validators in ValidatorTagHandler Key: DELTASPIKE-889 URL: https://issues.apache.org/jira/browse/DELTASPIKE-889 Project: DeltaSpike Issue Type: Bug Components: JSF-Module Affects Versions: 1.3.0 Environment: JSF 2.2 / Wildfly 8.1 Reporter: Thomas Frühbeck InjectionAwareApplicationWrapper wraps custom validators. In ValidatorTagHandlerDelegateImpl the check for class equality causes a unique constraint on validators, so effectively filtering all wrapped validators but the first: for (Validator validator : validators) { if (validator.getClass().equals(v.getClass())) { found = true; break; } } if (!found) { evh.addValidator(v); } -- This message was sent by Atlassian JIRA (v6.3.4#6332)