May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ] Tomas David updated DROOLS-1511: -------------------------------- Environment: DevStudio 10 + IS 10.3.0.CR2 Eclipse Neon + Drools plugin 7.0.0-SNAPSHOT was: DevStudio 10 Eclipse Neon + Drools plugin 7.0.0-SNAPSHOT > NullPointerException when running sample projects > ------------------------------------------------- > > Key: DROOLS-1511 > URL: https://issues.jboss.org/browse/DROOLS-1511 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: DevStudio 10 + IS 10.3.0.CR2 > Eclipse Neon + Drools plugin 7.0.0-SNAPSHOT > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Blocker > Labels: reported-by-qe > > NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created. > Eclipse log: > !SESSION 2017-04-04 12:39:38.638 ----------------------------------------------- > eclipse.buildId=4.6.3.M20170301-0400 > java.version=1.8.0_121 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737 > !MESSAGE Internal error in Drools Plugin: > !STACK 1 > Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'] > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112) > at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122) > at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739 > !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1511) NullPointerException when running sample projects

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1511?page=com.atlassian.jira.plugi... ] Tomas David updated DROOLS-1511: -------------------------------- Environment: DevStudio 10 Eclipse Neon + Drools plugin 7.0.0-SNAPSHOT was: Eclipse Neon Drools plugin 7.0.0-SNAPSHOT > NullPointerException when running sample projects > ------------------------------------------------- > > Key: DROOLS-1511 > URL: https://issues.jboss.org/browse/DROOLS-1511 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Environment: DevStudio 10 > Eclipse Neon + Drools plugin 7.0.0-SNAPSHOT > Reporter: Tomas David > Assignee: Robert (Bob) Brodt > Priority: Blocker > Labels: reported-by-qe > > NullPointerException is thrown when running sample project using Drools and Java Runtime classes because KieSession is not created. > Eclipse log: > !SESSION 2017-04-04 12:39:38.638 ----------------------------------------------- > eclipse.buildId=4.6.3.M20170301-0400 > java.version=1.8.0_121 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product > !ENTRY org.drools.eclipse 4 120 2017-04-04 12:41:31.737 > !MESSAGE Internal error in Drools Plugin: > !STACK 1 > Java Model Exception: Java Model Status [Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject'] > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3097) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3059) > at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3112) > at org.drools.eclipse.util.DroolsRuntimeManager.addBuilder(DroolsRuntimeManager.java:122) > at org.drools.eclipse.action.ConvertToDroolsProjectAction.run(ConvertToDroolsProjectAction.java:45) > at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5227) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4561) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4151) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > !SUBENTRY 1 org.eclipse.jdt.core 4 977 2017-04-04 12:41:31.739 > !MESSAGE Build path contains duplicate entry: 'DROOLS/Drools' for project 'TestProject' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8774) Race between SSO service start and deployment

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-8774: ------------------------------------ Summary: Race between SSO service start and deployment Key: WFLY-8774 URL: https://issues.jboss.org/browse/WFLY-8774 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8775) Race between SSO service start and deployment

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-8775: ------------------------------------ Summary: Race between SSO service start and deployment Key: WFLY-8775 URL: https://issues.jboss.org/browse/WFLY-8775 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2810) Add "hasCapability" to CapabilityServiceSupport

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2810: ---------------------------------------- Summary: Add "hasCapability" to CapabilityServiceSupport Key: WFCORE-2810 URL: https://issues.jboss.org/browse/WFCORE-2810 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Let services do capability checks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8772) Deployments referencing outbound connection with authentication context always use Elytron default-authentication-context

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8772?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-8772: ---------------------------------- As mentioned in chat, here's what was happening for the legacy ROC case: 1) In RemoteOutboundConnectionService#start, we specify the username that was configured in the legacy ROC when creating the destination URI (previously, we didn't specify the username when constructing this URI). 2) In EjbClientContextSetupProcessor.RegistrationService#transformOne, when building up a match rule for the destination URI from the ROC, we ensure that we match on any user info present in the destination URI (i.e., rule.matchUser(userInfo)) 3) To determine the AuthenticationConfiguration to use for EJBClientInvocationContext in EJBInvocationHandler#invoke, we use AuthenticationContextConfigurationClient#getAuthenticationConfiguration if there is no sticky authentication configuration present. I looked at what's happening in AuthenticationContextConfigurationClient#getAuthenticationConfiguration. The AuthenticationContext is actually correct at this point. However, the URI that is passed to AuthenticationContextConfigurationClient#getAuthenticationConfiguration does not have any user info on it. Thus, the rule that we built up doesn't match this URI and so the AuthenticationConfiguration that corresponds to the user defined in the ROC won't get used. We should no longer attempt to match on the user info for the destination URI for a remote outbound connection. For the Elytron ROC case, where no username is meant to be specified on the ROC, we were erroneously treating the username as the string "undefined" and then attempting to match on the user "undefined". > Deployments referencing outbound connection with authentication context always use Elytron default-authentication-context > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8772 > URL: https://issues.jboss.org/browse/WFLY-8772 > Project: WildFly > Issue Type: Bug > Components: Remoting, Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Labels: eap7.1-rfe-blocker, eap7.1-rfe-failure, eap71_beta_candidate > > Analysis document for EAP7-551 states the following: > {quote}This RFE is to add a reference to the new authentication-context capability to the remote-outbound-connection resource and make use of it satisfy the security requirements for the outbound connections being established. > The AuthenticationContext will be used to access both information required for authentication and also for any SSLContext required for the connection. > A newly referenced authentication-context will be used to provide all security configuration for outbound connections.{quote} > However, currently the remoting outbound connections will only use Elytron default authentication context and ignore authentication context defined in remoting outbound connection resource: > * If no default authentication context is defined in Elytron subsystem but remote outbound connection has defined one, no authentication context is associated with remote outbound connection. > * If the default authentication context is defined in Elytron subsystem but no authentication context is defined in remote outbound connection, remoting assumes that outbound connection uses legacy security. > * If the default authentication context is defined in Elytron subsystem and different authentication context is defined in remote outbound connection, the remote outbound connection will use the Elytron subsystem default none the less. > * The authentication context defined in outbound remote connection will only work if it is the same as default authentication context in Elytron subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1563) Values are always said to be invalid even when the respect the enumeration

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1563?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1563: ------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > Values are always said to be invalid even when the respect the enumeration > -------------------------------------------------------------------------- > > Key: DROOLS-1563 > URL: https://issues.jboss.org/browse/DROOLS-1563 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Matteo Mortari > Attachments: RBLoR test.dmn > > > When running the attached file which has one input that is a collection of a complex structure, the constraints on the field is always said to be invalid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-22) Deprecate interrupt protection and remove jboss-threads integration

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-22?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-22: ---------------------------- Description: Interrupt protection has been removed from the requirements. It means that AG-19 sould be reverted, and also InterruptProtection should be removed from the API was:Interrupt protection has been removed from the requirements > Deprecate interrupt protection and remove jboss-threads integration > ------------------------------------------------------------------- > > Key: AG-22 > URL: https://issues.jboss.org/browse/AG-22 > Project: Agroal > Issue Type: Task > Components: api, jboss-threads > Affects Versions: 0.1 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.2 > > > Interrupt protection has been removed from the requirements. > It means that AG-19 sould be reverted, and also InterruptProtection should be removed from the API -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1563) Values are always said to be invalid even when the respect the enumeration

by Mélanie Gauthier (JIRA)

Mélanie Gauthier created DROOLS-1563: ---------------------------------------- Summary: Values are always said to be invalid even when the respect the enumeration Key: DROOLS-1563 URL: https://issues.jboss.org/browse/DROOLS-1563 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Mélanie Gauthier Assignee: Edson Tirelli Attachments: RBLoR test.dmn When running the attached file which has one input that is a collection of a complex structure, the constraints on the field is always said to be invalid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1157) When merging an AuthenticationConfiguration instance with another one, only replace this AuthenticationConfiguration instance's credential source if it is explicitly configured in the other one

by Farah Juma (JIRA)

Farah Juma created ELY-1157: ------------------------------- Summary: When merging an AuthenticationConfiguration instance with another one, only replace this AuthenticationConfiguration instance's credential source if it is explicitly configured in the other one Key: ELY-1157 URL: https://issues.jboss.org/browse/ELY-1157 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 May 2017