[JBoss JIRA] (WFLY-6048) jboss-webservices.xml descriptor doesn't override @WebContext annotation
by Wojciech Oczkowski (JIRA)
Wojciech Oczkowski created WFLY-6048:
----------------------------------------
Summary: jboss-webservices.xml descriptor doesn't override @WebContext annotation
Key: WFLY-6048
URL: https://issues.jboss.org/browse/WFLY-6048
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 9.0.2.Final
Environment: ubuntu 14.04, Java 7
Reporter: Wojciech Oczkowski
Assignee: Alessio Soldano
Priority: Minor
Attachments: ws-xml-override.zip
It seems that annotation WebConfig takes precedence over jboss-webservices.xml descriptor values. It doesn't seem right as you cannot override annotation values for test purposes for example.
Problematic code seems to be:
org.jboss.as.webservices.metadata.AbstractMetaDataBuilderEJB:159
(should prefer JBossPortComponentMetaData over EJBEndpoint)
and
org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect:177
(should prefer EJBSecurityMetaData over annotation value)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1039) An invalid kie.conf should throw an exception and not be silently ignored
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1039?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1039:
-------------------------------------
Affects Version/s: 6.4.0.Beta1
> An invalid kie.conf should throw an exception and not be silently ignored
> -------------------------------------------------------------------------
>
> Key: DROOLS-1039
> URL: https://issues.jboss.org/browse/DROOLS-1039
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.4.0.Beta1
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> In drools-belief or optaplanner-core, change the META-INF/kie.conf file like this:
> {code}
> [
> 'assemblers' : [ new org.foo.ThisDoesNotExists() ],
> 'weavers' : [],
> 'runtimes' : [],
> 'beliefs' : []
> ]
> {code}
> Current behavior: it doesn't throw any exception, but of course later on things go haywire at some point with a completely unrelated error message.
> Expected Behavior: Fail fast and let me know that org.foo.ThisDoesNotExists does not exist and that my kie.conf is in error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1039) An invalid kie.conf should throw an exception and not be silently ignored
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1039?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1039:
-------------------------------------
Component/s: core engine
> An invalid kie.conf should throw an exception and not be silently ignored
> -------------------------------------------------------------------------
>
> Key: DROOLS-1039
> URL: https://issues.jboss.org/browse/DROOLS-1039
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 6.4.0.Beta1
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> In drools-belief or optaplanner-core, change the META-INF/kie.conf file like this:
> {code}
> [
> 'assemblers' : [ new org.foo.ThisDoesNotExists() ],
> 'weavers' : [],
> 'runtimes' : [],
> 'beliefs' : []
> ]
> {code}
> Current behavior: it doesn't throw any exception, but of course later on things go haywire at some point with a completely unrelated error message.
> Expected Behavior: Fail fast and let me know that org.foo.ThisDoesNotExists does not exist and that my kie.conf is in error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1039) An invalid kie.conf should throw an exception and not be silently ignored
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-1039:
----------------------------------------
Summary: An invalid kie.conf should throw an exception and not be silently ignored
Key: DROOLS-1039
URL: https://issues.jboss.org/browse/DROOLS-1039
Project: Drools
Issue Type: Enhancement
Reporter: Geoffrey De Smet
Assignee: Mark Proctor
In drools-belief or optaplanner-core, change the META-INF/kie.conf file like this:
{code}
[
'assemblers' : [ new org.foo.ThisDoesNotExists() ],
'weavers' : [],
'runtimes' : [],
'beliefs' : []
]
{code}
Current behavior: it doesn't throw any exception, but of course later on things go haywire at some point with a completely unrelated error message.
Expected Behavior: Fail fast and let me know that org.foo.ThisDoesNotExists does not exist and that my kie.conf is in error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1039) An invalid kie.conf should throw an exception and not be silently ignored
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1039?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet reassigned DROOLS-1039:
----------------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> An invalid kie.conf should throw an exception and not be silently ignored
> -------------------------------------------------------------------------
>
> Key: DROOLS-1039
> URL: https://issues.jboss.org/browse/DROOLS-1039
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.4.0.Beta1
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> In drools-belief or optaplanner-core, change the META-INF/kie.conf file like this:
> {code}
> [
> 'assemblers' : [ new org.foo.ThisDoesNotExists() ],
> 'weavers' : [],
> 'runtimes' : [],
> 'beliefs' : []
> ]
> {code}
> Current behavior: it doesn't throw any exception, but of course later on things go haywire at some point with a completely unrelated error message.
> Expected Behavior: Fail fast and let me know that org.foo.ThisDoesNotExists does not exist and that my kie.conf is in error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5989) FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-5989?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-5989:
-----------------------------------
You should not need the FilePermissions. Do you have an exception stack trace?
> FilePermission for XNIO and Marshalling modules are required for Remoting to run with security manager
> ------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5989
> URL: https://issues.jboss.org/browse/WFLY-5989
> Project: WildFly
> Issue Type: Bug
> Components: Remoting, Security Manager
> Affects Versions: 10.0.0.CR5
> Reporter: Ondrej Kotek
> Assignee: David Lloyd
> Priority: Critical
>
> Running _NestedRemoteContextTestCase_ (from WildFly _testsuite/integration/basic_) with security manager, like
> {noformat}
> ./integration-tests.sh -Dts.basic -Dts.noSmoke -Dtest=NestedRemoteContextTestCase -Dsecurity.manager
> {noformat}
> results in exception:
> {noformat}
> java.io.IOException: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found
> {noformat}
> To make it work, permissions like following need to be added to _permissions.xml_ of _ejb.ear_:
> {noformat}
> new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/xnio/nio/main/*", "read"),
> new FilePermission("/home/okotek/git/wildfly/dist/target/wildfly-10.0.0.CR5-SNAPSHOT/modules/system/layers/base/org/jboss/marshalling/river/main/*", "read"),
> new RemotingPermission("createEndpoint"),
> new RuntimePermission("createXnioWorker"),
> new RemotingPermission("addConnectionProvider"),
> new RuntimePermission("modifyThread"),
> new RuntimePermission("accessDeclaredMembers"),
> new ReflectPermission("suppressAccessChecks")
> {noformat}
> which is very confusing.
> Why do I need add seemingly unrelated permissions, like _FilePermission_ for XNIO and marshalling or _RuntimePermission_ for createXnioWorker? Such behavior should be fixed or properly documented.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months