November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5689) EJB subsystem security domain mapping

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-5689?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-5689: ----------------------------- Labels: affects_elytron (was: ) > EJB subsystem security domain mapping > ------------------------------------- > > Key: WFLY-5689 > URL: https://issues.jboss.org/browse/WFLY-5689 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > Fix For: 11.0.0.Alpha1 > > > Allow the EJB subsystem to declare which Elytron security domains it uses. > Sample configuration: > {code:xml} > <security-domains default="ApplicationDomain"> > <security-domain name="ApplicationDomain" alias="MyDomain"/> > <security-domain name="ManagementDomain"/> > </security-domains> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1133) JDK 1.8 on Mac causes javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found

by Jay SenSharma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1133?page=com.atlassian.jira.plugi... ] Jay SenSharma commented on WFCORE-1133: --------------------------------------- Pull request sent: https://github.com/wildfly/wildfly-core/pull/1249 Looks like we need to add following dependency in the "sun.scripting" module {code:java} <path name="apple/applescript"/> {code} > JDK 1.8 on Mac causes javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > --------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1133 > URL: https://issues.jboss.org/browse/WFCORE-1133 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 2.0.1.Final > Environment: Macbook > JDK 1.8 > Reporter: Jay SenSharma > Attachments: WildFlyServerSideJavaScript.war > > > - When we try deploying any simple ServerSide java script based application on WildFly 10 we see the following Error while deploying the application: > {code:java} > 22:50:49,050 ERROR [stderr] (ServerService Thread Pool -- 62) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > {code} > try deploying the attached application on WildFly 10 and notice the console output. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1133) JDK 1.8 on Mac causes javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found

by Jay SenSharma (JIRA)

Jay SenSharma created WFCORE-1133: ------------------------------------- Summary: JDK 1.8 on Mac causes javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found Key: WFCORE-1133 URL: https://issues.jboss.org/browse/WFCORE-1133 Project: WildFly Core Issue Type: Feature Request Affects Versions: 2.0.1.Final Environment: Macbook JDK 1.8 Reporter: Jay SenSharma Attachments: WildFlyServerSideJavaScript.war - When we try deploying any simple ServerSide java script based application on WildFly 10 we see the following Error while deploying the application: {code:java} 22:50:49,050 ERROR [stderr] (ServerService Thread Pool -- 62) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found {code} try deploying the attached application on WildFly 10 and notice the console output. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1133) JDK 1.8 on Mac causes javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found

by Jay SenSharma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1133?page=com.atlassian.jira.plugi... ] Jay SenSharma updated WFCORE-1133: ---------------------------------- Issue Type: Bug (was: Feature Request) > JDK 1.8 on Mac causes javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > --------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1133 > URL: https://issues.jboss.org/browse/WFCORE-1133 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 2.0.1.Final > Environment: Macbook > JDK 1.8 > Reporter: Jay SenSharma > Attachments: WildFlyServerSideJavaScript.war > > > - When we try deploying any simple ServerSide java script based application on WildFly 10 we see the following Error while deploying the application: > {code:java} > 22:50:49,050 ERROR [stderr] (ServerService Thread Pool -- 62) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found > {code} > try deploying the attached application on WildFly 10 and notice the console output. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-370) Cryptographic signature evidence type

by David Lloyd (JIRA)

