February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8168) Inter-application depdendency injection failure

by Daniel Huss (JIRA)

[ https://issues.jboss.org/browse/WFLY-8168?page=com.atlassian.jira.plugin.... ] Daniel Huss updated WFLY-8168: ------------------------------ Attachment: inter-app-dependency.zip > Inter-application depdendency injection failure > ----------------------------------------------- > > Key: WFLY-8168 > URL: https://issues.jboss.org/browse/WFLY-8168 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.1.0.Final > Reporter: Daniel Huss > Assignee: Stuart Douglas > Attachments: inter-app-dependency.zip > > > I was trying to implement a simple use case: > * There's some service.ear providing a _Service_ > * service.ear has a module alias _ModuleAlias_ > * There are add-ons to _Service _that are dynamically deployed as jar files that depend on _ModuleAlias_ via manifest entries > * The add-ons register/unregister themselves with _Service_ on deployment/undeployment > The [CDI Reference|https://docs.jboss.org/author/display/WFLY10/CDI+Reference] states that we can depend on other deployments, so this seemed to be the easiest way to get the job done with JEE. > The registration-on-deployment thing would look like this: > {code} > public void register(@Observes @Initialized(ApplicationScoped.class) Object init, AddonContext context) > { > context.register(this); > } > {code} > All I get is "WELD-001408: Unsatisfied dependencies". > So I've created a minimalistic example of the inter-app dependency scenario. See attachment. I've tried moving around module-alias, CDI annotations.... it just won't work. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-973) Add configuration option for DigestSaslServer to support additional protocols

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-973: ------------------------------------ Summary: Add configuration option for DigestSaslServer to support additional protocols Key: ELY-973 URL: https://issues.jboss.org/browse/ELY-973 Project: WildFly Elytron Issue Type: Enhancement Components: SASL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta28 Older clients may attempt to authenticate using both remote and remoting as the protocol. Add a configuration option to specify additional protocols that can be accepted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2311) System property wildfly.config.url doesn't resolve correctly relative paths

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2311?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-8001 to WFCORE-2311: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2311 (was: WFLY-8001) Component/s: Security (was: Security) > System property wildfly.config.url doesn't resolve correctly relative paths > --------------------------------------------------------------------------- > > Key: WFCORE-2311 > URL: https://issues.jboss.org/browse/WFCORE-2311 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Priority: Critical > > When an AS client runs with custom Elytron configuration specified and system property {{wildfly.config.url}} is used to provide the configuration (as a relative path), then the resolved URI is not correct. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2310) Upgrade WildFly Client Config to 1.0.0.Beta2

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2310?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-8973 to WFCORE-2310: ------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2310 (was: JBEAP-8973) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Upgrade WildFly Client Config to 1.0.0.Beta2 > -------------------------------------------- > > Key: WFCORE-2310 > URL: https://issues.jboss.org/browse/WFCORE-2310 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8141) CachedConnectionManager add operation excepts no parameters anymore

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8141?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-8141: -------------------------------------- Assignee: Brian Stansberry (was: Ingo Weiss) > CachedConnectionManager add operation excepts no parameters anymore > ------------------------------------------------------------------- > > Key: WFLY-8141 > URL: https://issues.jboss.org/browse/WFLY-8141 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 11.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Brian Stansberry > Priority: Critical > > Fix for WFLY-2640 broke :add operation for cached-connection-manager > scipts that do > {noformat} > /profile=default-web/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true") > {noformat} > {noformat} > /subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true") > {noformat} > now fail with > {{Operation 'add' does not expect any property.}} > This breaks our quickstarts -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8141) CachedConnectionManager add operation excepts no parameters anymore

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8141?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8141: ---------------------------------------- Scratch my #1 and #2 above. I think these are the requirements around this: 1) If a user *boots* a config with subsystem=jca in it but nothing that specifies CCM use, they should be able to go to the CLI and do this: [standalone@localhost:9999 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=install,value=true) That should work even though their config didn't specify anything to trigger adding the /subsystem=jca/cached-connection-manager=cached-connection-manage resource. This needs to work to be compatible with previous behavior, not because it's good. 2) Users starts a standalone server or domain profile with no JCA subsystem and then can do this: /profile=default-web/subsystem="jca":add() /profile=default-web/subsystem="jca"/cached-connection-manager="cached-connection-manager":add() (For the standalone server case ignore the /profile=default-web part). This needs to work or we have a regression. That's the main point of this JIRA. Fixing this will also fix Alexey's problem. 3) We want the WFY-2640 scenario to work: a) boot with JCA subsystem present b) With CLI: {code} [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:remove { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9990 /] :reload { "outcome" => "success", "result" => undefined } [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:add { "outcome" => "success", "result" => undefined } {code} The only way I see to meet all these objectives is to make the add handler public again, and rewrite it to not fail if the resource is already present, but is configured with all default values (i.e. interpret that state as meaning the resource was auto-added by the parser). The resource must always be present after boot for 1) to work. The add op must be public for 2). And for 3) to work in combination with 1), the add handler can't reject the add just because the parser already auto-added the resource. Having the following work is NOT a requirement: a) start with no JCA b) With CLI /subsystem="jca":add() /subsystem="jca"/cached-connection-manager="cached-connection-manager":write-attribute(name=install,value=true) It's the parser that "auto-adds" the CCM resource, allowing you to do a write-attribute to the CCM. Here there is no parser involved so you have to add it before you can write-attribute. Making the above work would be possible via the step adding tricks I mentioned in my last post. But it's not really valid behavior and in a mixed version domain the legacy slaves wouldn't be able to handle it. So I don't think we should do it. Instead we should regard 1) working as being a bug, but one that we aren't fixing because fixing it might break people. [~maeste] Without objection I like to go ahead and implement it this way. > CachedConnectionManager add operation excepts no parameters anymore > ------------------------------------------------------------------- > > Key: WFLY-8141 > URL: https://issues.jboss.org/browse/WFLY-8141 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 11.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Ingo Weiss > Priority: Critical > > Fix for WFLY-2640 broke :add operation for cached-connection-manager > scipts that do > {noformat} > /profile=default-web/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true") > {noformat} > {noformat} > /subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true") > {noformat} > now fail with > {{Operation 'add' does not expect any property.}} > This breaks our quickstarts -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1446) Implement RuleUnit

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1446: ----------------------------------- Summary: Implement RuleUnit Key: DROOLS-1446 URL: https://issues.jboss.org/browse/DROOLS-1446 Project: Drools Issue Type: Feature Request Reporter: Mario Fusco Assignee: Edson Tirelli -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1446) Implement RuleUnit

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1446?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1446: ----------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > Implement RuleUnit > ------------------ > > Key: DROOLS-1446 > URL: https://issues.jboss.org/browse/DROOLS-1446 > Project: Drools > Issue Type: Feature Request > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1446) Implement RuleUnit

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1446?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1446: -------------------------------- Component/s: core engine > Implement RuleUnit > ------------------ > > Key: DROOLS-1446 > URL: https://issues.jboss.org/browse/DROOLS-1446 > Project: Drools > Issue Type: Feature Request > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1085) No audit feature for security-realm

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1085?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1085: ----------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 912233|https://bugzilla.redhat.com/show_bug.cgi?id=912233] from ASSIGNED to CLOSED > No audit feature for security-realm > ----------------------------------- > > Key: WFLY-1085 > URL: https://issues.jboss.org/browse/WFLY-1085 > Project: WildFly > Issue Type: Feature Request > Components: Logging > Environment: EAP 6.0.x > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > There is no auditing feature for security-realm. Need the feature like audit provider for security-domain. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2017