September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBFORUMS-309) HHTP request not found in custom Login Module in JBOSS 7

by joy sen (JIRA)

[ https://issues.jboss.org/browse/JBFORUMS-309?page=com.atlassian.jira.plug... ] joy sen updated JBFORUMS-309: ----------------------------- Description: I want to use the HTTP request object in custom login module which extends AbstractServerLoginModule. In JBOSS 6.x this can be fetched from PolicyContext or FacesContext Object. But from 7.x onwards these cannot be found. Any approach to share information between authentication and login modules (Using ThreadLocal/Faces Contex/Policy Context) does not work. Need a way out to share information between authentication and login in EAP 6.4 version. was: I want to use the HTTP request object in custom login module which extends AbstractServerLoginModule. In JBOSS 6.x this can be fetched from PolicyContext or FacesContext Object. But from 7.x onwards these cannot be found. Any approach to share information between authentication and login modules (Using ThreadLocal/Faces Contex/Policy Context) does not work. Need a way out to share information between authentication in login in EAP 6.4 version. > HHTP request not found in custom Login Module in JBOSS 7 > -------------------------------------------------------- > > Key: JBFORUMS-309 > URL: https://issues.jboss.org/browse/JBFORUMS-309 > Project: JBoss Forums > Issue Type: Bug > Environment: EAP 6.4 > Reporter: joy sen > Assignee: Luca Stancapiano > Priority: Blocker > > I want to use the HTTP request object in custom login module which extends AbstractServerLoginModule. > In JBOSS 6.x this can be fetched from PolicyContext or FacesContext Object. > But from 7.x onwards these cannot be found. Any approach to share information between authentication and login modules (Using ThreadLocal/Faces Contex/Policy Context) does not work. > Need a way out to share information between authentication and login in EAP 6.4 version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4082) Fix common.sh setDefaultModularJvmOptions() to grep all function arguments

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4082?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-4082: ---------------------------------- Component/s: Scripts > Fix common.sh setDefaultModularJvmOptions() to grep all function arguments > -------------------------------------------------------------------------- > > Key: WFCORE-4082 > URL: https://issues.jboss.org/browse/WFCORE-4082 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 6.0.1.Final > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 7.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2949) [DMN Designer] Change of data type is not propagated to manage dialog

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2949?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2949: ------------------------------------- [~karreiro] hi could you please double check jira number? DROOLS-2762 seems to me unrelated to this DROOLS-2949 > [DMN Designer] Change of data type is not propagated to manage dialog > --------------------------------------------------------------------- > > Key: DROOLS-2949 > URL: https://issues.jboss.org/browse/DROOLS-2949 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Labels: drools-tools > Attachments: Screenshot from 2018-08-31 14-59-52.png, itemDef-dependency.dmn > > > User is able to achieve inconsistent state in *Manage custom data type dialog* See the attached picture. There is changed top level itemDefinition *Address* to *Adress111* however the itemDefinition *Person* stil shows it address field as *Adress*, it should be *Adress111* too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2945) DMN Designer - opening data type dialog shows warning in browser console

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2945?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2945: -------------------------------- Description: Opening *manage custom data types dialog* shows warning in the browser console. {code} org.kie.workbench.drools.KIEDroolsWebapp-0.js:22170 13:54:49 WARNING [TemplateUtil] Replacing Element type [SPAN] in org/kie/workbench/common/dmn/client/editors/types/listview/DataTypeListItemView.html with type [TD] for type in org.kie.workbench.common.dmn.client.editors.types.listview.DataTypeListItemView {code} h3. Acceptance test Check browser console after *manage custom data types* dialog opening in - IE11 - Chrome - Firefox was: Opening *manage custom data types dialog* shows warning in the browser console. {code} org.kie.workbench.drools.KIEDroolsWebapp-0.js:22170 13:54:49 WARNING [TemplateUtil] Replacing Element type [SPAN] in org/kie/workbench/common/dmn/client/editors/types/listview/DataTypeListItemView.html with type [TD] for type in org.kie.workbench.common.dmn.client.editors.types.listview.DataTypeListItemView {code} h3. Acceptance test Check browser console after *manage custom data types* dialog opening in IE11, Chrome, Firefox > DMN Designer - opening data type dialog shows warning in browser console > ------------------------------------------------------------------------ > > Key: DROOLS-2945 > URL: https://issues.jboss.org/browse/DROOLS-2945 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > Attachments: Port Clearance Rules - Solution 3.dmn > > > Opening *manage custom data types dialog* shows warning in the browser console. > {code} > org.kie.workbench.drools.KIEDroolsWebapp-0.js:22170 13:54:49 WARNING [TemplateUtil] Replacing Element type [SPAN] in org/kie/workbench/common/dmn/client/editors/types/listview/DataTypeListItemView.html with type [TD] for type in org.kie.workbench.common.dmn.client.editors.types.listview.DataTypeListItemView > {code} > h3. Acceptance test > Check browser console after *manage custom data types* dialog opening in > - IE11 > - Chrome > - Firefox -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2945) DMN Designer - opening data type dialog shows warning in browser console

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2945?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2945: -------------------------------- Description: Opening *manage custom data types dialog* shows warning in the browser console. {code} org.kie.workbench.drools.KIEDroolsWebapp-0.js:22170 13:54:49 WARNING [TemplateUtil] Replacing Element type [SPAN] in org/kie/workbench/common/dmn/client/editors/types/listview/DataTypeListItemView.html with type [TD] for type in org.kie.workbench.common.dmn.client.editors.types.listview.DataTypeListItemView {code} h3. Acceptance test Check browser console after *manage custom data types* dialog opening in IE11, Chrome, Firefox was: Opening *manage custom data types dialog* shows warning in the browser console. {code} org.kie.workbench.drools.KIEDroolsWebapp-0.js:22170 13:54:49 WARNING [TemplateUtil] Replacing Element type [SPAN] in org/kie/workbench/common/dmn/client/editors/types/listview/DataTypeListItemView.html with type [TD] for type in org.kie.workbench.common.dmn.client.editors.types.listview.DataTypeListItemView {code} > DMN Designer - opening data type dialog shows warning in browser console > ------------------------------------------------------------------------ > > Key: DROOLS-2945 > URL: https://issues.jboss.org/browse/DROOLS-2945 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > Attachments: Port Clearance Rules - Solution 3.dmn > > > Opening *manage custom data types dialog* shows warning in the browser console. > {code} > org.kie.workbench.drools.KIEDroolsWebapp-0.js:22170 13:54:49 WARNING [TemplateUtil] Replacing Element type [SPAN] in org/kie/workbench/common/dmn/client/editors/types/listview/DataTypeListItemView.html with type [TD] for type in org.kie.workbench.common.dmn.client.editors.types.listview.DataTypeListItemView > {code} > h3. Acceptance test > Check browser console after *manage custom data types* dialog opening in IE11, Chrome, Firefox -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10967) Jaeger Tracing: No sender found

by Harald Wellmann (JIRA)

Harald Wellmann created WFLY-10967: -------------------------------------- Summary: Jaeger Tracing: No sender found Key: WFLY-10967 URL: https://issues.jboss.org/browse/WFLY-10967 Project: WildFly Issue Type: Bug Components: MP OpenTracing Affects Versions: 14.0.0.Final Reporter: Harald Wellmann I'm not really sure what the intended behaviour is, but is seems that MicroProfile OpenTracing does not work out of the box. When deploying a JAX-RS + CDI application, I get the following warning {noformat} 16:37:49,023 WARN [io.jaegertracing.internal.senders.SenderResolver] (ServerService Thread Pool -- 73) No suitable sender found. Using NoopSender, meaning that data will not be sent anywhere! {noformat} My guess is that the module configuration is not quite correct. After adding the following dependencies, things look better: module io.jaegertracing.jaeger-core: {code:xml} <module name="io.jaegertracing.jaeger-thrift" services="import"/> {code} module io.jaegertracing.jaeger-thrift: {code:xml} <module name="org.apache.thrift"/> {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10966) Add version 8 of the Undertow subsystem schema and model

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-10966: --------------------------------------- Summary: Add version 8 of the Undertow subsystem schema and model Key: WFLY-10966 URL: https://issues.jboss.org/browse/WFLY-10966 Project: WildFly Issue Type: Task Components: Web (Undertow) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 15.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10829) Exclude ironjacamar-spec-api from the transitive depenencies

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10829?page=com.atlassian.jira.plugin... ] Lin Gao reassigned WFLY-10829: ------------------------------ Assignee: Lin Gao (was: Stefano Maestri) > Exclude ironjacamar-spec-api from the transitive depenencies > ------------------------------------------------------------ > > Key: WFLY-10829 > URL: https://issues.jboss.org/browse/WFLY-10829 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Kabir Khan > Assignee: Lin Gao > > Although not part of the server runtime, the ironjacamar-spec-api is included as a transitive dependency. This fixes it: > {code} > --- pom.xml > +++ pom.xml > @@ -4314,6 +4326,10 @@ > <version>\${version.org.jboss.ironjacamar}</version> > <exclusions> > <exclusion> > + <artifactId>ironjacamar-spec-api</artifactId> > + <groupId>org.jboss.ironjacamar</groupId> > + </exclusion> > + <exclusion> > <artifactId>jbossxb</artifactId> > <groupId>org.jboss</groupId> > </exclusion> > @@ -4346,6 +4362,10 @@ > <version>\${version.org.jboss.ironjacamar}</version> > <exclusions> > <exclusion> > + <groupId>org.jboss.ironjacamar</groupId> > + <artifactId>ironjacamar-spec-api</artifactId> > + </exclusion> > + <exclusion> > <artifactId>jboss-integration</artifactId> > <groupId>org.jboss.integration</groupId> > </exclusion> > @@ -4376,6 +4396,10 @@ > <version>\${version.org.jboss.ironjacamar}</version> > <exclusions> > <exclusion> > + <groupId>org.jboss.ironjacamar</groupId> > + <artifactId>ironjacamar-spec-api</artifactId> > + </exclusion> > + <exclusion> > <artifactId>jboss-common-core</artifactId> > <groupId>org.jboss</groupId> > </exclusion> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2018