David Lloyd created ELY-370: ------------------------------- Summary: Cryptographic signature evidence type Key: ELY-370 URL: https://issues.jboss.org/browse/ELY-370 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Add a cryptographic signature evidence type, which should be verifiable by all key- and certificate-based credentials. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-482) Inventory of dependencies that do not fulfill our minimal dependency requirements.

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-482?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-482: ------------------------------------------ Attachment: dependency-tree.txt dependecy:tree > Inventory of dependencies that do not fulfill our minimal dependency requirements. > ---------------------------------------------------------------------------------- > > Key: DROOLS-482 > URL: https://issues.jboss.org/browse/DROOLS-482 > Project: Drools > Issue Type: Task > Affects Versions: 6.1.0.Beta3 > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Attachments: dependency-tree.txt > > > We have a set of minimal requirements for our dependencies: > https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/READ... > If you're aware of any dependency that doesn't meet these requirements, please add it in this jira (description or comment). > Violating dependencies: > (none known yet) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-514) Clean up jetty dependencies in kie-parent-with-dependencies pom.xml

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-514?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer commented on DROOLS-514: ----------------------------------------------- not anymore found jettys in dependency:trees > Clean up jetty dependencies in kie-parent-with-dependencies pom.xml > ------------------------------------------------------------------- > > Key: DROOLS-514 > URL: https://issues.jboss.org/browse/DROOLS-514 > Project: Drools > Issue Type: Task > Affects Versions: 6.1.0.Beta4 > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Attachments: jetty-depTree.txt > > > 1) Make an inventory (using "mvn-all dependency:tree) of all modules that use jetty dependency and clearly indicate per module: > - Jetty groupId and Jetty version > - Scope: test or production > - Build classpath: normal dependency or plugin dependency (latter makes scope n/a) > 2) In theory, we should have no normal dependency in a non-test scope to Jetty, as our stuff is deployed on JBoss EAP, Tomcat, Jetty and WildFly alike. Is this true? > GWT does use Jetty, but only during compilation (= plugin classpath, not the dependencies classpath). gwt-dev is a fat jar that includes jetty even... but gwt-dev shouldn' be in the dependencies either (but it is and it needs to be removed!). > 3) Based on this inventory, discuss with ge0ffrey and mantis plan of attack. > Goal: Get rid of the jetty mess in kie-parent-with-dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-916) Upgrade wagon-provider-api from 1.0 to at least 2.6, so it's since with the rest of the maven/aether dependencies

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-916?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer resolved DROOLS-916. ------------------------------------------- Resolution: Done > Upgrade wagon-provider-api from 1.0 to at least 2.6, so it's since with the rest of the maven/aether dependencies > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-916 > URL: https://issues.jboss.org/browse/DROOLS-916 > Project: Drools > Issue Type: Task > Affects Versions: 6.3.0.CR2 > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Minor > > This downgrade in our dependency looks pretty bad. > {code} > [INFO] | | +- org.apache.maven.wagon:wagon-provider-api:jar:1.0:test (version managed from 2.6) > [INFO] | | +- org.apache.maven.wagon:wagon-file:jar:2.6:test > [INFO] | | | +- commons-lang:commons-lang:jar:2.6:test > {code} > It's probably because the ip-bom overwrites the wagon-provider-api version to 1.0 (while transitively it's 2.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1127) SocketBindingManagerImpl$UnnamedRegistryImpl is overly picky about unbound sockets

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1127?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-1127: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1282532 Bugzilla Update: Perform > SocketBindingManagerImpl$UnnamedRegistryImpl is overly picky about unbound sockets > ---------------------------------------------------------------------------------- > > Key: WFCORE-1127 > URL: https://issues.jboss.org/browse/WFCORE-1127 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.1.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.2.Final (EAP 7) > > > A failure like this isn't necessary: > {code} > 08:02:23,475 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.jgroups.channel.ee.connector: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee.connector: java.lang.IllegalStateException > at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:96) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalStateException > at org.jboss.as.network.SocketBindingManagerImpl$UnnamedRegistryImpl.unregisterBinding(SocketBindingManagerImpl.java:501) > at org.jboss.as.network.ManagedDatagramSocketBinding.close(ManagedDatagramSocketBinding.java:73) > at org.jboss.as.clustering.jgroups.ManagedSocketFactory.close(ManagedSocketFactory.java:148) > at org.jgroups.protocols.UDP.closeUnicastSocket(UDP.java:577) > at org.jgroups.protocols.UDP.destroySockets(UDP.java:429) > at org.jgroups.protocols.UDP.start(UDP.java:274) > at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:965) > at org.jgroups.JChannel.startStack(JChannel.java:890) > at org.jgroups.JChannel._preConnect(JChannel.java:553) > at org.jgroups.JChannel.connect(JChannel.java:288) > at org.jgroups.JChannel.connect(JChannel.java:279) > at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:94) > ... 5 more > {code} > If there's no socket address, it should just move on. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-916) Upgrade wagon-provider-api from 1.0 to at least 2.6, so it's since with the rest of the maven/aether dependencies

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-916?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-916: ----------------------------------------- +1 to resolve this, as it's been fixed with my PR for arquillian/aether etc that went into CR30. > Upgrade wagon-provider-api from 1.0 to at least 2.6, so it's since with the rest of the maven/aether dependencies > ----------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-916 > URL: https://issues.jboss.org/browse/DROOLS-916 > Project: Drools > Issue Type: Task > Affects Versions: 6.3.0.CR2 > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Minor > > This downgrade in our dependency looks pretty bad. > {code} > [INFO] | | +- org.apache.maven.wagon:wagon-provider-api:jar:1.0:test (version managed from 2.6) > [INFO] | | +- org.apache.maven.wagon:wagon-file:jar:2.6:test > [INFO] | | | +- commons-lang:commons-lang:jar:2.6:test > {code} > It's probably because the ip-bom overwrites the wagon-provider-api version to 1.0 (while transitively it's 2.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015